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

if there was mitra with the entire feature set of mastodon it would be crazy.

General Discussion
4 3 2

Gli ultimi otto messaggi ricevuti dalla Federazione
  • read more

  • @julian @kopper the world if we used sioc:UserAccount and sioc:Post instead of as:Person and as:Note (or heck, toot:Account and toot:Status... or atom:feed and atom:entry...)

    or alternatively, if people used activitystreams to actually model social activities...

    i've come to the stance that activitystreams trying to spec out vocab for Note and Article and so on was a distraction from what it was actually trying to do. it should have reused existing vocabs for that stuff, or left it unbounded.

    read more

  • @kopper @thisismissem in a more sensible world, interoperating with mastodon would use a vocabulary that more closely describes what mastodon is actually doing. like, if mastodon operates on "accounts" and "posts" then why not use a standard vocab that actually call them that? activitystreams was built on "activities" and "actors", which is a semantic mismatch for mastodon's model (activities are unwrapped for their side effects and then discarded, instead of being rendered directly)

    read more

  • @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 specs

    yes 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).

    read more

  • @fox I have a Mastodon account for testing but I don't run an instance myself.

    Mastodon is usable but yeah I think Pleroma and Misskey are better.

    >entire feature set of mastodon

    If you want something, open an issue.

    @julian

    read more

  • @kopper right, I think we're saying the same thing overall. But everyone wants ideal compatibility with Mastodon, which then acts as a forcing function on them needing to support more things, which isn't great because obviously limited resources.

    The goal seems to tend to be "interoperability with Mastodon" not "optimal federation via ActivityPub"

    read more

  • @thisismissem re-reading my post i feel like it's a bit confusing what i'm talking about so let me clarify: "everything is a Note" is not the thing i'm saying is "fine". but Mastodon's behavior of simply placing a title and a link for anything it doesn't understand, in my opinion, is perfectly OK.
    read more

  • @kopper so I'm not saying everyone should support everything, in fact, it's perfectly fine to have a decentralized ecosystem where one account enabled you to publish multiple different things.

    Striving for interoperability with just the dominant software in the protocol doesn't result in good outcomes. It results in a reduction of interoperability.

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    3 Views
    We were excited to see the recent release of Ghost 6 with ActivityPub features. The Ghost team have been an active participant in our Long-form Text project. John O’Nolan, founder and CEO of Ghost.org, was kind enough to answer our questions about the software and its community.SWF: For our readers who don’t know Ghost, how would you describe the platform?JO: Ghost is an independent publishing platform for people who take writing seriously. We’re open source, non-profit, and built to give creators complete ownership of their content and their audience. We’ve helped indie publishers generate over $100 million in revenue from sustainable modern media businesses like 404Media, Platformer and Tangle News.SWF: Tell us about your user community. Can you paint a picture of them with a broad brush? What kind of people choose Ghost?JO: Ghost attracts people who care about owning their home on the internet, rather than having another profile on a social media platform. Our publishers range from solo journalists and creators, to established news outlets and large businesses. They value independence, and they’re willing to do the work to maintain control of their brand, distribution, data, and relationship with readers.SWF: What is it like to be a Ghost user in 2025? What kind of problems are your users facing today?JO: The big challenge today is the same one that’s haunted independent publishers for two decades: discovery. You can own your platform and serve your audience beautifully, but if people can’t find you, none of it matters. Email newsletters have been a solid answer, but they’re still dependent on deliverability and inbox placement. Algorithms on social platforms actively suppress links now, so sharing your work there is like shouting into a hurricane.SWF: Tell us about your experience with ActivityPub. Why did you decide to add ActivityPub support to your software?JO: Ghost has had support for delivering content by email newsletters for a number of years, and email has remained an unassailable distribution platform for publishers because it’s an open protocol. No company controls your email list except you, so it’s one of the best investments you can make. ActivityPub is now doing the same thing for social technology. It allows publishers to own and control a distribution channel that allows their work to spread and be discovered by others. For the first time, you can publish independently and grow faster than ever before.SWF: What stack is Ghost built on? What development tools does your team use?JO: Ghost is all built in modern JavaScript; mainly Node and React. Our ActivityPub service is built on Fedify, and everything we build is released under an open source MIT license. Our development tools are constantly evolving, and now more quickly than ever before with the advent of AI tools, which seem to change on a near weekly basis.SWF: What was the development process like?JO: Challenging, honestly. ActivityPub is beautifully designed but the spec leaves room for interpretation, and when you’re building something new, there’s no roadmap. Building interoperability between other platforms, who’ve all interpreted the spec in their own unique ways, has been a real challenge. The approach we took was to ship early versions as quickly as possible to beta testers so we could learn as we go, using real-world data and issues to guide our process. We’re in a good spot, now, but there’s still a lot to do!SWF: Ghost produces long-form blog posts, articles and newsletters. How was the experience adapting Ghost articles to the microblogging interfaces of Mastodon and Threads?JO: In some ways really easy, and in other ways quite tricky. We’re at a pretty early stage for long-form content on ActivityPub, and the majority of other products out there don’t necessarily have interfaces for supporting it yet. The easy part is that we can provide fallbacks, so if you’re scrolling on Mastodon you might see an article title and excerpt, with a link to read the full post – and that works pretty well! The dream, though, is to make it so you can just consume the full article within whatever app you happen to be using, and doing that requires more collaboration between different platforms to agree on how to make that possible.SWF: You’ve been an active participant in the ActivityPub community since you decided to implement the standard. Why?JO: ActivityPub is a movement as much as a technology protocol, and behind it is a group of people who all believe in making the web a weird, wonderful open place for collaboration. Getting to know those humans and being a part of that movement has been every bit as important to the success of our work as writing the code that powers our software. We’ve received incredible support from the Mastodon team, AP spec authors, and other platforms who are building ActivityPub support. Without actively participating in the community, I don’t know if we would’ve gotten as far as we have already. SWF: Ghost has implemented not only a publishing interface, but also a reading experience. Why?JO: The big difference between ActivityPub and email is that it’s a 2-way protocol. When you send an email newsletter, that’s it. You’re done. But with ActivityPub, it’s possible to achieve what – in the olden days – we fondly referred to as ‘the blogosphere’. People all over the world writing and reading each other’s work. If an email newsletter is like standing on a stage giving a keynote to an audience, participating in a network is more like mingling at the afterparty. You can’t just talk the whole time, you have to listen, too. Being successful within the context of a network has always involved following and engaging with others, as peers, so it felt really important to make sure that we brought that aspect into the product.SWF: Your reader is, frankly, one of the most interesting UIs for ActivityPub we’ve seen. Tell us about why you put the time and effort into making a beautiful reading experience for Ghost.JO: We didn’t want to just tick the “ActivityPub support” checkbox – we wanted to create something that actually feels great to use every day. The idea was to bring some of the product ideas over from RSS readers and kindles, where people currently consume long-form content, and use them as the basis for an ActivityPub-native reading experience. We experimented with multiple different approaches to try and create an experience with a mix of familiarity and novelty. People intuitively understand a list of articles and a view for opening and reading them, but then when you start to see inline replies and live notifications happening around those stories – suddenly it feels like something new and different. SWF: If people want to get a taste of the kind of content Ghost publishers produce, what are some good examples to follow?JO: Tough question! There are so many out there, and it really depends on what you’re into. The best place to start would be on ghost.org/explore – when you can browse through all sorts of different categories of creators and content, and explore the things that interest you the most. SWF: If I’m a Fediverse enthusiast, what can I do to help make Ghost 6 a success?JO: Follow Ghost publishers and engage with their content – likes, replies, reposts all help! Most importantly, help us spread the word about what’s possible when platforms collaborate rather than compete. And if you’re technical, our ActivityPub implementation is entirely open source on GitHub – contributions, bug reports, and feedback make the whole ecosystem stronger.
  • 0 Votes
    1 Posts
    3 Views
    Checking out Bonfire's latest release. This Federation Status dashboard is pretty cool. And get this - it's not just visible to admins - end users can see the same, just filtered to their OWN processes.That's really helpful if you're trying to debug an issue with another platform development team.#ActivityPub #Bonfire
  • 0 Votes
    5 Posts
    13 Views
    @pfefferle Thanks, Mr. ActivityPub. I'll have an eye on that.
  • 0 Votes
    1 Posts
    1 Views
    Transparency update: Web framework integration progress We're sharing a public project board to track our progress on web framework integrations for #Fedify, work commissioned by the Sovereign Tech Fund (@sovtechfund@mastodon.social). You can follow along at: https://github.com/orgs/fedify-dev/projects/1 About this work The Sovereign Tech Fund invested in Fedify to expand its ecosystem through official integrations with popular web frameworks. This investment enables developers to add federation capabilities to their existing applications without changing their technology stack. Notably, some of these integrations were completed between our initial application submission and the official kickoff of the #STF investment. This demonstrates both our commitment to the project and the community's active development momentum. Current status Already completed: Next.js integration supporting both App Router and Pages Router (completed before STF kickoff) Elysia integration optimized for the Bun ecosystem (completed before STF kickoff) In progress: Fastify integration (PR currently under review) Upcoming: Koa integration Comprehensive documentation for all integrations Why this matters These integrations make Fedify accessible to developers across different JavaScript ecosystems and runtime environments. Each integration follows established patterns from our Express and h3 integrations, ensuring consistency and ease of adoption. Investment details Fedify has been awarded a service agreement by the Sovereign Tech Fund for this work, with a budget of €‎32,000 and completion target of November 30, 2025. The Sovereign Tech Agency supports the development, improvement, and maintenance of open digital infrastructure through investments like this. We believe in transparent development and welcome community input and contributions. #ActivityPub #SovereignTechFund #opensource