In case you missed it, we released a new version of Surf last week, with a redesigned Home. Here are a few cool new Surf feeds to celebrate (and to keep you occupied if you're enjoying a few days off for the U.S. Thanksgiving holiday).

#SurfFeeds #Flipboard #SurfSocial #Apps #ActivityPub #Fediverse

I have deeply mixed feelings about #ActivityPub's adoption of JSON-LD, as someone who's spent way too long dealing with it while building #Fedify.

Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.

But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.

Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.

To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.

Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.

#JSONLD #fedidev

Has anyone figured out how to use ActivityPub to make something IRC or Discord shaped?

#activitypub #irc

Your Home Feed is the inbox of an ActivityPub actor — in particular YOUR ActivityPub actor.

There could be an actor for each hash-tag, too.

You could even do Del.icio.us like things — and have actors for intersections of hash-tags, too.

These hash-tag actors' inboxes would need to be readable by anyone.

...

This could be a more ActivityPub like API alternative to Mastodon's "GET /API/v1/tags/{name}" API.

#ActivityPub #FediDev #FediDevs #Fediverse #HashTag #HashTags

🎤 Speaker Spotlight: Evan Prodromou @evan Co-author of the #ActivityPub protocol at @swf, Evan is a true pioneer of the #Fediverse. Sometimes called "The Father of the Fediverse," he made the first-ever post on the #SocialWeb in May 2008.
🎟️ In-person and streaming tickets: https://fedimtl.ca/

#FediMTL #DigitalSovereignty

🎤 Speaker Spotlight: Julian Lam @julian Co-Founder of @nodebb, an open-source community forum platform with built-in #ActivityPub support, connecting traditional forums to the #SocialWeb.
🎟️ In-person and streaming tickets: https://fedimtl.ca/

#FediMTL #Fediverse #DigitalSovereignty

Reminder to anyone managing a #ActivityPub project that matrix has been adopted as the chat solution by bookwyrm, write.as, friendica, plume, pleroma, fedilab, funkwhale, mitra, forgefed, mobilizon, phanpy, tokodon, moshidon, lemmy, gotosocial, bonfire, voyager, tusky, lemmy, loops, piefed, pixelfed, manyfold, owncast and others. You don't need to start from scratch if you leave discord : join us on matrix!

@Gargron

🎤 Speaker Spotlight: Julian Lam @julian Co-Founder of @nodebb, an open-source community forum platform with built-in #ActivityPub support, connecting traditional forums to the #SocialWeb.
🎟️ In-person and streaming tickets: https://fedimtl.ca/

#FediMTL #Fediverse #DigitalSovereignty

I managed to get 2/3rds of quote posts (FEP-044f) working in #ktistec. The only part remaining is quote posting from the server and this depends on functionality to delay delivery until the quote request is accepted (or not). I need that for scheduled posts, so it's a delay but time well spent!

#activitypub #fediverse

@dansup Can I request a @pixelfed feature to be able to pin a post?

#pixelfed #activitypub #fediverse

Bringing your site to the Fediverse: A practical guide for static sites - Part 1

Summary:

You can find the index and other parts of this series here.

This blog is on the fediverse! You can discover and follow the blog (@blog@maho.dev) and comment on its posts from your Mastodon app.

I spent the last couple of weeks getting this blog onto the social web (aka fediverse), investing an hour here and there (I hope you are reading this from Mastodon, btw). It was fun and a very exciting learning experience, and I want to share not only my reflections but also create a guide so others can do the same, to move the needle a little bit in the right direction.

You can find the index and other parts of this series here.

This blog is on the fediverse! You can discover and follow the blog (@blog@maho.dev) and comment on its posts from your Mastodon app.

I spent the last couple of weeks getting this blog onto the social web (aka fediverse), investing an hour here and there (I hope you are reading this from Mastodon, btw). It was fun and a very exciting learning experience, and I want to share not only my reflections but also create a guide so others can do the same, to move the needle a little bit in the right direction.

First of all, ActivityPub is a very nice idea; I love how much it has grown and the adoption that is growing day by day. I am not an expert in ActivityPub; I am far from being one. My only technical experience can be counted in literally ten days since this first post. But I have grown fond of it, and I am now #TeamActivityPub. So much so that I want to explain to others how to achieve the same on their own sites.

But before explaining how to do it, I want to share my vision of why you should do it. (If you have already decided to do it, you may skip this part).

You may have heard all these nice things about the indieweb, the bad corporations, and privacy. And I agree with almost all of them, but there is also the aspect of innovation which not many times is covered. ActivityPub, the Fediverse, or the SocialWeb are enablers of innovation, and we should make sure others see it. If you want to create a new app, a new social network, or a new product, you don’t need to start from zero to build a user base (or what is harder, a community); you can (and should) just focus on building that thing that adds value.

Bear with me; this is important to explain how to implement ActivityPub on your website. (Because at the end we are not going to implement the whole ActivityPub protocol, just the parts that make sense for you).

As you already know, Mastodon is a microblogging platform, a clone of Twitter, but the underlying protocol/technology, ActivityPub, is much more than that. It describes concepts that repeat in almost all social networks:

1. You can create content, described as a note.
2. You have an identity, or user.
3. You can follow and unfollow other users or people.
4. You can “like” and “reply” to other content.

There are others, but these base 4 concepts repeat themselves in each social network, no matter if it’s MySpace, LinkedIn, or TikTok. These features have been implemented over and over, since Google+ and Orkut where a thing.

That is why ActivityPub is the base of other implementations besides microblogging; take as examples Lemmy (a Reddit clone) and PixelFed (an Instagram clone). They look very different from Mastodon, but they are interconnected (aka federated). This means that I can follow a community from Lemmy, not only with my Mastodon account, but with my Mastodon app. It may be that when I favorite a Lemmy-created link in Mastodon means no more than a thumbs up (for Mastodon), but for Lemmy (remember, a Reddit clone) it can be used to upvote a post. Or a photo of a cat on Mastodon could just be yet another post, but it could be beautifully presented on Pixelfed. I personally want to see the GitHub feed to federate in the socialweb (maybe someone can help to it in GitLab).

But also you do not need to reimplement ActivityPub to create some new instance on a server; you can just consume the APIs on the client side. I can create my own For You algorithm, an app for weather alerts, or a news aggregator (like Google News). Flipboard is a content curation site, for example, and it is interconnected with the socialweb.

And this leads me to your blog, a newsletter, or news site, which also:

1. Publishes content.
2. Has an identity or multiple (for example, a news site could have @tech@nytimes.com, @politics@wsj.com, etc.).
3. You can subscribe to a blog or newsletter (follow/unfollow).
4. You can “like” or “comment” (reply).

Which btw, there is nothing on ActivityPub that says you cannot make your subscriptors (followers) paid-only, a follow request can be accepted after you verify any sort of payment. But the point is that imagine that you won’t need to create yet another account on each newspaper to be able to discuss or comment on their content. Or that you don’t need to create an account on Substack to follow an author. Or that you don’t even need to create a user on Google or Facebook to like a photo.

That is what ActivityPub, the Fediverse, and the Social Web bring: interoperability. This can go further, as in distributed dentity verification (you’ll be able to own your identity across instances), but that is another topic. For now, I want to convince you that if you have a site that publishes content, it should be in the Fediverse and Social Web. If not for principles, for numbers: there is already 2 million active users every month can read, consume, and engage with your content. You don’t need to create a user base, the user base already exists.

It appears that WordPress, Medium, Threads, Flipboard understood this, and with their actions, they are helping to convince others that this is no longer just an ideological matter but a practical one. There are some people who said this may not succeed, but what I have seen is that it has already done.

It may not go mainstream to replace Twitter, but that is not the purpose of the Fediverse. That is not the real question. The question is: how can we harness the power of interoperability to enhance accessibility, engagement, and inclusivity within our online communities and content distribution platforms? By integrating with ActivityPub and embracing the principles of the Fediverse and the Social Web, we open doors to a vast network of users who can seamlessly interact with our content without barriers such as mandatory account creation or platform restrictions.

Moreover, we contribute to the democratization of online spaces, allowing individuals to maintain control over their digital identities and fostering a more decentralized and open internet ecosystem. This not only benefits users but also offers significant advantages for content creators and publishers, as it expands their reach and facilitates meaningful interactions with their audience.

In essence, the question is not whether the Fediverse will replace mainstream platforms but rather how we can leverage its potential to create more inclusive, user-centric online experiences that prioritize accessibility and collaboration. This is the promise of the world-wide-web, interconnected websites, but also interconnected people. And if you site is not part of it, well, then keep reading.

In the next blog post, I will start getting into the details of the implementation. If you are interested, follow this blog (@blog@maho.dev) in the Fediverse/SocialWeb!

P.S. Special thanks to @SmartmanApps for beta-testing the whole thing.

Also readable in: https://maho.dev/2024/02/bringing-your-site-to-the-fediverse-a-practical-guide-for-static-sites-part-1/ by @mapache:

#fediverse #socialweb #mastodon #activitypub #interoperability #openinternet #decentralization #innovation #digitalidentity

The Future Is Federated

...

And will be federated for the amazing work of the amazing people in the fediverse.

One of my fav photos from #fosdem2026

Sweater by @_elena, photo by @sturmsucht

#activitypub #fediverse

@thenewoil
> Tinder looks to AI

The enshittification continues. I remember @evan shared some thoughts about using ActivityPub to develop a federated #dating app. In some ways, it's the ultimate test for UX, onboarding, etc, in federated networks. Some challenges;

* it requires helping people meet within a geographical range

* it requires a critical mass of attractive people using it to attract others (the bootstrap problem dialed up to maximum)

* Trust & Safety are *essential*

#ActivityPub