Loo kontoLogi sisse

Viimatised otsingud

Pole viimatisi otsinguid

Otsimisvalikud

Saadaval vaid kui sisse logitud.
est.social on üks paljudest sõltumatutest Mastodoni serveritest, mida saab fediversumis osalemiseks kasutada.
est.social on mõeldud Eestis üldkasutatavaks Mastodoni serveriks. est.social is meant to be a general use Mastodon server for Estonia.

Administraator:

Serveri statistika:

95
aktiivsed kasutajad

est.social: TeaveProfiilikataloogIsikuandmete kaitse

Mastodon: TeaveTõmba äppKiirklahvidLähtekoodv4.3.4+est

#activitypub

46 postitusega43 osalejaga0 postitust täna
Avalik
Robert Kingett

Hey all, the easiest way I can find #Ghost blogs using #ActivityPub is to search for @index and you will get some Friendica results, etc, but for now, that should be a sure way to find almost all the blogs that have enabled this feature so far. I couldn't tell if replies appear as comments, so if you don't want your comments on their blog, don't reply to their fediverse posts. A few told me they can see my comments on their dashboard but I don't know what that means. #FediTips #Fediverse

Avalik
David Fleetwood

If you claim to be a leftist and you are trying to convince people to move to #BlueSky rather than the community driven #ActivityPub options (#mastodon / #PixelFed / etc) I cannot take you seriously as a leftist.

A major component of leftist thought is community organizing and defense. It is opposition to centralized power and control. Intentionally helping people move or set up on centralized systems, regardless of what their CEO's claim about them, is directly in opposition to leftist ideals.

Yes some people are sometimes confused by the #Fediverse options. It's your job to help them find an appropriate community and work through the technical hurdles. The platforms they are moving away from, such as #Twitter, #Facebook & #Instagram were all confusing and overwhelming for people when they first joined. This is no different, it's always a learning curve.

Actually help and protect your communities by helping them not only escape corporate controlled networks but also by helping them find and utilize networks that are community run, moderated and controlled.

Avalik
The Real Grunfink
I'm glad to announce the release of version 2.74 of #snac, the simple, minimalistic #ActivityPub instance server written in C. It includes a lot of web UI translations by lovely people and a bit of minor tweaks and fixes:

Added Spanish (default, Argentina and Uruguay) translation (contributed by gnemmi).

Added Czech translation (contributed by pmjv).

Added Brazilian Portuguese translation (contributed by daltux).

Added Finnish translation (contributed by inz).

Added French translation (contributed by Popolon).

Added Russian translation (contributed by sn4il).

Added Chinese translation (contributed by mistivia).

Added German translation (contributed by zen and Menel).

Added Greek translation (contributed by uhuru).

Added Italian translation (contributed by anzu).

Mastodon API: added support for /api/v1/custom_emojis (contributed by violette).

Improved Undo+Follow logic (contributed by rozenglass).

Reverted (temporarily) the Markdown code that converted text between underscores to italics, because it was causing more problems that what it was worth.

Fixed bug in bookmark CSV import.

Don't indent Twitter-like "threads" (i.e. chains of short posts from the same author that are self-replies).

https://comam.es/what-is-snac

If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/

#snacAnnounces
Summary card of repository grunfink/snac2
Forgejo: Beyond coding. We Forge.snac2A simple, minimalistic ActivityPub instance written in portable C
Jätkatud lõim
Avalik
Fedify: an ActivityPub server framework

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

As we discussed in our previous post, Fedify currently creates separate queue messages for each recipient. While this approach offers excellent reliability and individual retry capabilities, it causes performance issues when sending activities to thousands of followers.

Our solution? A new two-stage “fan-out” approach:

  1. When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
  2. A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

  • Context.sendActivity() returns almost instantly, even for massive follower counts
  • Memory usage is dramatically reduced by avoiding payload duplication
  • UI responsiveness improves since web requests complete quickly
  • The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

  • "auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
  • "skip": Bypasses fanout when you need different payload per recipient
  • "force": Always uses fanout even with few recipients
// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

Flowchart comparing Fedify's current approach versus the new fan-out approach for activity delivery. The current approach shows: 1. sendActivity calls create separate messages for each recipient (marked as a response time bottleneck) 2. These individual messages are queued in outbox 3. Messages are processed independently 4. Three delivery outcomes: Recipient 1 (fast delivery), Recipient 2 (fast delivery), and Recipient 3 (slow server) The fan-out approach shows: 1. sendActivity creates a single message with multiple recipients 2. This single message is queued in fan-out queue (marked as providing quick response) 3. A background worker processes the fan-out message 4. The worker re-enqueues individual messages in outbox 5. These are then processed independently 6. Three delivery outcomes: Recipient 1 (fast delivery), Recipient 2 (fast delivery), and Recipient 3 (slow server) The diagram highlights how the fan-out approach moves the heavy processing out of the response path, providing faster API response times while maintaining the same delivery characteristics.
#ActivityPub#fedidev
Avalik *
Chuck Darwin

Newsletter platform #Ghost, an open source competitor to #Substack, is now connected to the fediverse, also known as the open social web.

Federated apps run on the protocol #ActivityPub, which powers apps like Mastodon, Pixelfed, Threads, Flipboard, and others,
allowing posts published on one app to be seen and engaged with by those on other federated platforms.

Ghost said last year that it was working on an integration with ActivityPub, which would allow its publishers to share their blog posts with the broader open social web.

The company expected the integrations to go live last year. However, Ghost this week announced the launch of its social web beta, which now allows any site running on its Ghost Pro subscription to try out the new ActivityPub integration.

The beta feature is still in active development, the company notes in its help documentation, but is expected to ship in a more finalized state in the Ghost 6.0 release.

When Ghost Pro users connect their blog or newsletter to the fediverse, others across the open social web will be able to follow their account’s handle.

This handle is a combination of “@index,” representing the home page of the publication, followed by the domain name (@yoursite.com).

Ghost says users will soon be able to customize the @index part of their @index@yoursite.com handle.

Users on federated apps will then be able to follow the Ghost publisher’s posts, as well as interact with them by liking, replying, or reposting.

To help Ghost publishers also participate in the fediverse and build their readership,
Ghost also launched a social web reader.

Here, users can browse a “feed” of the short-form content shared across the fediverse, including posts from services like Mastodon and Threads.

In a separate area called the “Inbox,” Ghost users can keep up with long-form content, like articles published on Ghost or WordPress, the popular publishing platform that integrated with the fediverse in 2023.

“Think of the Inbox screen like your email inbox. When you follow other publications on the social web, new articles they publish will show up here,” Ghost’s help page explains.

“Clicking on a post will open an inline reader view, right inside Ghost,
and when you get to the end you’ll be able to like, repost or reply.”

With the integration of these two feeds into Ghost’s admin, Ghost will also now allow its publishers to directly post short-form content to the fediverse, helping them to build their reputation and following on the open social web.

Ghost’s Reader also alerts users of interactions like follows, replies, likes, and reposts in its “Notifications” section.

Plus, users can customize their Profile page to offer a preview of their social web account,
following/followers, and their content, both short and long-form.

Later, the company hopes to more deeply integrate users’ social web profiles with Ghost memberships,
but for now, they operate independently from one another.

Other coming features include tools to block, report, and mute people or add images or media to notes and replies.
techcrunch.com/2025/03/19/subs

TechCrunch · Substack rival Ghost is now connected to the fediverse | TechCrunchNewsletter platform Ghost, an open source competitor to Substack, is now connected to the fediverse, also known as the open social web. Federated apps run
Jätkatud lõim
Avalik
Fedify: an ActivityPub server framework

We've been working on adding custom background task support to #Fedify as planned for version 1.5.0. After diving deeper into implementation, we've realized this is a more substantial undertaking than initially anticipated.

The feature would require significant API changes that would be too disruptive for a minor version update. Therefore, we've decided to postpone this feature to Fedify 2.0.0.

This allows us to:

  • Design a more robust and flexible worker architecture
  • Ensure better integration with existing task queue systems
  • Properly document the new APIs without rushing

We believe this decision will result in a more stable and well-designed feature that better serves your needs. However, some smaller improvements from our work that don't require API changes will still be included in Fedify 1.5.0 or subsequent minor updates.

We appreciate your understanding and continued support.

If you have specific use cases or requirements for background task support, please share them in our GitHub issue. Your input will help shape this feature for 2.0.0.

NoteWe've decided to postpone custom background task support to Fedify 2.0.0 instead of 1.5.0 as originally planned. This feature requires significant API changes that would be too disruptive for a...
GitHubSupport custom background tasks in worker · Issue #206 · fedify-dev/fedifydahlia poolt
#ActivityPub#fedidev
Avalik
Fedify: an ActivityPub server framework

Patch releases for #Fedify versions 1.0.21, 1.1.18, 1.2.18, 1.3.14, and 1.4.7 are now available. These updates address two important bugs across all supported release lines:

  1. Fixed a WebFinger handler bug that prevented matching acct: URIs with port numbers in the host. Thanks to @revathskumar for reporting and debugging the bug!
  2. Resolved server errors that occurred when invalid URLs were passed to the base-url parameter of followers collections.

We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.

Released on March 20, 2025. Fixed a bug of WebFinger handler where it had failed to match acct: URIs with a host having a port number. [#218, #219 by Revath S Kumar] Fixed a server error thrown...
GitHubRelease Fedify 1.0.21 · fedify-dev/fedifyReleased on March 20, 2025. Fixed a bug of WebFinger handler where it had failed to match acct: URIs with a host having a port number. [#218, #219 by Revath S Kumar] Fixed a server error thrown...
#ActivityPub#fedidev
Jätkatud lõim
Avalik
洪 民憙 (Hong Minhee)

今回、@lqez さんの『我々のコードを求めて』というYouTubeに出演させていただき、#フェディバース、#ActivityPub、#Fedify、#Hollo 等についてお話させていただきました。日本語字幕が用意されていますので、FedifyやHolloの開発秘話などが気になる方はぜひご覧ください！

https://www.youtube.com/watch?v=sqxR8zscSDo

YouTube우리의 코드를 찾아서 – 2막. 민희님과 Fedify & Hollo 알아보기하루개발 by @lqez poolt
#fediverse#fedidev
Avalik *
Robert Kingett

Link at end but I am amused by the replies and discourse to this article for the bafflement regarding the existance of small Fedi, Fedi users that don’t want to interact with the whole of users. Small Fedi has people that honestly just want to be left the fuck alone. The more tech minded of the Fedi, big Fedi, as described here, is astonished such a thing could exist and my sides are splitting from them realizing not everybody wants to talk to you. wedistribute.org/2025/03/websi #Fediverse #ActivityPub #privacy

Excerpt of "The Sinking of the USS President Lincoln" by Frederick Dana Marsh
We Distribute · Website League and the Rise of Island Networks - We Distribute
Veel kasutajalt We Distribute
Avalik
Fediverse Report

New: Fediverse Report #108

This week's news:
- Ghost's (@index) connection to the #fediverse is now availabe in public beta for Ghost Pro users, with both an #ActivityPub connection to send long-form posts into the fediverse, and a reader app to read/comment/interact with the fediverse
- @anewsocial , the organisation that manages the bridge between the fediverse and #bluesky shared their upcoming plans

Read at: fediversereport.com/fediverse-

fediversereport.com · Fediverse Report #108
Veel kasutajalt Laurens Hof
Avalik *
洪 民憙 (Hong Minhee)

이番(번)에 @lqez 님의 《우리의 코드를 찾아서》에 出演(출연)하여 #페디버스, #ActivityPub, #Fedify, #Hollo 等(등)에 關(관)해 이야기를 나눴습니다. Fedify와 Hollo의 開發(개발) 祕話(비화) 같은 게 궁금하시다면 한 番(번) 보셔도 재밌을지도 모르겠습니다. ㅎㅎㅎ

https://www.youtube.com/watch?v=sqxR8zscSDo

YouTube우리의 코드를 찾아서 – 2막. 민희님과 Fedify & Hollo 알아보기하루개발 by @lqez poolt
#연합우주#fediverse#fedidev
Avalik
Surf

Well, it’s a lucky day 🍀. Our latest update contains a pot o’ gold for the Bluesky community especially. Take a look at what’s in this release, including linking your Bluesky account to Surf, a new Home Timeline that unifies your Bluesky and Mastodon, and Bluesky notifications in our app. 🦋

App release notes for Surf update week of March 17, 2025. This is post 1 of 2, and it says: Link your Bluesky account in Surf settings! New Home Timeline unifies your Bluesky & Mastodon Post & engage with your Bluesky community See your Bluesky notifications in Activity Access your Bluesky lists, starter packs & custom feeds from your profile
App release notes for Surf app week of March 17, 2025. This is post 2 of 2 and it says: Bluesky Digest is renamed Bluesky Following Check out feeds from the community in the new Surf Shop destination Tired of the Elon news? Tame your timeline by excluding hashtags, topics & people in your custom feeds (See Filter & Sort tab in Feed Settings)
#bluesky#mastodon#ATProtocol
AvastaLaiv lõimed
Teave