Last Week in Fediverse – ep 86
Threads degrades their fediverse integration, a separate ActivityPub-based Island Network launches, and more news about Ghost and ActivityPub.
Threads delays posts for 15 minutes before federating
Threads’ latest update has degraded the value of their fediverse integration. Posts made on Threads will now always be delayed by 15 minutes before they are delivered to the rest of the fediverse, if fediverse sharing is turned on. The 15 minute delay is added for the purpose of post editing; posts on Threads can now be edited for 15 minutes after they are created. This used to be 5 minutes, both as a window for editing posts as well as the delay to be send out to the rest of the fediverse.
A 15 minute delay is a long time in microblogging, and significantly impacts things like breaking news, and live-posting sports events. It also meaningfully impacts the ability to have a back-and-forth conversation with people in a comment section. The delay itself is already an issue, but things get even more problematic when taken into consideration that during live events, Threads posts with a 15 minute delay are now mixed with fediverse posts without a delay and presented as happening during the same time. This was already noticeable during yesterday’s U.S. VP debate, an event where people use microblogging for the real-time reaction. But part of the real-time reactions was actually 15 minutes delayed, while another part was not, which creates even more confusing experience. A Threads engineer says that they will want to solve this problem ‘eventually’, but that it will probably come after Threads has implemented full bi-directional interoperability.
This news is not a great start for the Social Web Foundation either, which launched last week with criticism from the wider fediverse developer community for having Meta as one of their supporting members. There is a distrust of Meta’s intention within the fediverse, and them degrading their fediverse integration is likely not helping.
Website League
The Website League is a new social networking project that has arisen out of the demise of Cohost. Cohost was a social media site for the last 2 years, that has shut down, and on October 1st the website entered read-only mode. Cohost had a dedicated user base who appreciated the community that they’ve build on the site. Website League is a new project by users of Cohost (the Cohost staff is not involved) to build a successor network in Cohost’s place.
What makes Website League stand out is that it is a federated Island Network, described by Website League themselves as ‘a bunch of smallish websites that talk to each other’. This federated social network is using ActivityPub, but deliberately does not connect to the rest of the fediverse. Instead, it is an allowlist-based form of federation, where only websites/servers who agree to the Website League’s central set of rules can join.
The Website League has a big focus community organisation and governance. Even though the project is very young, and launched under time pressure of the deadline of Cohost closing, there are already multiple systems in place with an active Loomio for Stewardship, a wiki and more. The Website League provides a different vision of what a federated social network build on top of ActivityPub can look like, and I’m very curious to see where the project will go.
Ghost and Fedify
Ghost published their latest update on their work on adding ActivityPub, with more information about their upcoming beta. Ghost is slowly starting their beta process soon, making it clear that this is indeed a testing program, and data loss should be expected for people who are participating. They also said more about the performance and scaling of Ghost and ActivityPub. Sending out a newsletter over ActivityPub to 5000 subscribers turned out to need 10 servers, which indicates how resource-intensive and expensive ActivityPub can be. As a result, ActivityPub followers will count towards Ghost Pro billing, as Ghost Pro charges based on the number of members an account has.
Fedify, an open-source framework that simplifies building federated server apps, is now officially in version 1.0. Ghost’s ActivityPub integration is build on top of Fedify, and Ghost is sponsoring the Fedify developer as well.
The Links
- Flipboard is connecting another 250 accounts of publishers to the fediverse.
- Bonfire is building a native app, and a series of developer diaries with it.
- The first release candidate for Mastodon 4.3 is now available.
- This week’s fediverse software updates.
- Beyond technical features: why we need to talk about the values of the Fediverse (part 1) – Elena Rossini.
- Mastodon Announces Fediverse Discovery Providers – WeDistribute.
- fedi vs web – on the distinction between social network and social web, where activitypub straddles both.
- Mallory Knodel, the Executive Director for the new Social Web Foundation, writes about the new foundation.
- The Mastodon server strangeobjects.space will shut down, and in the announcement post the admins explain the emotional cost and impact that comes with being a server admin.
That’s all for this week, thanks for reading!
Subscribe to our newsletter!
reshared this
Debbie Goldsmith 🏳️⚧️🏳️🌈⧖ reshared this.
Strypey
in reply to Laurens Hof • • •> Sending out a newsletter over ActivityPub to 5000 subscribers turned out to need 10 servers, which indicates how resource-intensive and expensive ActivityPub can be
I'm interested in the details. I'm guessing Ghost sent out 5000 documents full of bloated HTML markup, big fat images, and tracking cruft. Like people do with email newsletters. If so, not exactly an AP problem.
This is not compulsory, and there may more efficient approaches, requiring much less server power.
(1/2)
Strypey
in reply to Strypey • • •What would make more sense in theory is;
1) get the newsletter payload to lose weight
2a) send only metadata and ASCII text. Then... stop. Nobody needs the rest of the cruft.
2b) send only metadata and ASCII text, and have receiving servers DOFV (Down On First View) for the rest.
With a DOFV approach, timing of heavier downloads is staggered, as people view the post at different times. Instead of hitting the sending server all at once. Also, posts that are never seen, never need to be sent.