What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
0

Heißt natürlich nicht, dass sie es nicht trotzdem versuchen und einen Haufen Kohle dafür rauswerfen. Also, wenn ihr schon nicht gegen Abschiebungen seid, weil sie menschenfeindliche Kackscheiße sind, dann seid doch wenigstens dagegen, weil es kaum eine größere Geldverschwendung gibt, als Abschiebungen?

@marcelMarcel Keienborg Das Geldargument bringt leider nichts, merkt man auch schon hier beim Bürgergeld wo man immer wieder gegen das Amt klagen muss obwohl sie wissen das sie falsch liegen (und dazu jedes mal die Prozesskostenhilfe usw. vom Staat getragen werden muss) dazu das massive Bürokratiemonster mit den Zwangsterminen usw. der deutsche Michel lässt sich seine Peitschenhiebe furchtbar gern bezahlen <.<

0

Heißt natürlich nicht, dass sie es nicht trotzdem versuchen und einen Haufen Kohle dafür rauswerfen. Also, wenn ihr schon nicht gegen Abschiebungen seid, weil sie menschenfeindliche Kackscheiße sind, dann seid doch wenigstens dagegen, weil es kaum eine größere Geldverschwendung gibt, als Abschiebungen?

0
0
0
0

I’m sure we will hear a lot about Bill Atkinson (RIP) over the next few days, but I want to point out the huge influence of on the Web. @timblTim Berners-Lee himself mentioned it in his original WWW proposal (cybercultural.com/p/1990-progr), early web browsers like ViolaWWW were modeled on HyperCard (cybercultural.com/p/1992-web-v), and even JavaScript owed a debt to it (HyperCard included an object oriented scripting language called HyperTalk; cybercultural.com/p/1995-the-b).

0

I organized meetups for a decade.

Most of them were technical.

One thing I learned is what tends to make a talk good or bad.

Here it is —

Good talks tell a story

Tell a story!

Here is the story most good tech talks tell —

• I had this problem
• I first tried to solve it this way, but it failed
• Then I tried to solve it this way, and I succeeded

Wrap what you want to say in terms of a story

There is something about the human mind that makes us (humans) receptive to stories

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

그리고 이거 그린 쪽 출처가 혐세같아서 더 웃김 뭘 두려워하는지 너무 선명해서 "가부장제, 전통 규범이 무너지면 내가 설 자리는 없다고!" "바로 그걸 원한 겁니다!"

RE: https://bsky.app/profile/did:plc:rnly2atatlotgylbzw23kpxw/post/3lqzioig3ck2n

1

"교인인 76.4% 목회자 92.6% 동성애, 동성 결혼 반대한다고 응답했습니다. 그러니까 이건 진보 보수의 문제가 아니라 교회는 이미 이걸로 간 거예요. 지금 그냥 동성애 동성혼은 반대. 이 정서를 지금 이식을 시켰단 말이에요." [출처: 뉴스앤조이] [주간 처치독] 한국교회 극우 비율, 얼마나 될까 교회를 잡아야 하네요

RE: https://bsky.app/profile/did:plc:a6qvfkbrohedqy3dt6k5mdv6/post/3lqzqlbgips2b

0
0
0
0

@reiver ⊼ (Charles) :batman: shared the below article:

Session 6 Notes

benpate @benpate@emissary.nodebb.com

<p>Please help to take good notes. We will publish them on <a href="http://fediforum.org" rel="nofollow ugc">fediforum.org</a> like we did after previous events.</p> <p>Data and Account Portability: ...<br /> Convener of the session: Dmitri Z. <a href="https://social.coop/@dmitri">@<bdi>dmitri@social.coop</bdi></a></p> <p>Slides: <a href="https://docs.google.com/presentation/d/1SSFrS2ke2tqMZrRUGyIPsOXIfS62qZFu0JcyBVSz9rI/" rel="nofollow ugc">https://docs.google.com/presentation/d/1SSFrS2ke2tqMZrRUGyIPsOXIfS62qZFu0JcyBVSz9rI/</a></p> <p>Attendees (please add your own name here if you would like to be listed. There is no obligation.)<br /> Charles Iliya Krempeaux <a href="https://mastodon.social/@reiver">@<bdi>reiver@mastodon.social</bdi></a><br /> Scott M. Stolz <a href="https://loves.tech/channel/scott">@<bdi>scott@loves.tech</bdi></a> <a href="https://codejournal.dev/channel/scott">@<bdi>scott@codejournal.dev</bdi></a> @scott.codejournal.dev<br /> Raphael Lullis @raphael@communick.com<br /> <a href="http://bumblefudge.com" rel="nofollow ugc">bumblefudge.com</a><br /> Scott Jenson <a href="https://social.coop/@scottjenson">@<bdi>scottjenson@social.coop</bdi></a><br /> Ben Pate <a href="https://mastodon.social/@benpate">@<bdi>benpate@mastodon.social</bdi></a><br /> Nigini Oliveira <a href="https://social.coop/@nigini">@<bdi>nigini@social.coop</bdi></a><br /> Johannes Ernst <a href="https://j12t.org" rel="nofollow ugc">https://j12t.org</a> <a href="https://j12t.social/@j12t">@<bdi>j12t@j12t.social</bdi></a> @j12t.org<br /> Ryan Barrett @snarfed.org<br /> Damon, @damonoutlaw.xyz<br /> Maho Pacheco <a href="https://hachyderm.io/@mapache">@<bdi>mapache@hachyderm.io</bdi></a><br /> Seth Goldstein <a href="https://indieweb.social/@phillycodehound">@<bdi>phillycodehound@indieweb.social</bdi></a> &lt;&lt; <a href="https://social.sethgoldstein.me" rel="nofollow ugc">https://social.sethgoldstein.me</a><br /> James Marshall @jamesmarshall@sfba.social<br /> Evan Prodromou <a rel="nofollow ugc">acct:evan@cosocial.ca</a><br /> Paul Fuxjaeger @cypherhippie@chaos.social<br /> Cagan Mert Islek, <a href="https://islekcaganmert.me/">@<bdi>islekcaganmert.me@bsky.brid.gy</bdi></a><br /> Tom Casavant <a href="https://tomkahe.com/@tom">@<bdi>tom@tomkahe.com</bdi></a><br /> David Rowley<br /> Jesse Karmani <a href="https://mastodon.social/@jesseplusplus">@<bdi>jesseplusplus@mastodon.social</bdi></a><br /> Matt Baer @matt@writing.exchange</p> <p>Website (if the subject has one): ...</p> <p>Notes<br /> We are trying to do on the Open Social Web what email accomplished</p> <ul> <li>You can dowload your emails and contacts and move to another email provider.</li> </ul> <p>We have tiny windows of portability on Web 2 (and its platforms)</p> <ul> <li>sometimes parts of your data</li> <li>but generally they lock in your social graph.</li> </ul> <p>Can we do better? YES!</p> <ul> <li> <p>We want to EXPORT data (not only posts, but also interactions and media), identifiers, as well as the social graph</p> </li> <li> <p>AND IMPORT</p> </li> <li> <p>Automated</p> </li> <li> <p>Dmitry asked developers interested in this to join: <a href="https://www.w3.org/community/socialcg/" rel="nofollow ugc">https://www.w3.org/community/socialcg/</a></p> </li> <li> <p>Dmitry: checkout: <a href="https://swicg.github.io/activitypub-data-portability/lola.html" rel="nofollow ugc">https://swicg.github.io/activitypub-data-portability/lola.html</a></p> </li> </ul> <p>Current efforts:<br /> - DTI &amp; LOLA: (online portability) <a href="https://swicg.github.io/activitypub-data-portability/lola.html" rel="nofollow ugc">https://swicg.github.io/activitypub-data-portability/lola.html</a></p> <p>Connection with Cory's remedies for enshitification:<br /> - a core affordance is easy portability between difference service providers!!!</p> <p>Q: what are the groups we can contribute to to make this happen?</p> <ul> <li>How can we get to having the "migration button" (some service providers are blocked for a lack of clarity on how to move forward)</li> <li>Comment: Hubzilla has implemented a lot of what is been discussed!</li> <li>FEP-c390 - Identity proofs</li> <li>identity is not associated to a server</li> <li></li> </ul> <p>A: Roadmap as proposed by Data Portability Work Group</p> <ul> <li>FEP-7952</li> </ul> <p>Q: What is the strucuture of the problem?<br /> - Export protocol<br /> - Content addressing/format<br /> - Identify mapping?<br /> - Post migration<br /> - Huge issues for modation<br /> - ...</p> <p>Hubzilla, Streams, Forte, and Mitra are working on a solution:</p> <pre><code>Client-side keys </code></pre> <p>Links<br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/7952/fep-7952.md" rel="nofollow ugc">FEP-7952: Roadmap For Actor and Object Portability</a> (see <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/7952/fep-7952.md#references" rel="nofollow ugc">References section</a> for many relevant FEPs)<br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/73cd/fep-73cd.md#migration-user-stories" rel="nofollow ugc">FEP-73cd: Migration User Stories</a><br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/6fcd/fep-6fcd.md" rel="nofollow ugc">FEP-6fcd: Account Export Container Format</a> and <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/9091/fep-9091.md" rel="nofollow ugc">FEP-9091: Export Actor Service Endpoint</a><br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/cd47/fep-cd47.md" rel="nofollow ugc">FEP-cd47: Federation-friendly Addressing and Deduplication Use-Cases</a> - Content-addressing &lt;&gt; DATA Portability considerations<br /> <a href="https://github.com/fedimod/fires" rel="nofollow ugc">FediMOD FIRES tooling for portable/interoperable moderation records (WIP)</a> - re-moderating or checking for moderation history at time of import can use FIRES if exporting/prior server also supports it<br /> <a href="https://erinkissane.com/notes-from-a-mastodon-migration" rel="nofollow ugc">https://erinkissane.com/notes-from-a-mastodon-migration</a><br /> <a href="https://github.com/tweetback/tweetback" rel="nofollow ugc">https://github.com/tweetback/tweetback</a><br /> Identity Proofs - <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/c390/fep-c390.md" rel="nofollow ugc">https://codeberg.org/fediverse/fep/src/branch/main/fep/c390/fep-c390.md</a></p>

Read more →
0
0
0
1
1

Why Bell Labs worked so well, and could innovate so much, while today’s innovation, in spite of the huge private funding, goes in hype-and-fizzle cycles that leave relatively little behind, is a question I’ve been asking myself a lot in the past years.

And I think that the author of this article has hit the nail on its head on most of the reasons - but he didn’t take the last step in identifying the root cause.

What Bell Labs achieved within a few decades is probably unprecedented in human history:

  • They employed folks like Nyquist and Shannon, who laid the foundations of modern information theory and electronic engineering while they were employees at Bell.

  • They discovered the first evidence of the black hole at the center of our galaxy in the 1930s while analyzing static noise on shortwave transmissions.

  • They developed in 1937 the first speech codec and the first speech synthesizer.

  • They developed the photovoltaic cell in the 1940, and the first solar cell in the 1950s.

  • They built the first transistor in 1947.

  • They built the first large-scale electronic computers (from Model I in 1939 to Model VI in 1949).

  • They employed Karnaugh in the 1950s, who worked on the Karnaugh maps that we still study in engineering while he was an employee at Bell.

  • They contributed in 1956 (together with AT&T and the British and Canadian telephone companies) to the first transatlantic communications cable.

  • They developed the first electronic musics program in 1957.

  • They employed Kernighan, Thompson and Ritchie, who created UNIX and the C programming language while they were Bell employees.

And then their rate of innovation suddenly fizzled out after the 1980s.

I often hear that Bell could do what they did because they had plenty of funding. But I don’t think that’s the main reason. The author rightly points out that Google, Microsoft and Apple have already made much more profit than Bell has ever seen in its entire history. Yet, despite being awash with money, none of them has been as impactful as Bell. Nowadays those companies don’t even innovate much besides providing you with a new version of Android, of Windows or the iPhone every now and then. And they jump on the next hype wagon (social media, AR/VR, Blockchain, AI…) just to deliver half-baked products that (especially in Google’s case) are abandoned as soon as the hype bubble bursts.

Let alone singlehandedly spear innovation that can revolutionize an entire industry, let alone make groundbreaking discoveries that engineers will still study a century later.

So what was Bell’s recipe that Google and Apple, despite having much more money and talented people, can’t replicate? And what killed that magic?

Well, first of all Bell and Kelly had an innate talent in spotting the “geekiest” among us. They would often recruit from pools of enthusiasts that had built their own home-made radio transmitters for fun, rather than recruiting from the top business schools, or among those who can solve some very abstract and very standardized HackerRank problems.

And they knew how to manage those people. According to Kelly’s golden rule:

How do you manage genius? You don’t

Bell specifically recruited people that had that strange urge of tinkering and solving big problems, they were given their lab and all the funding that they needed, and they could work in peace. Often it took years before Kelly asked them how their work was progressing.

Compare it to a Ph.D today who needs to struggle for funding, needs to produce papers that get accepted in conferences, regardless of their level of quality, and must spend much more time on paperwork than on actual research.

Or to an engineer in a big tech company that has to provide daily updates about their progress, has to survive the next round of layoffs, has to go through endless loops of compliance, permissions and corporate bureaucracy in order to get anything done, has their performance evaluated every 3 months, and doesn’t even have control on what gets shipped - that control has been taken away from engineers and given to PMs and MBA folks.

Compare that way of working with today’s backlogs, metrics, micromanaging and struggle for a dignified salary or a stable job.

We can’t have the new Nyquist, Shannon or Ritchie today simply because, in science and engineering, we’ve moved all the controls away from the passionate technical folks that care about the long-term impact of their work, and handed them to greedy business folks who only care about short-term returns for their investors.

So we ended up with a culture that feels like talent must be managed, even micromanaged, otherwise talented people will start slacking off and spending their days on TikTok.

But, as Kelly eloquently put it:

“What stops a gifted mind from just slacking off?” is the wrong question to ask. The right question is, “Why would you expect information theory from someone who needs a babysitter?”

Or, as Peter Higgs (the Higgs boson guy) put it:

It’s difficult to imagine how I would ever have enough peace and quiet in the present sort of climate to do what I did in 1964… Today I wouldn’t get an academic job. It’s as simple as that. I don’t think I would be regarded as productive enough.

Or, as Shannon himself put it:

I’ve always pursued my interests without much regard for final value or value to the world. I’ve spent lots of time on totally useless things.

So basically the most brilliant minds of the 20th century would be considered lazy slackers today and be put on a PIP because they don’t deliver enough code or write enough papers.

So the article is spot on in identifying why Bell could invent, within a few years, all it did, while Apple, despite having much more money, hasn’t really done anything new in the past decade. MBAs, deadlines, pseudo-objective metrics and short-termism killed scientific inquiry and engineering ingenuity.

But the author doesn’t go one step further and identify the root cause.

It correctly spots the business and organizational issues that exist in managing talent today, but it doesn’t go deeper into their economic roots.

You see, MBA graduates and CEOs didn’t destroy the spirit of scientific and engineering ingenuity spurred by the Industrial Revolution just because they’re evil. I mean, there’s a higher chance for someone who has climbed the whole corporate ladder to be a sociopath than there is for someone you randomly picked from the street, but not to the point where they would willingly tame and screw the most talented minds of their generation, and squeeze them into a Jira board or a metric that looks at the number of commits, out of pure sadism.

They did so because the financial incentives have drastically changed from the times of Bells Labs.

The Bells Labs were basically publicly funded. AT&T operated the telephone lines in the US, paid by everyone who used telephones, and they reinvested a 1% tax into R&D (the Bells Labs). And nobody expected a single dime of profits to come out from the Bells Labs.

And btw, R&D was real R&D with no strings attached at the time. In theory also my employer does R&D today - but we just ended up treating whatever narrow iterative feature requested by whatever random PM as “research and development”. It’s not like scientists have much freedom in what to research or engineers have much freedom in what to develop. R&D programs have mostly just become a way for large businesses to squeeze more money out of taxpayers, put it in their pockets, and not feel any moral obligation of contributing to anything other than their shareholders’ accounts.

And at the time the idea of people paying taxes, so talented people in their country could focus on inventing the computer, the Internet or putting someone on the moon, without the pressure of VCs asking for their dividends, or PMs asking them to migrate everything to another cloud infrastructure by next week, or to a new shiny framework that they’ve just heard in a conference, wasn’t seen as a socialist dystopia. It was before the neoliberal sociopaths of the Chicago school screwed up everything.

The America that invested into the Bell Labs and into the Apollo project was very different from today’s America. It knew that it was the government’s job to foster innovation and to create an environment where genuinely smart people could do great things without external pressure. That America hadn’t yet been infected by the perverse idea that the government should always be small, that it’s not the government’s job to make people’s lives better, and that it was the job of privately funded ventures seeking short-term returns to fund moonshots.

And, since nobody was expecting a dime back from Bell, nobody would put deadlines on talented people, nobody hired unqualified and arrogant business specialists to micromanage them, nobody would put them on a performance improvement plan if they were often late at their daily standups or didn’t commit enough lines of code in the previous quarter. So they had time to focus on how to solve some of the most complex problems that humans ever faced.

So they could invent the transistor, the programming infrastructure still used to this day, and lay the foundations of what engineers study today.

The most brilliant minds of our age don’t have this luxury. So they can’t revolutionarize our world like those in the 20th century did.

Somebody else sets their priorities and their deadlines.

They can’t think of moonshots because they’re forced to work on the next mobile app riding the next wave of hype that their investors want to release to market so they can get even richer.

They have to worry about companies trying to replace them with AI bots and business managers wanting to release products themselves by “vibe coding”, just to ask those smart people to clean up the mess they’ve done, just like babies who are incapable of cleaning up the food they’ve spilled on the floor.

They are seen as a cost, not as a resource. Kelly used to call himself a “patron” rather than a “manager”, and he trusted his employees, while today’s managers and investors mostly see their engineering resources as squishy blobs of flesh standing between their ambitious ideas and their money, and they can’t wait to replace them with robots that just fullfill all of their wishes.

Tech has become all about monetization nowadays and nothing about ingenuity.

As a result, there are way more brilliant minds (and way more money) in our age going towards solving the “convince people to click on this link” problem rather than solving the climate problem, for example.

Then of course they can’t invent the next transistor, or bring the next breakthrough in information theory.

Then of course all you get, after one year of the most brilliant minds of our generation working at the richest company that has ever existed, is just a new iPhone.

https://links.fabiomanganiello.com/share/683ee70d0409e6.66273547

0

Session 6 Notes

benpate @benpate@emissary.nodebb.com

<p>Please help to take good notes. We will publish them on <a href="http://fediforum.org" rel="nofollow ugc">fediforum.org</a> like we did after previous events.</p> <p>Data and Account Portability: ...<br /> Convener of the session: Dmitri Z. <a href="https://social.coop/@dmitri">@<bdi>dmitri@social.coop</bdi></a></p> <p>Slides: <a href="https://docs.google.com/presentation/d/1SSFrS2ke2tqMZrRUGyIPsOXIfS62qZFu0JcyBVSz9rI/" rel="nofollow ugc">https://docs.google.com/presentation/d/1SSFrS2ke2tqMZrRUGyIPsOXIfS62qZFu0JcyBVSz9rI/</a></p> <p>Attendees (please add your own name here if you would like to be listed. There is no obligation.)<br /> Charles Iliya Krempeaux <a href="https://mastodon.social/@reiver">@<bdi>reiver@mastodon.social</bdi></a><br /> Scott M. Stolz <a href="https://loves.tech/channel/scott">@<bdi>scott@loves.tech</bdi></a> <a href="https://codejournal.dev/channel/scott">@<bdi>scott@codejournal.dev</bdi></a> @scott.codejournal.dev<br /> Raphael Lullis @raphael@communick.com<br /> <a href="http://bumblefudge.com" rel="nofollow ugc">bumblefudge.com</a><br /> Scott Jenson <a href="https://social.coop/@scottjenson">@<bdi>scottjenson@social.coop</bdi></a><br /> Ben Pate <a href="https://mastodon.social/@benpate">@<bdi>benpate@mastodon.social</bdi></a><br /> Nigini Oliveira <a href="https://social.coop/@nigini">@<bdi>nigini@social.coop</bdi></a><br /> Johannes Ernst <a href="https://j12t.org" rel="nofollow ugc">https://j12t.org</a> <a href="https://j12t.social/@j12t">@<bdi>j12t@j12t.social</bdi></a> @j12t.org<br /> Ryan Barrett @snarfed.org<br /> Damon, @damonoutlaw.xyz<br /> Maho Pacheco <a href="https://hachyderm.io/@mapache">@<bdi>mapache@hachyderm.io</bdi></a><br /> Seth Goldstein <a href="https://indieweb.social/@phillycodehound">@<bdi>phillycodehound@indieweb.social</bdi></a> &lt;&lt; <a href="https://social.sethgoldstein.me" rel="nofollow ugc">https://social.sethgoldstein.me</a><br /> James Marshall @jamesmarshall@sfba.social<br /> Evan Prodromou <a rel="nofollow ugc">acct:evan@cosocial.ca</a><br /> Paul Fuxjaeger @cypherhippie@chaos.social<br /> Cagan Mert Islek, <a href="https://islekcaganmert.me/">@<bdi>islekcaganmert.me@bsky.brid.gy</bdi></a><br /> Tom Casavant <a href="https://tomkahe.com/@tom">@<bdi>tom@tomkahe.com</bdi></a><br /> David Rowley<br /> Jesse Karmani <a href="https://mastodon.social/@jesseplusplus">@<bdi>jesseplusplus@mastodon.social</bdi></a><br /> Matt Baer @matt@writing.exchange</p> <p>Website (if the subject has one): ...</p> <p>Notes<br /> We are trying to do on the Open Social Web what email accomplished</p> <ul> <li>You can dowload your emails and contacts and move to another email provider.</li> </ul> <p>We have tiny windows of portability on Web 2 (and its platforms)</p> <ul> <li>sometimes parts of your data</li> <li>but generally they lock in your social graph.</li> </ul> <p>Can we do better? YES!</p> <ul> <li> <p>We want to EXPORT data (not only posts, but also interactions and media), identifiers, as well as the social graph</p> </li> <li> <p>AND IMPORT</p> </li> <li> <p>Automated</p> </li> <li> <p>Dmitry asked developers interested in this to join: <a href="https://www.w3.org/community/socialcg/" rel="nofollow ugc">https://www.w3.org/community/socialcg/</a></p> </li> <li> <p>Dmitry: checkout: <a href="https://swicg.github.io/activitypub-data-portability/lola.html" rel="nofollow ugc">https://swicg.github.io/activitypub-data-portability/lola.html</a></p> </li> </ul> <p>Current efforts:<br /> - DTI &amp; LOLA: (online portability) <a href="https://swicg.github.io/activitypub-data-portability/lola.html" rel="nofollow ugc">https://swicg.github.io/activitypub-data-portability/lola.html</a></p> <p>Connection with Cory's remedies for enshitification:<br /> - a core affordance is easy portability between difference service providers!!!</p> <p>Q: what are the groups we can contribute to to make this happen?</p> <ul> <li>How can we get to having the "migration button" (some service providers are blocked for a lack of clarity on how to move forward)</li> <li>Comment: Hubzilla has implemented a lot of what is been discussed!</li> <li>FEP-c390 - Identity proofs</li> <li>identity is not associated to a server</li> <li></li> </ul> <p>A: Roadmap as proposed by Data Portability Work Group</p> <ul> <li>FEP-7952</li> </ul> <p>Q: What is the strucuture of the problem?<br /> - Export protocol<br /> - Content addressing/format<br /> - Identify mapping?<br /> - Post migration<br /> - Huge issues for modation<br /> - ...</p> <p>Hubzilla, Streams, Forte, and Mitra are working on a solution:</p> <pre><code>Client-side keys </code></pre> <p>Links<br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/7952/fep-7952.md" rel="nofollow ugc">FEP-7952: Roadmap For Actor and Object Portability</a> (see <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/7952/fep-7952.md#references" rel="nofollow ugc">References section</a> for many relevant FEPs)<br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/73cd/fep-73cd.md#migration-user-stories" rel="nofollow ugc">FEP-73cd: Migration User Stories</a><br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/6fcd/fep-6fcd.md" rel="nofollow ugc">FEP-6fcd: Account Export Container Format</a> and <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/9091/fep-9091.md" rel="nofollow ugc">FEP-9091: Export Actor Service Endpoint</a><br /> <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/cd47/fep-cd47.md" rel="nofollow ugc">FEP-cd47: Federation-friendly Addressing and Deduplication Use-Cases</a> - Content-addressing &lt;&gt; DATA Portability considerations<br /> <a href="https://github.com/fedimod/fires" rel="nofollow ugc">FediMOD FIRES tooling for portable/interoperable moderation records (WIP)</a> - re-moderating or checking for moderation history at time of import can use FIRES if exporting/prior server also supports it<br /> <a href="https://erinkissane.com/notes-from-a-mastodon-migration" rel="nofollow ugc">https://erinkissane.com/notes-from-a-mastodon-migration</a><br /> <a href="https://github.com/tweetback/tweetback" rel="nofollow ugc">https://github.com/tweetback/tweetback</a><br /> Identity Proofs - <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/c390/fep-c390.md" rel="nofollow ugc">https://codeberg.org/fediverse/fep/src/branch/main/fep/c390/fep-c390.md</a></p>

Read more →
0

I’m sure we will hear a lot about Bill Atkinson (RIP) over the next few days, but I want to point out the huge influence of on the Web. @timblTim Berners-Lee himself mentioned it in his original WWW proposal (cybercultural.com/p/1990-progr), early web browsers like ViolaWWW were modeled on HyperCard (cybercultural.com/p/1992-web-v), and even JavaScript owed a debt to it (HyperCard included an object oriented scripting language called HyperTalk; cybercultural.com/p/1995-the-b).

0
0
0
0
0

혐오로 정치하던 인간이 혐오를 대상이 되어버리고... 이 역시 그리스 비극적 모먼트가 아닐 수 없습니다!!! 세상에 이런 자업자득이 또 없죠!!

RE: https://bsky.app/profile/did:plc:447baz4chyvqlfcvy4c33tl5/post/3lqyyorxhx22l

0

I’m sure we will hear a lot about Bill Atkinson (RIP) over the next few days, but I want to point out the huge influence of on the Web. @timblTim Berners-Lee himself mentioned it in his original WWW proposal (cybercultural.com/p/1990-progr), early web browsers like ViolaWWW were modeled on HyperCard (cybercultural.com/p/1992-web-v), and even JavaScript owed a debt to it (HyperCard included an object oriented scripting language called HyperTalk; cybercultural.com/p/1995-the-b).

0
0
0

"Fünf junge Aktivisten wurden von der Polizei besucht, weil sie mit abwaschbarer Sprühkreide auf der Promenade zum Protest gegen Rechts aufgerufen hatten.
Der Einschüchterungseffekt wird dabei nicht nur in Kauf genommen, sondern ist auch ein Ziel und Zweck der Maßnahme."

allesmuenster.de/polizei-vor-d

Wollt ihr Nazis beleidigen? Dann habt ihr mit der zu tun.

0
0

Reminder that if you like a website you should probably click on the "contact" link and tell the author you like their website

🐰 Oh I bet they get lots of email every day saying their website is cool, I'd just annoy them
🦝 Nope. I have a donations button and I'm not exaggerating when I say it gets hit a hundred times more often than my email address. People will literally transfer ten dollars from their bank account before saying "Hey cool website btw."

🐀 Wouldn't it be weird though
🦝 My learned friend, why do you think there's a "Contact" page on the website in the first place, it's so that you can say "Hey cool website btw."

🐴 This site hasn't been updated in ages, I bet they're not even interested anymore
🦝 Or maybe they stopped updating it because they had ten thousand people reading it every day but it felt empty and unfulfilling like shouting into a hole because only two of them ever emailed to say "Hey cool website btw."

🐹 But what do I even say
🦝 You say "Hey cool website btw."

0
0
0
0
0
0
0
0
0