If ActivityPub wants to keep riding the wave it has now they should start investigating ways to support this. I think more and more people are getting fed up with centralized platforms / not owning their data.
Given the meteoric rise of TikTok, I don't think there is any sign of this being true outside a small techy bubble. At least, not as a percentage (that is, the growth in the number of people who are fed up with centralized platforms is dwarfed by the growth in the number of people who are fine with centralized platforms / not owning their data).
Network effects are real, but appear insignificant until they’re in our faces. The fact that it’s currently a minority is expected, that’s just how network effects work. It was just a minority on Reddit when Digg was the place to be as well.
Obviously I don’t have any magical predictive abilities. But the “vocal minority” argument has bitten a lot of people before. Including those that have stake in the game and are paranoid about competitors.
The younger Snapchat generations have normalised having their face plastered on every random "hello" message daily.
In Denmark we're in the process of banning devices like iPads and smartphones from schools and other institutions. We're also likely going to see an age limit on Social Media like TikTok that's around the same age as buying Alcohol (yes, that's a good combination) and a range of other things. In the wider EU, you have privacy and competition stepping in, both banning and taxing these platforms in ways that might make it hard to operate a profitable platform if you're allowed to have one.
It's still a little too uncertain to say anything concrete, but it's certainly not looking like the explosive growth of centralized "free-to-use" platforms will face the same profitable and non-regulated market the coming 20 years that they did the previous.
Someone is going to be well positioned to take advantage of this as people move on from the previous generation of social media platforms.
This is another advantage for Bluesky. Because as of now, a user of BlueSky would have no clue that it is "decentralized" at all. In comparison, Nostr shoves it in your face that it is totally unlike anything you're used to.
Bluesky just appears as a Twitter alternative. And I think that is very smart of them. Because realistically, only very serious people/companies should consider running alternative relay servers. Relays come and go on Nostr because people underestimate the amount of work / money involved in running them.
Another non-activitypub alternative is nostr, where your identity is a public/private key pair: https://github.com/aljazceru/awesome-nostr
Moving data only works in this case if you've thought to attach your DID to a domain you control, and the server you move to connects to the BGS server your data lives on. It's still very unclear how this will work. I suspect it will be like Usenet where most BGS indexers have expiry rules and won't hold on to every post.
This is more complicated than AP and Mastodon where you know exactly where you stand when your server goes down. So many people are going to be burned because they heard it's all portable, but didn't actually understand how it worked, and find they can't migrate their identity or their posts because it all rested under [handle].somehugecentralizedserver.tld.
People who struggle with instances on Mastodon (and eventually, Bluesky) are not going to have an easier time figuring out domains and DNS to make their identity portable. This remains a huge unaddressed issue and should concern people who think Bluesky is easier just because it's unfinished.
With Mastodon you can download your data any time, but you can’t actually upload it anywhere else. There is forwarding, but only for follower subscriptions, with the cooperation of both servers. It’s quite limited. There are brownouts from servers getting overloaded and also due to fairly frequent policy disputes. It does let you do more things without making them public, though, and that’s important to many people.
The blogging model where you have actually independent websites, links, and RSS feeds seems better from a decentralization standpoint, but it’s not popular due to the difficulty of getting people to subscribe to your blog.
That’s why we comment here, right? You could post a comment to your blog, but who would read it? Replies are important.
[1] Technically three - I've got Akkoma, GotoSocial, and a Honk but I only really use the Akkoma one for "real life".
Not only do you have to keep it running at your expense but you need to invest significant time in moderating the content. Lest you allow illegal content e.g. CP to be hosted for which you will be legally responsible.
That way you don’t need to moderate.
There's also the fact that Bluesky is run by Jack, who founded and managed pre-Musk Twitter "1.0" and funded Musk's Twitter "2.0". I don't have high expectations nor hopes.
That's not accurate, Jack gave the Bluesky/AT Protocol organization initial grant money, but he doesn't "run" it. The CEO is Jay Graber.
Jack is a power-hungry opportunist who throws money at anything that can give him wealth and status in the future.
The fact that they haven’t broadly got other servers they’re federating with - they’re not ready - is why they’re limiting signups.
> A problem with the system of having a domain as a username is that people can claim it who don’t have access to that username.
That was a bug, and is not generally speaking, the case. You must have the ability to alter the DNS records for the domain you wish to claim.
> However, that means interactions, such as user likes, blocks, follows, etc are all public. With no means to make them private. Which could lead to harassment!
It could also lead to the enlightenment of man, if we're just making random claims without explaining ourselves...
> But runs into the problem of algorithms being hijacked to show inappropriate/offensive/bigoted content.
Posts on the AT Proto can be labeled by whatever labeling service you prefer, including Bluesky itself. You can then use your preferred labeling to filter out labels you don't want, or subscribe to a feed that does that for you.
> But also it’s a group of overly complicated specifications that could’ve just been extensions to the ActivityPub protocol rather than a whole new protocol!
I don't think, "AT Proto is too complex, use ActivityPub instead" is a reasonable claim at all. The problem is a complex one, and AT Proto in particular is not even out yet.
Honestly, I can barely understand this "article". It's just a bunch of oversimplified (and sometimes outright wrong) statements about what AT Proto is, coupled with painfully misunderstood declarations that border on the illegible.
This is not exactly true, it just means the server that holds ur data (traditionally instance or home server) doesn't need to be involved in the transfer process. However, this has centralized identity resolution, which is not a good long term solution.
> For example, someone was able to get the AWS S3 domain as their handle!
This is easily hotfixable by requiring more stringent proof of ownership of the domain (like DNS records), rather than a problem with the protocol itself. But it's a valid concern
> But runs into the problem of algorithms being hijacked to show inappropriate/offensive/bigoted content.
I thought the whole point was that if you didn't like the algorithm you could swap it out for something simpler. This point puzzles me greatly
> that could’ve just been extensions to the ActivityPub protocol rather than a whole new protocol!
Not really. If you peel back the interface they're very different, since the transferability of accounts across servers is something baked deeply into how ActivityPub works and cannot be easily changed without rewriting the protocol. That being said, I personally hope there is some network that can solve the problem of untying resources from domains, since it is one of the big problems with any federated protocol
A big improvement is possible "just" by making instances revalidate the URI against webfinger regularly (you'd still need to plan ahead for that, but it'd enable "stable" usernames) and secondly by allowing for a key pair to let users sign messages to make claims about ownership and which account is current. That would make it possible to enable fully unilateral moves.
Neither would require any changes to ActivityPub.
Realistically, I don't think it could handle a full enslaught of new users and wants to onboard slowly which makes sense from a development point of view. The issue is, it's basically dead or just full of shitposts. Which has no real value.
And the number of people who want on it aren't actually that high, I've got 3 invites and no one to invite.
It has the potential to be, once it’s finished. But it’s not finished yet.
Is anybody already doing this? It shouldn't too be hard. Just throw all the notes into a directory and add some code which replies to the different types of requests.
I guess the best way to get ones tweets out of Twitter is the "Download an archive of your data" thingy in the settings?
https://wordpress.org/plugins/activitypub/
The Indieweb Crew of course did this first. The principle POSSE – Publish (on your) Own Site, Syndicate Elsewhere – was coined by them and is the guiding principle behind the Indieweb movement and it is exactly what you’re trying to do. You should click around a little bit in their wiki:
Most of the time the Indieweblings are doing their own “protocol“ by receiving and reacting to webmentions with rich data structures in Microformats syntax in their HTML. Some parts of Indieweb a rather opinionated about technologies. But a lot of them also interact with different federation services, for example see:
So they probably could get even more users, but I'm guessing it's already sufficiently crazy for the team right now
That isn't necessarily an issue with using a domain as a username, it was only possible because you could verify ownership by putting something in a subdirectory they defined which was available as an S3 bucket name (see https://news.ycombinator.com/item?id=35820815). If you allow verification only from the root directory or via DNS records this shouldn't be a problem AFAICT.
Au contraire, if network users control their clients, they can "block"¹ and "follow" content at-the client level without stating it publicly.
¹. Not a full block, as the blockee can still read and interact with the blocker's posts.
So do those extensions exist (even in the form of plans), especially the ones that free you up from a server or is it just wishful thinking?
I tried Mastodon for a bit and like the community there, but I found they were very deliberately trying to build a place that wasn’t like twitter: building federated search is frowned-upon; no quote-tweets; extremely low threshold for content warnings.
They’re building something different and that’s great, but it’s no surprise that people fleeing twitter want to go to the more twitter-like app.
There should be a decentralized social communication protocol that is more fit to reflect how people communicate: more ephemeral and less of a permanent record. I remember LitePub/Pleroma did some work in that direction, and it's mostly compatible with ActivityPub too I think
You have four properties of feeds: category, tree-comment, real-time and persistent.
Reddit was the winner on all those except real-time.
Decentralization is now the most important feature, and taking responsibility of your own data is the best version of that.
The only missing part is decentralized RSS servers and clients. Think backup for your posts and RSS reader services that also backup your favorite feeds.
All you need for that is a distributed db underlying it all like this: http://root.rupy.se and a reader web tool.
The only feature we lack is a category (think hashtag) for RSS.
So a combination of all services below:
Add mail and video hosting/streaming and you got the complete deal.
Reply works fine and comments too even if only local.
I got my invite from a website where people shared their invite links. After creating an account, and using it for a while I also got the ability to share invites with like 10 people or something.
I don’t even know if doing that kind of thing would work today though, given how many spammers and such trawl the internet. Probably some small number of people would grab every invite for themselves, instead of taking only one invite each.
I know of no way at this time to run one's own instance or federate.
There are of course significantly less users compared to the main instance, but it should give you some confidence that federation dev work is on the right track.
It has to be better somehow, and the whole selling point is decentralization to sidestep the possibility of recreating the current Twitter fiasco.
That goal is not yet achieved, which means it's below parity.
If you don't like Mastodon, there's Pleroma, Misskey, Calkey and others, as well as apps, or you can find RSS feeds from them if you just want to read, or you can use one of the alternate web frontends.
Originally people were extending feeds with the Atom ActivityStreams Extensions, in XML, for richer data structures which contain the social activities of persons. The protocol PubSubHubbub (now WebSub) was used for some realtime updating of feed subscribers (Push-then-pull, instead of Pull). Mapping persons or rather their accounts to resources like feeds was the impetus for WebFinger. And for notifying comments or reactions to upstream feed producers there was the Salmon protocol. Together those formats and protocols morphed into the OStatus protocol.
With the rise of JSON and with lessons learned from OStatus and pump.io those specs morphed into ActivityPub today. The underlying ActivityStreams vocabulary is still the same, I think, but the mechanism for following and responding now uses dedicated out- and inboxes.
I think microblogging and other social network stuff and long-form blog posts are different content, best consumed differently. There is some overlap, of course, but articles do not need shoehorned in. Sometimes people simply undervalue the simple link from a microblog post to the longform article.
Which is based on an open-standard, interoperates with Mastodon and is from a company that has the battle scars to prove that they can operate a global service in a mature and a reasonable way.
Given Jack Dorsey's support of the crazier positions of Elon Musk and RFK e.g. WiFi causes leaky brain it really does look like the best of a bad bunch.
[1] https://www.theverge.com/2023/7/1/23781271/instagram-threads...
> Which is based on an open-standard, interoperates with Mastodon
By which we mean: capitalises on work done to form an open standard, to parasitically drain users, and then deliberately break compatibility a year down the track. FB messenger literally did this when it started too - supported a bunch of different protocols to capture everyone, and then let them break.
That said, I’m impressed teams at Facebook have managed to stop working on stealing features wholesale from TikTok and Zuck’s anaemic VR disaster long enough to knock out an app to parasitise a different community.
yes, yes... let's cheer at Facebook doing things right...
yeah, I'm not sure why he's going all-in on a fringe candidate who's clearly never going to win
