

Ai definitely can’t replace many (if any) microsoft employees.
Failing optimist, can code poorly.
RIP: lemm.ee
Ai definitely can’t replace many (if any) microsoft employees.
The tweet is fake.
I don’t really think it being edited adds anything to the joke.
I’m coming back to this,
I think the self-hosting bit is a bit flawed, its almost entirely based on opinion.
For example, I’d have taken a lot of points from email as its all too easy to get blacklisted for doing everything right, and setting up everything is a pain. Cory Doctorow (Author and popular blogger) got on a spam-blocklist for self-hosting his newsletter, and it was an effort for him to get himself off it. It would be impossible for an average joe to get off a blocklist.
You can self-host old versions of reddit, I’d have given it a few points.
Self hosting a PDS is pretty popular, but the average PDS has less users than mastodon instances.
Its also not very poorly documented, hosting the official PDS is just running three commands: https://atproto.com/guides/self-hosting#preparation-for-self-hosting-pds . they have a docker for it as well.
Maybe not bluesky itself, but there is lots of atproto AppViews (essentially clients) which do stuff. Would you classify frontpage.fyi as a client?
There is clients for bluesky itself anyway, graysky, deck[.]blue, AppViewLite, the official apps, deer[.]social gander[.]social tapestry, surf, phoenix (made by the people who made ivory), skeets (real app), bluejeans, off the top of my head.
I think the content share part doesn’t really apply to bluesky since everything is portable, so if bsky disappeared, all content would still exist and be referenceable. Unlike AP based stuff, where everything is tied to its host server.
Also: hosting PDSes is piss easy, if there was demand for people to move to other servers, more PDSes would pop up.
Instances are centralised, but the network isn’t.
Yeah, it doesn’t even have communities.
Yes, it is, but so is mastodon, if I curate my feed, I can exclude them from it.
this is about the technical aspects of bluesky/atproto.
I like both formats, but I do prefer forum-style conversation.
https://frontpage.fyi/ is a link-aggregator built on atproto.
Bluesky would work better for that, since everything would be on the AppView. Hosting multiple appviews would be intensive on the relays, but different ones could keep content for different amounts of time.
I think AP works better when you don’t need or want all the information to be available at once.
I use them interchanagbly, which has proved to be a mistake.
Kinda like how mastodon and fediverse are used interchangably.
👍
No, mastodon is more decentralised than bluesky, but its designed so that PDSes aren’t that important, unlike mastodon.
I feel like that’s closer to email, which is a shitshow when it comes to decentralisation.
There are instances though.
Portability makes it really easy to migrate accounts. You just need a .car archive of your old one.
Decentralisation is not black and white, and depends on your defintion of the word.
At this point, the problem is that everyone is on bluesky’s servers. There is little technical problems.
Annoyingly, most people aren’t interested in that.
Also: I found this list: https://github.com/mary-ext/atproto-scraping
There’s a good few more PDSes than I thought. There’s a few with open signups. Though, for relays the situation is a bit more bleak.
I’m sure it will improve in future, there is a lot of orgs planning on setting up AT infrastructure.
Oh.
Well, as of now, there’s little incentive to host one.
AppViewLite lets you use the network without a relay, which I think is cool.
Because all the nerds who want to do that are on mastodon ; ).
Jokes aside, people are self hosting them, there’s about 2000 independant PDSes right now.
do you mean instances having a native atproto implementation? Wafrn is kinda like that.
Also: Bluesky isn’t maintaining the bridge, its maintained by someone else.
Sam Altman makes money from people believing this.