One of the project areas of the Social Web Foundation for the last year has been end-to-end encrypted messaging. ActivityPub, the standard protocol that powers the Social Web, has privacy controls, but they do not protect the content of messages from server operators. Encrypted messaging has become a common feature on many social networks since ActivityPub was created, and its lack has inhibited Social Web adoption and public trust in the network.ActivityPub is extensible, though. As part of our E2EE program, Mallory, Tom and I adapted the Messaging Layer Security (MLS) standard as an extension of ActivityPub to make the MLS over ActivityPub specification. The protocol fits the great MLS E2EE system onto the ActivityPub API and federation protocol.But a protocol specification is not enough; it must be implemented. That’s why we’re so happy to announce that the Sovereign Tech Fund has commissioned work with the Social Web Foundation to coordinate two new interoperable implementations of MLS over ActivityPub. This investment by the Sovereign Tech Fund will help move the Fediverse towards more privacy for social web users, no matter what server they use.We decided to partner with two different projects in order to make sure that we’re making an open standard that can work between implementations. With two implementers, we’ll need to communicate clearly about architectural and implementation decisions, and make sure that those decisions end up in the final version of the spec — not in a TODO comment in the source code of a single project.The first project is Emissary, the great social web application platform behind projects like Atlas and Bandwagon. Ben Pate, Emissary founder, says, “The Emissary Project is deeply committed to the Fediverse, where we are building a free and trustworthy Internet for all 8 billion humans. Delivering on that promise, Emissary is excited to team up with the Social Web Foundation to bring End-to-End-Encryption (E2EE) to the Fediverse. We are eternally grateful for the SWF’s leadership and support, without which this project could not have happened.  Our work is already underway, and in 2026 anyone will be able to build E2EE applications on the Emissary platform.”The second project is Bonfire. Bonfire is a modular framework for building federated apps, with its first app (Bonfire Social) offering a social networking experience enhanced with tools for privacy, trust, and collaboration (such as circles and boundaries). The maintainers of Bonfire, Ivan Minutillo and Mayel de Borniol, said: “We think that end-to-end encryption should simply be the default for any private communication online. Working with the Social Web Foundation to bring E2EE to ActivityPub marks a crucial step in fostering privacy and trust, and especially in enabling the fediverse to become a safe space for activists and communities to organise, coordinate, and collaborate meaningfully. By making secure, user-friendly messaging a core part of the fediverse, we’re helping lay the groundwork for decentralised networks where people can go beyond talking in the mythical ‘global town square’ and actually organise and accomplish things together.”This work will happen best if the Fediverse community tracks it closely. We’ll be making updates here on the SWF blog as progress continues. Developers and active users may also be interested in the ActivityPub E2EE Messaging Task Force at the W3C, where the specification is being developed into a report for the Social Web Community group. Finally, we’ll be using the #JustBetweenUs hashtag to share progress and ideas, so you can follow it to see what’s been happening.

Follow-up post, a review of federated CMSes that can take over long running sites before Wordpress turns to slop.https://kbin.earth/m/fediverse@lemmy.zip/t/2330341/Recommendations-for-federated-CMS-alternatives-to-Wordpresscc @davidgerard @nspsegal @julian @morph @elfin #wordpress #ActivityPub #CMS #noAI #fediverse

#Introduction - A new home for longer mountain ramblings & tech dabbling!After years on a managed Mastodon instance, I've finally jumped into the #selfhosted world! Say hello to my new personal #ActivityPub instance, powered by #GoToSocial from home.While I test the waters here (and learn all the complexities of managing self-hosting!), this space will be for the longer-form, deeper-dive content:1. Extended mountain trip reports with more photos.2. Ramblings on my rather amateur adventures in #technology, #landscapephotography, #lora mesh networks, #degoogling efforts, and #linuxphone solutions.Think of it as my digital base camp. If you're a mountain person who loves tech (or a tech person who loves mountains), we probably have things in common. Boosts and introductions are welcome!

The other day I was thinking about some of the people who I used to follow in the old blue bird site. A few of them did open accounts here on Mastodon, mostly because it was "trendy" at that time, but most (of those few) eventually left their accounts to rot. A lot of people from the old site just eventually ended up in Bluesky, but they are not even bridging here (I even asked, they ignored me).Whatever their reasoning was, they lost followers one way or another, for sure. And now I have met new people, I have been following them, and some of those are following me back, which was unthinkable in the old site.Time flies when we're having fun, and the past just becomes a blur.#Mastodon #ActivityPub #Hachyderm

Finally federated!After a truly ridiculous amount of stubbornness, debugging, and duct-taping containers together, my Ghost blog is now fully ActivityPub enabled.You can now follow my blog directly from the fediverse:@laura@blog.laurahargreaves.com #Fediverse #ActivityPub #OpenWeb #SelfHosting #Ghost #IndieWeb #FediTech

Sommaire du Guide MastodonSommaire du guide d’utilisation et tutoriel non-officiel de Mastodon en français, mis à jour régulièrement pour suivre les nouveautés ou changements des nouvelles versions.https://www.didiermary.fr/sommaire-du-guide-mastodon/#ActivityPub #Fediverse #Mastodon #Microblogging

dsddsdsfdsfsd

#OpenScience and the #fediverse .. let's get that ball rolling @jfietkau @jonny and @bonfire opened a brainstorm and evaluation on how we can provide better support for the academic world and #science in general to the #ActivityPub-based fediverse.Various different iniitiatives are underway, and there's great opportunity to bundle forces and align these efforts where possible. Set standards.Interested? Join the discussion:https://discuss.coding.social/t/my-current-goals-for-activitypub-and-academic-data/750#LinkedData #SemanticWeb #JSONLD #RDF

A response to this post.

asdasdasdsadas

Welcome to your brand new NodeBB forum! This is what a topic and post looks like. As an administrator, you can edit the post's title and content. To customise your forum, go to the Administrator Control Panel. You can modify all aspects of your forum there, including installation of third-party plugins. Additional Resources NodeBB Documentation Community Support Forum Project repository

Publicacion scheduled for monday 2025-02-03 18:00Dear studi0 communityWe decided to add an #element #matrix #privateSpace #chatRoom to our setup and called it: tupambaeORGstudi0Please be patient in any case as this is complete #Neuland for the admin in charge.At least he managed to onboard a filmmaker, photographer and writer as the first step to understand how invites work!So, hi there!.. self-hosting based in Paris, France newbie @ elena@aseachange.com, director of The Illusionists documentary and #FOSDEM2025 traveler for your new proyect: #TheFutureIsFederatedThe one who host's here photos apparently at @ ele@photos.elenarossini.com.To begin with we created 3 rooms: studi0 communityAPP tutorialsand as the first officialy approved project@jesuisatire managed to trigger:Projekt wahlKarnavalKrampf #foFritzMertzIn the @edit profile we creatd already a postString for that Projekt with a very limited time horizon.Next step will probably be creating a activityPub #podcast handle on cast.tupambae.com by @utopiarte, the admin over there, as content colection and conversation about the idea itself in the EDITing post is already up and running.Part of the details concerning the cast domain is to figure out how to organize the tools #castopod gives us at hand as it looks like it has quite interesting options to organize cooperation, as stated briefly in a tutorial page created on that site, result of the #learningBYdoing process while installing it: brief Castopod tutorialLast but not least, we are still trying to drag @lizzischmidt the creator and promotor of the #sundayGimp community experience that is alive and running for over a decade on #diaspora* on to our shores, but federation with diaspora, from a technical point of view, definitely has seen better times in the past. Maybe this very cross community chat option, added right here and now, can help to improve the communication for all of us.This inicial publication will federate quite well out into the vast space of the #fediVerse, but to see comments from the diaspora bubble and the #activityPub sphear, youll have to visit this original page on this friendica server.Unless of course you are friendican yourself.So, with no more further introduction, let's jam the #fediFolks!tube.tchncs.de/w/u7q2ddpNfv6cU…

A few facts and thoughts about #BlueSky being decentralized or not:#ATProto (the protocol behind bluesky) is decentralized and open-source, but is controlled by a for-profit (albeit fiscally a public benefit) organization, "Bluesky Social PBC"."Bluesky" refers to a sum of ATProto concepts, notably the AppView (bsky.app), the main Personal Data Servers (PDS, bsky.social), and the Relays (or firehose, bsky.network). There are others, but they're the 3 important ones.Anyone can run their own AppView, PDS or Relay AND consume the content from/get their content consumed by the Bluesky infrastructure. HOWEVER, not everything is trivial or cheap to run.3.0 A PDS, which contains your data (account details but also posts, likes, follows, etc), is trivial and cheap to self-host. Cheaper than hosting a mastodon instance, even, because it does way less stuff and receives way less requests. See https://github.com/bluesky-social/pds3.1 An AppView (the presentation layer, where users interact with ATProto content) can be created by anyone, but the bsky.app backend is NOT open-source, so there are not a ton of options right now.EDIT: seems like I was wrong and that the bsky.app AppView is open-source: https://github.com/bluesky-social/atproto/tree/main/packages/bsky3.2 Running a relay is trivial but expensive to self-host. This is because its purpose is to act as an aggregator for all the PDS so that AppViews can consume the data in a way that scales better. The Bluesky relay implementation (bigsky) is open-source: https://github.com/bluesky-social/indigo/blob/main/cmd/bigsky/README.mdAbout 2.5 months ago, 4.5TB of storage was needed and an OVH server costing 150$/month worked to host a full-atmosphere relay (more on that later).4.0 To make a comparison with #ActivityPub (the protocol behind #mastodon ), the AppView and PDS is the same thing in ActivityPub, and the concept of relay doesn't exist. There are advantages and drawbacks to both architectures, I might do a future post highlighting those.5.0 With those definitions out of the way, some observations:5.1 A lot of users self-host their PDS, but the vast majority of users chose the simpler option.5.2 There are some alternative AppViews built on ATProto, but the vast majority of users visit bsky.app.5.3 There are very little non-bluesky self-hosting of relays, mostly because of their prohibitive cost. Running the bigsky relay is expensive partly because of design decisions for ATProto and partly because it takes ALL content from ALL accounts for ALL the network on the atmosphere (in this case atmosphere == fediverse but for ATProto). This is like if your Mastodon instance queried ALL servers for ALL accounts querying ALL posts. In the future, there might exist relays that don't scrape ALL data but only a subset of it, which would bring down costs, but it's not yet the case.6.0 So "is Bluesky decentralized?"6.1 In theory, yes, everything that bluesky does on ATProto can be.6.2 In practice, however, the most decentralized part of Bluesky is the PDS, where the user data is stored, and even that is not that decentralized.6.3 Will it stay this way? I'm hopeful it won't, but I don't know. ATProto is fairly new compared to ActivityPub, and the ecosystem around it was mostly built by the BlueSky company, but I expect this to change in the future. However, the cost of entry for things built on ATProto will always be more than the cost of entry for things built on ActivityPub.6.4 Things built on ActivityPub will always be more decentralized than things built on ATProto, because of design decisions from both of these protocols.

Hi all,For the past year I've been working on an activitypub federated instant messenger called Shoot.I haven't had time to work on it for a while because of my job, so I'm making it public to see if anyone would be interested in helping out.You can find the server repo here: https://github.com/MaddyUnderStars/shootand the client repo here: https://github.com/MaddyUnderStars/shoot-clientFeatureset currently includes:- Dm channels- Friends/relationships- Guilds- Guild channels- Guild invites- Voice calls (not yet federated)- Mostly working federation with itself- Iffy federation with other platformsThere's no official instance yet, but I could host one if there is interest.What I need help with most is:- Frontend development. The client code is very hacky and gross, let alone the UI haha- Safety features- Probably general architecture stuffThanks all#activitypub

Jag tänker göra en sån #introduktion / #introduction (igen, jag kommer inte ihåg om jag gjorde det förut faktiskt).Hej Jag heter Jessica Tallon, och jag jobbar med peer-to-peer-teknologi och hjälpte till som medförfattare på #activitypub. Jag jobbar på Spritely Institute, där vi försöker bygga och standardisera framtidens sociala medier (bland annat).När jag inte är vid datorn tycker jag om att vandra, plocka svamp, odla och läsa lite.Jag flyttade kontot hit från @tsyesika@octodon.social

The federated experiment for this blog has begun. This is a public blog though sensitive content will be marked with a content warning both in HTML and when distributed. All remote posts to a blog post will go into the approval queue for comments.I have an internal aggregator feed for each person/bot I will follow, and hopefully that will inspire me to write blog posts in reply to those in my feed. I have not implemented receiving posts directly, and most-likely, if I do, those will go in as feed items somehow. However I probably won't implement private messages so please don't be offended if I don't reply privately.I do have inbox forwarding, which I think I have implemented correctly, and we'll see how other instances deal with what I forward.

One downside to Mastadon for me so far: the servers I join keep shutting down. I figure joining the main place will increase my odds of longevity! Also got #activitypub going on my #wordpress website, but still haven't configured after installing last year I guess I'm just usually adverse to all social no matter who runs the platforms But I'd also love to see the fruition of a truly open web, so 'be the change you wish to see'.

@evanprodromou I wish we'd also had a url handle to deal with everything. like web+ap:// but supported by everyone and used for everything, not just links.https://fedilinks.org/spec/en/6-The-web-ap-URI

@blog Another apparent i18n limitation in the Fediverse is that hashtags have an extremely limited character set.

Part 3 of "A Guide to Implementing ActivityPub in a Static Site (or Any Website)" is just out the oven!In this blog post, I explain how to make your blog discoverable in the Fediverse as an account, and also address some of the annoying pitfalls I encountered. Full article here: https://maho.dev/2024/02/a-guide-to-implementing-activitypub-in-a-static-site-or-any-website-part-3/If you like it don't forget to follow the @blog !#fediverse #activitypub #static-sites #hugo #azure #mastodon #web-development #social-web #webfinger #http