Stop lumping it in with ActivityPub.
-
Stop lumping it in with ActivityPub.
It costs $30 million to create a second copy of Bluesky.
All the decentralization happening on Bluesky is happening within the context of that particular network.
You need MILLIONS, a ton of infrastructure, and a ton of employees, to create even a second copy of Bluesky.
That will not save us. That is not a fire exit.
-
"...decentralized social media options like Bluesky and Mastodon..."
Bluesky really benefiting from all the positive aspects of Mastodon/Fedi decentralization, without having to do the work.
-
P [email protected] shared this topic
-
@[email protected] it doesn't cost $30 million for a separate infrastructure, it's just Mozilla and a bunch of other AI companies noticing "oh wow there's a lot of money floating around how do we get in on this bonanza?" and trying to create the Bluesky equivalent of SWF.
-
@jdp23 I don't really have any elaboration on your post, but thought you'd find it interesting, from a user safety standpoint, I just approved your reply.
-
@[email protected]
right you are, I'm very interested in that! Very cool!
Before you approved it, would it still have been visible on other instances besides yours? -
@jdp23 My thinking is that this would only be the case if they somehow searched your instance. Like I imagine whether or not my instance approved the reply or not, yours surely had to create it on your side.
This would have given you the impression you created the reply, but if I never approved it, no one scraping my instance for posts (as GTS does with conversation threads and which has a PR Mastodon is still waiting to approve)...
But my thinking is that other instances will contact my instance to pull down the "official" record so they can add replies, as GTS is doing above.
If I don't approve, or deny the reply, then that won't show up as a reference for others on other instances to use, so they can't reply to it, either.
I'm not 100% on this, but I believe they'd still be able to reply to it from your instance just fine, assuming they navigated to it there, but on the official "OP" thread they are most likely to use as a "source of truth", there'd be no record of the reply.
Which is about the best we can expect right now until interaction policies are supported by other software, too.
This is one neat thing about the ION island network--all the instances run GTS, so reply controls are enforced equally across the network.
-
@[email protected] that makes sense although it's hard to know the behavior for sure. I just followed you from @[email protected], if you hold off on approving this for a bit I'll see whether it's visible over there.
And yes I agree that being able to limit participation to instances running software with stronger safety functionality is a huge strength of island networks! Really looking forward to the blocklist subscription feature in the next GtS release, that'll make things a lot more tractable. -
Nope, it showed up immediately in my home feed here. Oh well. Not much that can be done really ... island networks FTW
-
And here, on a GTS instance (where my account isn't following you), when I clicked on the @thenexusofprivacy reply, it pulled the whole thread, so it did show @jdp23's not-yet-approved reply to your post as a reply. So ... hmmm ...
-
@jdp23 @thenexusofprivacy @jdp23 Actually, that followed my reply policy.
The policy is that you can always reply if you follow me, or if I follow you. And GTS will allow anyone @mentioned to reply, too.
Permission, for me, only comes into play when there's no follow relationship. You already followed me from the nexus account.
Also, once permission is granted in the thread, there's no way to revoke it, but we can certainly test this later if you want.
-
Got it. That makes sense -- I had misunderstood your policies and also didn't reaize that once it's granted it applies to further replies in that thread.
Yes, if you're up for it, it would be interesting to do some testing. This account and @[email protected] aren't following your olifant.social account.
@[email protected] @[email protected]
