🆕 blog! “Rebuilding FourSquare for ActivityPub using OpenStreetMap”
I used to like the original FourSquare. The "mayor" stuff was a bit silly, and my friends never left that many reviews, but I loved being able to signal to my friends "I am at this cool museum" or "We're at this pub if you want to meet" or "Spendi…
I and others have talked a lot about the #Facebook / #Meta#FediVerse issue over the past few days, analyzing their strategy, and possible responses, and why pre-emptive blocking isn't an effective measure.
This leaves the question of "what should we do?" So....
ITT: actually effective measures for building the resilience of the FediVerse and #ActivityPub, informed by the experience of the #OSS movement.
what do we have to do to make the #ActivityPub plugin attractive to more #WordPress users? We are currently at 4000+ active users on WordPress.org + the WordPress.com users.
So its done! I finally released a fairly easy to install (from scratch) Hugo based Static Site generator with full ActivityPub support.
It has step-by-step instructions on how to set it up for your own blog or static website.
One of the coolest features for me, other than having your static site blog posts show up as posts in the Fediverse is the support for interacting with those posts. Any replies you leave, likes, or boosts will show up in the "comments" section of the website on the page associated with the post. How cool is that!
For #ActivityPub the question of "Why use #LinkedData?" has never been answered. There should be clear merits to wade through all the complexity that this choice brings, right?
Yes, its ultra flexible, and you can define your own semantic #ontologies, and theoretically it could provide a robust extension mechanism to AP protocol. Except that right now it doesn't.
What's the vision of a Linked Data #Fediverse? What great innovative #SocialNetworking#UX would it bring, that makes it worthwhile?
Threads now has a Supplemental Privacy Policy (https://help.instagram.com/515230437301944) regarding "Third Party Services" like Mastodon. Should Threads interconnect with Mastodon via #ActivityPub, this addresses what they will do with our data.
Note that they will collect information from anyone "allowing Threads users to follow you or interact with your content". The information they collect will include your profile, your content, and your interactions.
It always amazes me in how in discussions of the future of #ActivityPub services that moderation is generally an afterthought.
Okay, we add nomadic identity, how does that impact the ability for servers to moderate, given all moderation tooling is built on user + server identity?
Okay, we add the ability to put people on lists without following, how does that impact moderation and privacy?
Meta joining the Fediverse is like AOL joining the internet: something that will bring a mass amount of people in, create some friction, but ultimately make the net better as more people federating on #Mastodon, #kbin, #lemmy, #pixelfed and other parts of the Fediverse make open protocols that much stronger.
#Bluesky now allows you to “choose your own algorithm”.
Which sounds “incredible” and “sci-fi”—but it really isn’t.
What it essentially does is give a Twitter-like service Reddit-like features.
As an aside, now I’m wondering why Reddit doesn’t offer an alternative web front-end to make it more Twitter-like!
But how does this apply to the #ActivityPub flavour of the #Fediverse? This feature now makes me realize how big a deal Fediverse groups are going to be, and if I were @Gargron, I’d be even more excited about rolling out Mastodon’s group functionality.
Because while groups aren’t exactly relevancy algorithms, once you add a “New”, “Hot”, “Best”, etc. feed to groups, now you’re in business.
I don’t know if choosing your own algorithm is the killer feature that Bluesky thinks it is. My experience is that most people hate choice. Nevertheless, I still thinks it’s important.
They go on to imagine some wonderful or awful scenario where the floodgates are open and #Threads becomes another #ActivityPub app like #CalcKey or #Plemora.
Maybe.... but what you are envisioning is really very unlikely. Threads is entirely algorithm driven. How's that going to work? Plus they have no interest in letting their captured users escape.
I just had a look at #Meta's recent press release about #Threads, and something caught my attention right away.
For the very first time, they're acknowledging another #Fediverse platform alongside #Mastodon. Specifically, they're highlighting that #WordPress can now connect through #ActivityPub.
Now, you know Meta's PR department doesn't say things by accident. So here's why this is a big deal. Last time I checked, WordPress powers a whopping 43% of the Internet. Yeah, you heard that right! If you visit a website, there's a good chance it's using WordPress as its CMS.
Now, if even a fraction of those WordPress sites start federating, it could have a huge impact on the network effect of the Fediverse. Of course, Meta isn't oblivious to this. I've been talking about the potential of WordPress and ActivityPub for quite some time now.
But if you're particularly observant, you might also notice that they mention #Tumblr. We've known for a while that Tumblr is likely to integrate ActivityPub into their platform.
But here's an interesting tidbit: Did you know that one company, Automattic, not only owns Tumblr but is also the driving force behind WordPress?
I don't want to jump to conclusions, but once again, PR departments don't just drop hints randomly. I have a strong feeling that Meta has been having some high-level discussions with Automattic about the future of ActivityPub. It wouldn't surprise me if Meta has some insights into Automattic's upcoming plans for the Fediverse.
The network effect for #ActivityPub is gaining some serious momentum right now. As more services adopt the protocol, more people, more communities and more content are added to the network making it increasingly more valuable for everyone. This will only accelerate in the coming months as Threads, Wordpress, Tumblr, Flipboard and others federate.
We're still in early innings but there's no way to put this genie back in the bottle. The open social Web / the #Fediverse is going to be huge.
Yet another question people are asking me: "How can I, a common person, help hasten the demise of #Meta through #ActivityPub?"
Again, I want to re-emphasize this. #Fediblock is not an all-purpose tool. It's useful as a hammer. But in this scenario, we don't just need a hammer. We need drills, pliers, saws, and blowtorches.
That said, we must protect communities that choose to defederate from Meta. Which means that if those servers don't want to receive messages from any Meta-owned services, we must not only be respectful of that, we should make damn sure that those servers are quarantined from Meta. So much of the success of fighting Meta will require safe spaces from Meta.
The next thing we need is lots and lots of nodes. Currently, we only have ~25,000 nodes on the Fediverse but we need more. Preferably, these nodes should be small, agile, and well-moderated. If you have the finances and/or skill to run a node, it's important that you do so. To compete with Meta, we need to build scale -- and the easiest way to build scale is by adding more nodes to the Fediverse.
What will also be key is lobby servers. These will be servers specifically set up for migrants from Meta-owned services to help onboard them towards the rest of the Fediverse. To run such a lobby server, they need to be welcoming, moderated well, and free of the elitists and gatekeepers that poison so much of the Fediverse currently.
How to get people from Meta to try out the rest of the Fediverse? We need people willing to be ambassadors on #P92 who are ready and willing to evangelize the rest of the Fediverse. Folks like @tchambers are very good at this on Twitter, and I have no doubt that we can do the same with P92. Except this time we'll have the benefit of federation already happening 😉
Now if there's one thing I've learned about the growth of the Fediverse it's that bad corporate decisions pay dividends. We've already experienced waves of migration from Tumblr, Twitter, and Reddit. And I have no doubt that it's only a matter of time before Meta makes another corporate mistake -- as they tend to do.
In which case, we need to strike fast. When another Cambridge Analytica happens, we need to remind everyone on Meta about the lobby servers that are on standby, and ready to take them on. Unlike previous migrations, let's not be unprepared for this. Let's be especially prepared since Meta plans to join the Fediverse.
Finally, we need more devs. Specifically, we need devs willing to build innovative server and client software that takes aim at Meta. And to do that, we need to support the devs that currently exist -- show evergreen devs pondering whether they should invest here that we, as a community, are appreciative of our current devs.
If you like #Mastodon, #Calckey, #Kbin, #Friendica, etc., it's important that you open up your hearts as well as your wallets and fund the next stage of Fediverse development.
This will take a lot of work. But if you want to fight Meta, challenge their dominance of social media, this is what must be done.
Personally, I'm hyped about the future of the Fediverse -- regardless of whether Meta eventually lives to tell the tale.
I’m happy to see Threads starting to federate with Mastodon and other ActivityPub networks!
Open standards are good, and honestly, I have a ton of friends already on Instagram and Threads that would never join yet another social network, but I’d still love to keep up with them and their lives without having to use Threads. Federating via ActivityPub enables exactly that.
With Meta beginning to test federation, there's a lot of discussion as to whether we should preemptively defederate with Threads. I made a post about the question, and it seems that opinions differ a lot among people on Kbin. There were a lot of arguments for and against regarding ads, privacy, and content quality, but I don't...
#ActivityPub is super cool once you see it in action.
For instance, you can visit the new StarTrek lemmy server here: https://startrek.website/c/startrek. Looks like a reddit sub with posts, threaded comments, upvotes, &c.
OR you can follow the same server on Mastodon @startrek.
Every thread and comment shows up as a boosted post.
Cool, right? Now, say you find a comment that you want to reply to. Post through your favorite Mastodon app, and that feeds right back to the thread on the #Lemmy server! 🤯
It is an existential threat to the very core of Meta’s social media monopoly. Surprisingly, if the goal is to fight against Meta’s hegemony, the most effective strategy may be to federate with them.
“But Chris,” some of you might state, “Even you agree that it might be better to defederate Meta – and you’ve even set up notmeta.social for expressly this purpose.”
Yes, because it’s not everyone’s objective to fight Meta, and there should be spaces where fighting Meta isn’t top of mind. Not everyone wants to be part and parcel of a fight, and that’s okay.
Let’s first acknowledge the technology through which federation happens. #ActivityPub is an open standard protocol that enables the decentralized social networking that powers the Fediverse. It allows different social media platforms (#Mastodon, #Calckey, #Kbin, etc.) to interoperate, meaning that users on one platform can communicate with users on another platform. Federation is the process by which these platforms connect and share content, forming a decentralized network.
The most important thing to understand about ActivityPub is that, more than a technology to merely send and receive messages, it’s also a common ruleset – a gentleman’s agreement that everyone will play nice when sending and receiving messages.
Now when Meta opts to use ActivityPub, they’re abiding by the agreement: to play by the same rules as everybody else. Should they renege on this agreement, they are no longer using ActivityPub. They’re using something else.
But let’s assume for a moment that Meta is abiding to use ActivityPub, and they indeed will play by the same rules. Knowing Meta, this is a tall order – but still, let’s assume.
ActivityPub means that whatever of Meta’s userbase that’s exposed to federation will diversify into other platforms. This is because, through ActivityPub, smaller platforms can connect with each other and offer a combined user base that competes with Meta’s centralized network. This diversification reduces the dependence of users on a single platform, giving them more choices and potentially drawing them away from Meta.
This creates an erosion of Meta’s network effects. Meta’s entire monopoly is based on ownership of their platforms’ network effects, where the value of the platform increases as more users join. Suddenly, by federating, Meta no longer own the network effect. This is because federation challenges this by breaking down barriers between platforms, allowing users to interact regardless of the platform they are on. This reduces the exclusivity and advantage Meta holds, as the network effects become distributed across multiple interconnected platforms.
Federation also gives Meta’s users power that they never previously had. Federation promotes decentralization by giving users greater control over their data and interactions. With ActivityPub, users have the freedom to choose which platform they prefer without sacrificing connectivity. This user empowerment threatens Meta’s control over user data and engagement, potentially leading to a loss of influence and advertising revenue.
ActivityPub poses a tangible threat to Meta’s monopoly on social media. By choosing to federate, Meta might be opening Pandora’s box. The moment Meta’s users receive a message from a server not owned by Meta is the moment they’re exposed to something else beyond Meta’s control. Inevitably, this will create more diversity of ActivityPub-enabled platforms – not less. This will erode Meta’s network effects. For people who use Meta, the power of decentralization – giving them more freedom – will prove revelatory.
Of course, this is a fight. And just because Meta federates doesn’t mean it’s game over. In the next post, I will explore what Meta is hoping to gain by joining the #Fediverse.
iOS AppStore privacy preview for Meta’s upcoming ActivityPub-based app Threads
A case for preemptively defederating with Threads
With Meta beginning to test federation, there's a lot of discussion as to whether we should preemptively defederate with Threads. I made a post about the question, and it seems that opinions differ a lot among people on Kbin. There were a lot of arguments for and against regarding ads, privacy, and content quality, but I don't...