Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Week in Fediverse 2025-12-12

Fediverso
1 1 8

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    8 Views
    I think I have identified a fairly significant flaw in how the #Fediverse currently operates. Hear me out.The Fediverse currently consists of all sorts of different systems - #Mastodon, #Friendica , #Pixelfed , #PeerTube, #BookWyrm , and so forth. And while they are all connected via the #ActivityPub protocol, they all have different functionalities and different ways of presenting themselves. Which is as it should be, because Diversity Is Our Strength(TM).However, it is here that the ActivityPub-based interactivity hits its limits - for usually, you can either experience the relevant system as it was intended, or you can interact with it, but not both - _unless_ you have an account on the same system (though not necessarily on the same instance).Let's say that you are a Mastodon user who looks at another person's BookWyrm page. You scroll through their books, posts, and comments. Then you see some comment you want to comment on yourself, but can you do so?Not directly. You need to figure out the URL of their comment, and then copy and paste that comment into the search bar of your Mastodon instance. Then it will show up in the same format as a Mastodon post, and you can interact with it - boost it, like it, comment on it.Sure, it works, but it's a whole lot of tedious effort.Or you can search for the user account in Mastodon and scroll through all their posts and comments as if they were a Mastodon user - and thus, you will miss out on all the unique user interface features of BookWyrm.So what is missing?Well, Mastodon already has an "Open original page" feature when looking at someone's post. What we need is an "Open original page AND AUTHENTICATE" feature. This way, the target instance (whatever software they are using) could acknowledge the viewer as an external user who could nevertheless fully interact with the local user interface, including the ability to boost, like, and make comments.This is something that should be theoretically possible to implement, right? #FediHelp
  • 0 Votes
    2 Posts
    13 Views
    fedigarden@social.growyourown.services I would like to submit ActivityPub.space to this list but I am unable to comply with Threads defederation. We are topic-focused around AP development and would not want to exclude those developers outright. There are occasionally discussions about Threads/AP interop that could be useful and on-topic. It'd be like closing off discussion about ATProto/AP discussion by blocking BridgyFed. I could consider something like an opt-in for that domain?
  • 0 Votes
    11 Posts
    74 Views
    @evan @phi > We have some ad hoc ways to move from one to the other, but they aren't built into the SMTP or IMAP specsyes they are, though? in IMAP, you can just copy your messages and folders from one inbox to another. in SMTP, we have email forwarding.using your own DNS name can make things easier, but the main challenge in fedi is that we don't have a common storage/access abstraction (equivalent to IMAP folders), and we don't recognize HTTP redirects (equivalent to SMTP forwarding).
  • 0 Votes
    1 Posts
    9 Views
    Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics. It's headless, meaning you can use existing #Mastodon client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use #Markdown in the content of your posts and you can quote another post. Oh, and Hollo is built using #Bun and #Fedify. https://github.com/dahlia/hollo #fedidev