irelephant
@irelephant@lemmy.dbzer0.com
- Comment on Microsoft pushes staff to use internal AI tools more, and may consider this in reviews. 'Using AI is no longer optional.' 2 hours ago:
Sam Altman makes money from people believing this.
- Comment on Microsoft pushes staff to use internal AI tools more, and may consider this in reviews. 'Using AI is no longer optional.' 2 hours ago:
Ai definitely can’t replace many (if any) microsoft employees.
- Microsoft pushes staff to use internal AI tools more, and may consider this in reviews. 'Using AI is no longer optional.'www.businessinsider.com ↗Submitted 2 hours ago to technology@lemmy.world | 33 comments
- Comment on Bluesky is more open than you think. 1 day ago:
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: atproto.com/guides/self-hosting#preparation-for-s… . 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.
- Comment on Bluesky is more open than you think. 2 days ago:
Yeah, it doesn’t even have communities.
- Comment on Bluesky is more open than you think. 3 days ago:
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. - Comment on Bluesky is more open than you think. 3 days ago:
I like both formats, but I do prefer forum-style conversation.
frontpage.fyi is a link-aggregator built on atproto.
- Comment on Bluesky is more open than you think. 3 days ago:
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.
- Comment on Bluesky is more open than you think. 3 days ago:
I use them interchanagbly, which has proved to be a mistake.
Kinda like how mastodon and fediverse are used interchangably. - Comment on The strenghts and weaknesses of atproto and activitypub. 4 days ago:
I feel like that’s closer to email, which is a shitshow when it comes to decentralisation.
- Comment on What happens to the content if an Lemmy instance shuts down? 4 days ago:
I was misremembering something here, mastodon always keeps old keys iirc, but lemmy caches them temporarily iirc.
- Comment on Bluesky is more open than you think. 4 days ago:
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. - Comment on The strenghts and weaknesses of atproto and activitypub. 4 days ago:
That’s a good point.
I think by recipient they meant followers in general. - Comment on The strenghts and weaknesses of atproto and activitypub. 4 days ago:
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.
- Comment on The strenghts and weaknesses of atproto and activitypub. 4 days ago:
Yes, this does help, but atproto as a whole still doesn’t scale well:
In the beginning of our network, we have 26 users, which conveniently for us map to each letter of the English alphabet: [Alice, Bob, Carol, … Zack]. Each user sends one message per day, which is intended to have one recipient. (This may sound unrealistic, but this is fine to do to model our scenario.) To simplify things, we’ll have each user send a message in a ring: Alice sends a message to Bob, Bob sends a message to Carol, and so on, all the way up to Zack, who simply we wrap around and have message Alice. This could be because these messages have specific intended recipients or it could be because Bob is the sole “follower” of Alice’s posts, Carol is the sole “follower” of Bob’s, etc.
Let’s look at what happens in a single day under both systems.
Under message passing, Alice sends her message to Bob. Only Bob need receive the message. So on and so forth.
From an individual self-hosted server, only one message is passed per day: 1. From the fully decentralized network, the total number of messages passed, zooming out, is the number of participants in the network: 26. Under the public-gods-eye-view-shared-heap model, each user must know of all messages to know what may be relevant. Each user must receive all messages.
From an individual self-hosted server, 26 messages must be received.
Zooming out, the number of messages which must be transmitted in the day is 26 * 26: 676, since each user receives each message.
Okay, so what does that mean? How bad is this? With 26 users, this doesn’t sound like so much. Now let’s add 5 users.
Under message passing:
Per server, still 1 message received per user per day. Per the network, it’s 5 extra messages transmitted per day, which makes sense: we’ve added 5 users. Under the public-gods-eye-view-shared-heap model:
Per server: 5 new messages received per user per day.
Per the network, it’s ((31 * 31) - (26 * 26)): 285 new messages per day!
But we aren’t actually running networks of 26 users. We are running networks of millions of users. What would happen if we had a million self-hosted users and five new users were added to the network? Zooming out, once again, the message passing system simply has five new messages sent. Under the public shared heap model, it is 10,000,025 new messages sent! For adding five new self-hosted users! (And that’s even just with our simplified model of only sending one message per day per user!)
Source: dustycloud.org/…/re-re-bluesky-decentralization/
As well as this, if there was a reddit-like atproto AppView, setting up multiple instances of it would still result in the same problems.
- Comment on Bluesky is more open than you think. 4 days ago:
Actually, take a look at AppViewLite, it lets you skip relays and crawl PDSes directly. Its fairly lightweight as well, so you could host it alongside a PDS.
- Comment on Bluesky is more open than you think. 4 days ago:
Define decentralised.
As per RFC 9518: Centralization, Decentralization, and Internet Standards,[…] “centralization” is the state of affairs where a single entity or a small group of them can observe, capture, control, or extract rent from the operation or use of an Internet function exclusively.
[Decentralization is when] “complete reliance upon a single point is not always required” (citing Baran, 1964)
[…] federation, i.e., designing a function in a way that uses independent instances that maintain connectivity and interoperability to provide a single cohesive service.
- Comment on Bluesky is more open than you think. 4 days ago:
No, they just want to develop it themselves so they have no reliance on bluesky.
- Comment on The strenghts and weaknesses of atproto and activitypub. 4 days ago:
Ah, right.
Well, this is just AP in general.
Though, piefed having community moving is great, since communities aren’t trapped on their host server. I don’t think lemmy.world would be as big a problem if they could move communities there. - Comment on The strenghts and weaknesses of atproto and activitypub. 4 days ago:
What do you mean? As in, not missing information? In that case, it is the same as lemmy. Though iirc that’s only for stuff in communities.
- Comment on Bluesky is more open than you think. 4 days ago:
I don’t think you should be critising bluesky when you don’t even know who the CEO is.
- Comment on Bluesky is more open than you think. 4 days ago:
I’m not quite sure what you mean here to be honest.
- Comment on Bluesky is more open than you think. 4 days ago:
I really hate this attitude.
Most people who are against bluesky don’t even care about an open internet or whatever, they just want their protocol to win or whatever.
- Submitted 4 days ago to fediverse@lemmy.world | 13 comments
- Comment on Bluesky is more open than you think. 4 days ago:
I agree with you there.
I wish they put a bit more effort into getting people onto independant servers.
They took to opposite approch of mastodon: they abandoned proper distribution for better growth.In any case, ActivityPub and atproto can both coexist.
- Comment on Bluesky is more open than you think. 4 days ago:
You would be correct.
- Comment on Bluesky is more open than you think. 4 days ago:
My point was that the network was fairly centralised in the beginning. The people behind atproto.africa are working on an alternate bluesky appview anyway.
- Comment on Bluesky is more open than you think. 4 days ago:
I just say bluesky because that’s what everyone knows it as. I’m really talking about its network.
Its not very well distributed, because almost everyone is on bluesky’s meganodes.
Its more of a social problem than a technical problem at this point. - Comment on Bluesky is more open than you think. 5 days ago:
I have read it, and a lot of the problems have been addressed.
Bluesky is still very early. There was an awkward period where lemmy was mostly lemmy.ml.I’m not trying to cherry pick anything, I’m just addressing arguments against it I have seen.
- Comment on Bluesky is more open than you think. 5 days ago:
That is horribly centralised, but its not (imo) an essential part of the network.
They do intent to fix it at some point.