Zum Inhalt der Seite gehen


Fediverse! I’ve been building a bridge to Bluesky, and they’re turning on federation soon, which means my bridge will be available soon too. You’ll be able to follow people on Bluesky from here in the fediverse, and vice versa.

Bluesky is a broad network with lots of worthwhile people and conversations! I hope you’ll give it a chance. Only fully public content is bridged, not followers-only or otherwise private posts or profiles. Still, if you want to opt out, I understand. Feel free to DM me at @snarfed@indieweb.social (different account than this one), email me, file a GitHub issue, or put #nobridge in your profile bio.

A number of us have thought about this for a while now, we’re committed to making it work well for everyone, and we’re very open to feedback. Thanks for listening. Feel free to share broadly.

cc @activitypubblueskybridge @fedidevs @fediversenews

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf Ryan Barrett

will you be able to e.g. reply to a Bluesky post from the Fediverse, in a way that people on Bluesky will see your reply?
Als Antwort auf Ryan Barrett

@tchambers Holy moly "moderate people, not code" is so good. So many ideas I've wanted to express but you had the skill and knowledge to express them so much better than I'd have been able to!
Als Antwort auf Ryan Barrett

Pagan Plus will be blocking the blue sky bridge for automaticly opting unaware users into sharing and introducing the fediverse to bluesky's moderation problems.
Als Antwort auf :jan:‍:abreath:‍‍🌬:dandelion:

After reviewing the domain operated by the bridge creator, I have silanced the domain to discourage interaction with data scrapers

teilten dies erneut

Als Antwort auf Ryan Barrett

sure wish the number of you thinking about this for a while had thought long enough to make it opt in for those interested rather than opt out for those not interested.
Als Antwort auf Shiri Bailem

I promise I know how the fediverse works. have a great life.

teilten dies erneut

Als Antwort auf DJ Sundog - from the toot-lab

@DJ Sundog - from the toot-lab @Ryan Barrett @Ryan Barrett clearly not if you are upset at a bridge offering an opt-out feature, as opposed to all the other bridges which don't. Or that you're upset at a bridge existing on the fediverse in general...
Als Antwort auf Ryan Barrett

How do domain blocks work across the bridge?

For example, if I'm opted-in to the bridge, but want to block the entire foo.bar PDS, will a Mastodon domain block work?

Assuming it does anything at all, will it block all traffic originating from foo.bar, or only accounts that use the foo.bar domain in their handles?

If it doesn't work, is there any way to subscribe to a shared blocklist across the bridge?

Als Antwort auf SuperMoosie

Mastodon works this way by default, it sends your posts to thousands of other servers without your permission. Please leave this developer alone.
Als Antwort auf Sam :verified:

There is nothing to prevent a commercial organization from setting up a Mastodon server, in fact I believe that there are already examples of that.

So, there is no protection on Mastodon now for sharing your content with commercial services.

teilten dies erneut

Als Antwort auf Tim Erickson, @stpaultim

Sure there is. Defederation and account level domain blocks are protections against that. Which are exactly the topics I asked about.

teilten dies erneut

Als Antwort auf L. Rhodes

How do defederation & account level domain blocks prevent some commercial entity from setting up a server & syndicating via the activitypub protocol?

@stpaultim @sam @SuperMoosie @snarfed.org @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf L. Rhodes

@L. Rhodes @Ryan Barrett on both sides the bridge would appear as a single instance, so you would not be able to selectively block servers on the other side of the bridge. If this becomes a problem you can easily block the whole bridge.

For more granular controls you would want a native plugin to your platform.

teilten dies erneut

Als Antwort auf Shiri Bailem

could you block individual fediverse users from bluesky?

i'm not sure on fediverse if we currently can block individual users effectively anyway from this direction?

teilten dies erneut

Als Antwort auf Golda

@Golda @L. Rhodes @Ryan Barrett It's really important to understand the language here, Bluesky once they federate is the fediverse even if it's not accessible from Mastodon. If you want to differentiate we're on ActivityPub (the protocol our instances are using to talk to eachother, though my instance supports multiple different protocols while Mastodon does not). This is not a Bluesky to Fediverse bridge, but a Bluesky Fediverse to ActivityPub Fediverse bridge.

On both sides you will be able to block individual users without issue, they'll still appear as individual users. The only limitation on blocking is site-wide blocks.

One of the things people miss is that Bluesky is intending to compete with Activitypub by releasing their own protocol. So eventually there will be other servers sharing on the Bluesky protocol and not just the one.

Once that happens, you will not be able to block individual Bluesky instances from ActivityPub and likewise Bluesky will not be able to block individual ActivityPub instances. They can block individual users or the whole bridge, nothing inbetween.

Als Antwort auf Golda

From what I can tell, the bridge uses the did:plc as the account ID of Bluesky posts bridged to ActivityPub, which should make it relatively easy to block individual accounts, since that's their canonical ID on the Bluesky network.

Ironically, it *doesn't* use a canonical ID when relaying ActivityPub to Bluesky—it uses the bridgy domain as part of the ID—which could theoretically make it easier to avoid Bluesky blocks from the ActivityPub side.

teilten dies erneut

Als Antwort auf L. Rhodes

hm except "block" having the meaning of "they also can't see me" i think is much harder to enforce over the bridge

teilten dies erneut

Als Antwort auf Golda

I think it can work as long as the Bsky PDS is compliant with blocks, since blocks themselves can be bridged. The main difference is that third parties can see blocks too over there, iinm.

teilten dies erneut

Als Antwort auf Qazm

My understanding is that blocks are handled upstream of the PDS—usually by the feed generator or App View. I could be wrong about that, though. Maybe PDS also handle blocks? But the flow chart in their latest white paper also shows some feeds bypassing the PDS and going straight to the account-holder's client, so it seems possible to route around PDS blocking enforcement.

All those extra services complicate things, don't they?

teilten dies erneut

Als Antwort auf L. Rhodes

Yeah.

Each PDS publishes its local users' block lists (and changes to that should be part of its outbound AT firehose), so the bridge can send blocks to Bsky. On the fedi side, it should notice them at least through authorised fetch, but there's probably some activity pushed for changes there too.

The main "issue" is that it's a push vs. pull and collation boundary, so the bridge must bookkeep this info locally and can't just translate volatile network requests on demand.

teilten dies erneut

Als Antwort auf Qazm

An interesting aspect of blocks on Bsky is that they're non-destructive, so they don't actually cut follow-relationships (but essentially fully suspend them) and are pretty reversible. I think that's an implementation detail though and neither AT nor AP really prescribe this one way or another.

Non-destructive blocks are a bit nicer with shared blocklists, since that means less "spiky" computing and that block lists can't do as much damage if they become unreliable.

teilten dies erneut

Als Antwort auf Qazm

I'm trying to sort what that would mean across the bridge. Let's say Eta on Bsky follows Delta on AP, and Delta then blocks Eta. On Delta's end, it looks like Eta is no longer a follower, but as far as Bsky is concerned, Eta is still following Delta, correct? And outgoing posts are only prevented from reaching Eta by the bridge's record-keeping? What if that record becomes "unreliable?" Might the follow be restored without Delta's knowledge?

teilten dies erneut

Als Antwort auf L. Rhodes

The bridge can't really filter in this direction, since afaik AT firehose subscriptions are anonymous. Rather, it's Eta's PDS that enforces the bridged block. Delta's instance should also stop sending posts to the bridge, as AP does not use a firehose, but only if there are no other (not-blocked) bridged Bsky followers.

A meaningful desync happens only when the block is rescinded: The bridge may have to automatically re-follow Delta as Eta to restore consistency, since I don't think you can 'remove a follower' on AT.

What happens with a follow in the other direction depends on whether there are separate block and unfollow activities generated by Mastodon. If yes, then no desync happens and Delta('s software) can choose whether they still follow Eta after the block is gone. If blocking does imply unfollowing in AP, then the bridge would have to translate AP blocks into AT block-and-unfollow.
Delta would then not follow Eta after the block is gone, unless Delta('s instance) re-follows Eta explicitly.

Maybe there's some inconsistency detection and cleanup scheme built into one or both of the protocols, too, in which case the bridge should make use of that where possible. I'm not aware of such a mechanism, though.

teilten dies erneut

Als Antwort auf Qazm

If the bridge forgets about the block somehow, then the follow may be restored on the AT side if Eta's PDS pulls Delta's AT repository from the bridge to refresh/catch up after a disconnect and doesn't see the block, yes.

The bridge can probe whether Delta blocks Eta over AP at least if Delta's instance requires Authorized Fetch, so when possible, it should probably do that at a low frequency to keep its records straight.

teilten dies erneut

Als Antwort auf Ryan Barrett

no good idea. It is not ok to demand an active optout via #nobridge from everyone. I dont care for bluesky, i care for my privacy! @ErikUden
Als Antwort auf DaFrühling

I guess you want to use privacy settings on your posts then. This is all public by default here

teilten dies erneut

Als Antwort auf DaFrühling

I don't know you, we're not connected in any way I know, and yet, I can see your post, and your profile and more.
How is that for your privacy?

teilten dies erneut

Als Antwort auf Zatty :meowybara:

I might be missing something, I don’t follow how this is different to the Fediverse today. Any new server can access & federate from any other, unless the user or the server blocks it (unless I’ve misunderstood!) Wouldn’t this be the same for fed.brid.gy? (But you can *also* use the hashtag in your profile)
Als Antwort auf JP

I think the main difference is that, like Nostr, Bluesky is just one big monolith with known problematic users (that have to be "filtered" out), so it's hard to moderate effectively. It's the same as any other large Mastodon instance, like dot Social or Gab.
Als Antwort auf Blake Leonard

Ahh yeah, I guess some users/servers might want/need to block the whole of brid.gy to avoid the risk of specific users on a given bridged platform being able to follow them. That’s not so different to today’s fediverse (lots of people/servers block Threads), but it sucks to lose the other functionality of brid.gy.
Als Antwort auf JP

(Unless you can block specific bridges platforms individually @snarfed.org ? This still seems within the limits of current Fediverse architecture to me, but it’d be a shame if we can’t allow people to select platforms by server, just like with the Fediverse!)
Als Antwort auf JP

@byjp@zatnosk@activitypubblueskybridge@fedidevs@fediversenews@snarfed@hachyderm.io If you want to block just Bridgy's Bluesky bridge, or just their (upcoming) Nostr bridge, or whatever, you can do that. If you want to block specific PDS's, I don't think there's a way to do that.
Als Antwort auf JP

The difference is it is a commercial network. We have not signed up to the TOS AND he is copying everything with out permission from the user.

We did sign up just to the fediverse, not to make content for a billionaire.

If people want to post elsewhere they can sign up for the TOS.

It needs to be OPT IN If people want to use it.

@zatnosk @activitypubblueskybridge @fedidevs @fediversenews

Als Antwort auf SuperMoosie

Considering each instance can have its own terms of service, this is a legal space that is largely untested currently. My thoughts are that the legality will boil down to "follow each instance terms", but it's an amazingly complex thing even there. And I say this even as an instance owner who thinks that bridgy should be explicitly opt-in either per-post, per-user, or per-instance.

Per-instance, to me, kind of makes the MOST sense for having an 'opt-out' tag in the bio -- each instance owner is then making their own users aware of the policy and can give them advance notice if they don't wish to be included. Just having a global "we can have your information even if you're unaware of it" policy is half the problem of the current tech industry snarfing up damn everything as if it's theirs to use, causing all the LLM garbage issues today.

Hell, the fact I'd have to end my wifi SSID in _at least_ two weird tag things, and one of them MUST be the last one, to avoid my wifi SSID, BSSID, and location getting snarfed by mapping cars (google, MS, etc) is just part of this. I have to take up limited characters in my bio for each service I want no part in? I have to make my SSID ugly just so a corp won't use info I didn't consent to them using? While I like the idea of being able to follow friends of mine who are on AT instead of fedi, and refuse to use fedi, it's not worth it being so open; I always figured there would be an opt-in mechanism, not yet more opt-out stuff.

C'mon, @activitypubblueskybridge, haven't you seen how many times people offering only opt-out are shown the distaste for this? =/ 'bridge' or not, it's still technically a specialized service, it's not transparent just because things are duplicated both ways.

Als Antwort auf Kay Ohtie

@Kay Ohtie @SuperMoosie @JP @Zatty :meowybara: legal space is simple, TOS only applies to the service you're using. You're not using Bluesky, you're not using my instance.

For a TOS to apply you have to accept it in some fashion, most of these sites do this by either a passive "if you continue to use this site you implicitly accept the TOS" (and that can only reasonably apply while you're actively browsing the site, not for relayed fediverse messages) or a "to create an account you have to accept the TOS".

It's the same legal grounds as whether or not Yahoo's terms of service apply when I email someone who has a Yahoo account.

It's also a woefully flawed argument to assume that the loudest voices represent the majority. The majority don't care and the backlash just goes more to show the toxicity of Mastodon culture (and I mean Mastodon here, not ActivityPub)

teilten dies erneut

Als Antwort auf SuperMoosie

There are several commercial Fediverse networks that you have not opted into, but that your posts can be sent to (via boosts, replies, etc.). Please shut the fuck up and leave this developer alone. This is embarrassing.
Als Antwort auf SuperMoosie

I did not consent to the TOS of your instance and yet, it's copying this post so that you can see it. And guess what, you did not consent to the TOS of my server and yet, it has copied your post and basic info so that I can see them.
Als Antwort auf JP

The difference is that when you post to the Fediverse, you expect your post to be federated within the Fediverse via its native means. One consents to this type of content propagation when they make posts on Fedi.

Bridging is something beyond that, and is not something one consents to when making posts on the Fediverse.

teilten dies erneut

Als Antwort auf eishiya

@eishiya @JP you should know that Bluesky, once they start federating (which this is directly related to)... is the fediverse as well.

Please do not confuse Mastodon/ActivityPub with the whole fediverse. The fediverse is a wide array of servers and there are many bridges between different protocols out there already.

And on the topic of consent, this is a purely public system. Consent within the fediverse is opt out, when you post publically you are automatically consenting to anyone receiving and transmitting your post however they wish. If you do not wish to provide that consent, you make your post private.

Bridges are a natural part of federation and are key to it's survival as it makes all relevant platforms less likely to collapse.

teilten dies erneut

Als Antwort auf Shiri Bailem

This is a good point, and I should know better than to conflate AP services with the whole Fediverse.

After I made that post, I did think about how this is different from federating with, say, Diaspora, which I personally don't have a problem with. I think the difference is that Bluesky is a corporate product that offers no reason to assume good faith. Same deal with Threads, which uses AP.

(1/2)

Als Antwort auf eishiya

My problem isn't so much with federating with Bluesky, but with the opt-out mechanisms this bridge offers. They are all non-standard (not part of either protocol), with the exception of instance-level blocks. If user-level blocks (e.g. me personally blocking the bridge domain) works, then I'm less bothered, but AFAIK OP hasn't responded to that query.

(2/2)

Dieser Beitrag wurde bearbeitet. (2 Monate her)
Als Antwort auf eishiya

@eishiya You blocking the bridge domain will work just the same as blocking any other instance, they won't be able to answer that really because that occurs entirely on your server and not theirs (I don't believe there's any AP protocol for "Hey X user@domain has blocked you").

I do really like their approach to providing opt-out mechanisms specifically because not all platforms have user level domain blocking available. Especially as they're implicitly suggesting a standard with the nobridge hashtag in the bio as it would be a great universal way to request an opt-out of bridges by default if it became broadly accepted... though the backlash here might hurt that.

As far as the corporate aspect of it... yeah, all the corporate platforms are awful and I genuinely hate them. The only reason I'm in favor of bridges like this is because I dream of the fediverse becoming the norm, that corporations can be better dis-empowered by connecting than isolating (ie. they see that it's better over here, so choose to leave Bluesky for AP, and the bridge then makes that transition relatively painless for them, as opposed to the segmentation that happens with no bridge)

I've never once spoken out against people choosing for themselves whether to block an instance, only against the backlash efforts where people moralize over it (ie. considering blocking threads a moral imperative, or demanding that someone's passive bridge between open and public networks be opt-in instead of opt-out).

Als Antwort auf Shiri Bailem

I think hashtags are a poor mechanism. Bio space is often limited, and bios are intended to be read mainly by humans - people want them to look nice and not be full of hashtags like nobridge, noai, nobot, etc.

I think if there's no protocol-level opt-out possible, the next best thing would be to provide a low-spoon way to opt-out, such as via a form. "Contact me on socials or open an issue", however well-intentioned, comes off as requesting more effort than is reasonable for many folks.

Als Antwort auf eishiya

@eishiya something like a google docs form is not unreasonable, though I think the "contact me on socials" is easier so long as you don't have social anxiety lol

For reference though, the hashtag idea is mostly for the lack of protocol level options. This doesn't mean OP chose to not implement such options, but rather that such options just don't exist in the protocol. They had to write extra code to make the system parse your bio for that tag before allowing the content through the bridge, which I do consider to be very considerate.

Als Antwort auf Stevie Cat, Daisy Dog & Betty

@Stevie Cat, Daisy Dog & Betty @JP @eishiya for the hashtag to work you need to put it in your profile. When a Bluesky user tries to follow you through this bridge it'll check your profile and hide your account if you have that tag in your profile.
Als Antwort auf Zatty :meowybara:

Indeed. There should be no bridge, and if there is a bridge, then requiring opt-out by people who have nevee heard of that bridge is the opposite of consent.
Als Antwort auf the roamer

This argument about consent is fictional. Anyone can create a server on the Fediverse and everyone on the Fediverse is conntected, without their consent.

Bluesky could create a Mastodon server, any commercial entity can create a server and everyone is linked without consent.

The only way to preserve consent on the Fediverse, is to create a server that is not linked to other servers, in which case you don't have to worry about this bridge.

teilten dies erneut

Als Antwort auf Tim Erickson, @stpaultim

If you really believe in consent, then you should be advocating that no one is connected to any server other than the one they signed up for, unless they opt-in.

teilten dies erneut

Als Antwort auf Tim Erickson, @stpaultim

The BS bridge links to a commercial platform outside the Fediverse, rather than to other instances within the Fediverse. People sign up to their Fediverse instance in order to be connected within the Fediverse. Some people in the Fediverse also want to be connected to commercial external platforms, but many very definitely don't. They joined the Fediverse precisely because they want to be free from those platforms. That's where the "opt-out" mechanism violates consent.

#consent

teilten dies erneut

Als Antwort auf Tim Erickson, @stpaultim

With respect it is not at all like a commercial Mastodon server. A bridge contributes to a social media platform that's not (yet) proven its bona fides as regards being anti-monopolistic.

teilten dies erneut

Als Antwort auf Ben Thompson 🐕

The developer has made clear that this bridge is only possible if Blue Sky turns on Federation and made clear it will be a two way bridge.

I'll leave it at that.
snarfed.org/2023-11-27_re-intr…

teilten dies erneut

Als Antwort auf the roamer

Undecided on this but we had bridges / gateways to a lot of federated networks on the usenet and users did not consider this a problem with consent in principle. You don’t have to use it and your instance can block it.
However, blueky could easily become one of the too big to block instances on the fediverse, but with a different culture concerning moderation (and archiving), and that may become a problem.

teilten dies erneut

Als Antwort auf chris@strafpla.net

@chris@strafpla.net @the roamer @Ryan Barrett @Zatty :meowybara: I don't think "Too Big To Block" is really an argument... If people don't want to talk to Bluesky users, they can block Bluesky. If Bluesky is so uncontrollably toxic as to create a critical problem, then why would you not block those posts?

The only time "Too Big To Block" really applies is the same time the people who aren't bothered by this... the people who prioritize getting as many people on the fediverse as possible to have as much reach as possible.

teilten dies erneut

Als Antwort auf Zatty :meowybara:

Please shut the fuck up.

Mastodon sends your posts to thousands of other servers without your consent. That is how ActivityPub works. This is doing absolutely nothing different.

Als Antwort auf Sam :verified:

I think, many Fediverse users trust on the moderation in the fediverse. Connecting to a network without a trusted moderation could be a problem?!
Bluesky isn't simply "another server"

teilten dies erneut

Als Antwort auf Markus

I'm still on the fence about this, but if Bluesky suddenly becomes partly dependent on Mastodon content, it may well force moderation … or I guess they'd be defederated. @sam @zatnosk @snarfed.org @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf Världens bästa Kille™

@Världens bästa Kille™ @Sam :verified: @Ryan Barrett @Zatty :meowybara: @Markus they'd be defederated, and-or users would migrate from Bluesky to Mastodon now that they can do so without cutting off contact to other Bluesky users.

teilten dies erneut

Als Antwort auf Sam :verified:

I'm in agreement with your arguments. But, I'm fully against the tone and the aggressiveness of your responses.

It's nice that Mastodon has such nice features to block users such as yourself.

Your account is an opt-out account. No one was asked to consent to your hostility, it's just part of the network, however everyone has the option to block it (opt out).

I expect, I'll be taking advantage of that feature.

teilten dies erneut

Unbekannter Ursprungsbeitrag

JP
Looks like, yes! There are some details on his site: snarfed.org/2023-11-27_re-intr…
Als Antwort auf Ryan Barrett

I'm a big fan of bridges and this is the big one I've been eagerly waiting for. I'll probably add it to my wizard soon after it's available. Once the moderation issues get sorted out, I firmly believe that in the end, this will be a net positive for both networks, since Bluesky users will be able to follow and engage with the vibrant and growing communities and services here, and we'll be able to follow and engage with shitposters from Bluesky.

The moderation issues should be sorted out promptly, and I'm a little disappointed that you're going to open it up with little consideration about mod tooling, especially considering the lists and lists of known problematic users on Bluesky, from mere crypto-shills and scammers to bigots, transphobes, racists, fascists, and genocide supporters. I don't have any way to find or use Bluesky's mod lists from here so there needs to be some other way.

Plus, I'm sure Bluesky users want a way to mass-mute and mass-block bridged users, maybe even from particular instances, especially considering our ongoing tone police and reply guy problems, which have driven numerous people from here to there. I feel like this part is imminently solvable with automatically-populated moderation list(s), though.

Als Antwort auf Blake Leonard

Where have we signed up for the bluesky TOS?

What gives this guy the right to copy our content we make for the fediverse available on a commercial network?

No one has consented for this.

Bridges need to be opt in.

@fediversenews @fedidevs @activitypubblueskybridge @snarfed.org @snarfed

Als Antwort auf SuperMoosie

@SuperMoosie @Ryan Barrett @Ryan Barrett @Blake Leonard to be clear, where have you signed up for my server's TOS? And I don't mean that just to be silly, it's very explicitly how the legal take works here.

You can not apply your TOS to outside users and they can't apply their TOS to you. If you take issue with it you can block the instance.

And as far as "Bridges should be opt in" that ship passed decades ago, bridges aren't remotely new, this is just probably the first you've noticed.

teilten dies erneut

Als Antwort auf Ryan Barrett

Glad to hear it! I would prefer to have a single account that gives me access to the wider Fediverse than have to have multiple identities across multiple networks. Thanks for your work! How do we use it?
Als Antwort auf Ryan Barrett

Opt-in only, or I #DomainBlock

What is that again?

bsky.brid.gy?

So noted...

I want *nothing* to do with #Bluesky

#NoBridge has been added to my profile

cc @activitypubblueskybridge @fedidevs @fediversenews@venera.social

Als Antwort auf FinchHaven

@FinchHaven @Ryan Barrett ... "opt-in or I opt-out"?

How's that a threat? It's literally how these things work...

teilten dies erneut

Als Antwort auf Ryan Barrett

"Moderate people, not code"

You do not have the resources to moderate everything that will flow over this bridge, so you shouldn't do it. Your project will force this work on other instance mods.

Opt-out is unethical because people aren't aware they're being opted-in, but also because it makes this bigger and dumps more work on other instances.

Als Antwort auf unlofl [Promoted Toot]

honestly, we probably need another project like #fedipact to track things like this. I don't want to keep an eye out for every scraper/indexer/bridge project, I just want to pick an instance where my admins defed and opt everyone out. As a bonus, this would place pressure on projects to be opt-in only, so they don't get blocked on sight by whole communities.
Als Antwort auf unlofl [Promoted Toot]

@unlofl [Promoted Toot] @Ryan Barrett That's literally a whitelist server, you join a server that only federates with pre-approved servers.

That's the only functional way if you want to pro-actively avoid being accessible from all bridges. Though to be honest you can also just pay attention to the usernames of whomever follows you to see if it's a bridge account, not like it's hard to spot randomuser:bluesky@instance

teilten dies erneut

Als Antwort auf Ryan Barrett

please, make your tool opt-out by default. and learn about the concept of consent. opt-in by default is never acceptable.
Als Antwort auf Sveitsiläinen Älypieru

youre correct, but you mean the opposite words. opt-out is what is described in the post and is unacceptable
Als Antwort auf Toatrika, Witch of Numbers :neocat_legs:

@Toatrika, Witch of Numbers 🏆 @Kaknäsin Thorne @Ryan Barrett y'all could also learn to use the concept of consent with public speech... get over yourselves, you consented by posting publicly. If you don't understand that then you need a primer in what the fediverse is and how it actually works...

teilten dies erneut

Als Antwort auf Ryan Barrett

I am excited for this, thank you for the time and effort you're putting into building this ActivityPub <> ATproto bridge, especially the two-way communication support! I have had very poor experiences with BlueSky myself, but I have multiple friends that prefer it and just aren't interested in Fedi. It will be amazing to be able to rebuild that part of my social circle and keep tabs with them, while still being able to utilize the filtering and timeline curation tools that only Mastodon provides right now.
Als Antwort auf Noxy 🐾

The Fediverse is already made up of literally dozens of various services that all speak the same protocol - Mastodon, Firefish, Pixelfed, Pleroma, Frendica, among many others - and users on one service can freely interact with users on another service. Personally I don't see this bridge as being anything different, really. I have essentially zero issue with a public post of mine being visible to any and all - that's the whole point of a public post on the open web, imo. As long as they hold true to their word that non-public posts won't be viewable via the bridge, I have no issues with it.
Als Antwort auf Baral'heia Stormdancer ΘΔ🐲

"I have essentially zero issue with a public post of mine being visible to any and all"

YOU speak for only YOU. Yet you seem happy to subject others to your comfort zone.

Do you not see why that's a significant problem?

Als Antwort auf Pusher Of Pixels (old account)

Honestly no, I don't. First of all, I was only talking about my own preferences in that regard. If I post something with full public visibility, I have zero expectation of privacy on that post. But that said, a public post is a public post. Any time you make a public post on Fedi, that post is copied to other instances and other services through federation in order for others to view it. This is entirely by design. If you do not wish a post to be seen by any random user on the Fediverse, you are empowered with multiple ways to make that happen - be it blocking the user, blocking their instance, or adjusting your account or post privacy settings. According to the documentation (fed.brid.gy/docs) for the bridge, it's intended to work the same way, with the same restrictions - posts would not get picked up by the bridge until someone follows you, you would receive notifications any time someone followed you (there are NO anonymous follows), and you can block that user from following you just as if they were a native Fedi user. If the post or account is not public, then the bridge won't even know the post exists to do anything with it.
Als Antwort auf Baral'heia Stormdancer ΘΔ🐲

So you're supposition is people can choose how widely seen their content is?

That's kinda ironic considering this is entirely without choice for the vast majority who won't even know about it.

OptOut is a terrible idea on every angle.

Als Antwort auf Pusher Of Pixels (old account)

@AS4gBPS9axYI2RYbEe.snarfed.org@snarfed.org Opt-out is the default of the Fediverse. As a server admin, I don’t actively choose who federates with me. Federation happens as soon as my server “sees” another.

There is a way to change this default towards opt-in, and that’s by whitelisting. Most servers, including universeodon.com, don’t choose to go this route because it severely affects their visibility.

Another problem is that, even if you whitelist, once your content federates onto another server, it is beyond your control. It exists elsewhere. A malicious party who is on another server may interact with it in a distasteful, insensitive, perhaps illegal manner.

The way some servers have gotten around this is by turning off federation entirely. That is an option, but probably not one that most people on the Fediverse want.

Als Antwort auf Chris Trottier

Yes indeed, Thanks for making that clarification for all of the clueless people posting here who hitherto believed otherwise, as if they ever had it that way.

They'll complain and threaten to go somewhere else, and of course, they're welcome to that option as well, but in the end...

"“Life's but a walking shadow; a poor player, that struts and frets his hour upon the stage, and then is heard no more: it is a tale told by an idiot, full of sound and fury, signifying nothing.”

#tallship #FOSS #Fediverse #bridges #innovation #fools

⛵️

.

Als Antwort auf Pusher Of Pixels (old account)

uh yeah, that's the whole point. This bridge acts just like a regular Fedi user and follows all the same rules. If the bridge can't see your posts, it can't do anything with them - and you have full control over how visible your posts are. You also have the option of adding a hashtag to your profile, defederating from the domain the bridge lives on, or contacting the dev for a manual opt-out.

Plus, as far as I can tell, absolutely none of this is intended to happen in a vacuum. The documentation I linked earlier explains that users who are followed via the bridge still get a notification that they were followed, just like they were followed by a regular Fedi account. You'll see the BlueSky user names of each user that follows you through the bridge, and you'll be able to block individual users from seeing your account through the bridge if you so choose (in addition to the options above).

You'll have the same control over who can see your content that you would with any other Fedi user.

I'd strongly recommend reading the documentation to get a better understanding of how this is intended to work when it goes live.

Als Antwort auf Pusher Of Pixels (old account)

I’m not meaning to be snarky, but your point is that users on the fediverse don’t understand what the differences between the multiple visibility options of postings are?
@baralheia @noxypaws @snarfed.org @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf lily 🏳️‍⚧️ :flag_pansexual: θΔ ⋐ &

Do you think that people who don’t know about the bridge would give a fsck about it - taking into account that their public posts are visible on instances of lemmy, friendica, pleroma,… and they don’t know about it?
Isn’t the way this bridge to bluesky is implemented exactly the way that another service on the fedi should be implemented?
Is it because bluesky is a commercial instance?

@pixelpusher220 @baralheia @noxypaws @snarfed.org @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf chris@strafpla.net

no, their posts are just visible on other fedi instances. that's how fedi works. obviously they're fine with that, or they wouldn't have signed up to fedi. no, the bridge to bluesky isn't implemented in the same way, because bluesky doesn't use activitypub, therefore is not part of the fediverse. people's posts would be being mirrored to bluesky without their consent.

teilten dies erneut

Als Antwort auf lily 🏳️‍⚧️ :flag_pansexual: θΔ ⋐ &

So what’ the difference between the fedi
and bridged bluesky?
Just the protocol? What parts/variants?
If I ask those very angry posters in this thread, can they explain to me what activitypub is?
What about services that use OStatus? Are they fedi? And then most posts are accessible using rss and some are integrating this into their blogs.
Is wordpress an ok member of the fediverse?

@pixelpusher220 @baralheia @noxypaws @snarfed.org @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf chris@strafpla.net

And if it is the protocol -
where does it have to be implemented? Can a service use a different protocol for internal communication and communicate to external instances using AP? Can this part run as a separate server? What’s the difference to a bridge?
No, this drama is not about the protocol.
“The Fedi” means something(s) else and we need to understand this to solve the drama.
@pixelpusher220 @baralheia @noxypaws @snarfed.org @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf Baral'heia Stormdancer ΘΔ🐲

Here's a thought... While it's not a concern for me, I'm seeing a lot of worry from others about opt-in consent for this bridge. Could you consider (either by option or by default) having the bridge send newly-followed users a message through their service saying, basically, "this is an automatic message from Bridgy Fed. <User> wants to follow you from <service> via this bridge. Do you want to allow this?" and offer always, yes, no, and full opt-out options in response. The user who initiated the follow request wouldn't see anything until the newly-followed user responded, and no response would equal a "no" answer. Could something like that be doable?
Als Antwort auf Baral'heia Stormdancer ΘΔ🐲

@Baral'heia Stormdancer🔜 AnEx @Ryan Barrett that's pretty much already native with how a bridge works.

When a Bluesky user goes to follow you, you'll get a follow request from that user:instance@bridge (or similiar format username).

A lot of the confusion and freak out comes from people (a) not knowing how bridges work and (b) taking vague offense because they don't like Bluesky and think that the whole fediverse should conform to their personal standards

teilten dies erneut

Als Antwort auf Shiri Bailem

You misunderstand me - I'm well aware of how follows work on Fedi. What I'm suggesting is that there be an additional active consent prompt via DM specifically for the Bridgy Fed bridge when someone follows you through the bridge - the idea being since BlueSky is an external service and not part of the Fediverse, this not only informs users that Bridgy Fed is a thing and gives them control over whether or not they will allow their posts to be bridged over to BlueSky independent of their normal Fedi follow settings.

teilten dies erneut

Als Antwort auf Baral'heia Stormdancer ΘΔ🐲

@Baral'heia Stormdancer🔜 AnEx @Ryan Barrett wouldn't really be possible because they couldn't know to send it until some action had already been taken on your account over the bridge. Let alone the fact that it would be incredibly spammy and still be an opt-out system.

It's important to note that Bridges have existed for decades, a lot longer than ActivityPub has been a thing (and a lot of people don't realize there are other fediverse protocols, let alone older ones...), probably longer than I've been a thing.

Als Antwort auf Shiri Bailem

it's perfectly possible. Imagine this scenario: a BlueSky user finds and follows a Mastodon user through the bridge. The bridge receives the incoming follow activity from BlueSky and sends a direct message like the one I mentioned before to the Mastodon user. Mastodon user replies with the correct keyword to accept the follow, at which point the bridge sends a follow activity to the Mastodon user (and if necessary sends an accept activity back to the BlueSky user - I'm not certain how that message flow works). The rest of the message bridge process would be unchanged from this point, once the follow relationship is established.
Als Antwort auf Baral'heia Stormdancer ΘΔ🐲

@Baral'heia Stormdancer 🔜 TFF @Ryan Barrett how would it get the follow activity without already bridging the profile? That's the part you're missing.

And again, it's a massively burdensome process that is a wild departure from federation standards, both in following and in how bridges operate.

Als Antwort auf Ryan Barrett

I hope your creepy non-consensual fucking project gets defederated from every instance and your shitty fucking bridge becomes completely fucking useless
Als Antwort auf hazelnot :yell:

@hazelnot :yell: @Ryan Barrett reporting you to your server admins for violating rule 7 on your server...

Bridges are a dime a dozen (literally there are so many out there already and this is open source so good luck de-federating them all without just joining a whitelist server), the fediverse doesn't work the way you think it does, bridges probably don't work the way you think they do, and dogpiling on someone for sharing their project for feedback, especially for offering a polite feature to exclude yourself from the bridge which no other bridge I've seen offers just makes it clear you're an asshole.

teilten dies erneut

Als Antwort auf Shiri Bailem

This is increasingly how I'm inclined to treat these crybullies. Ryan's doing really important work to move the Fediverse forward and these are people who just get off on abusing strangers online. They'll never be satisfied.

teilten dies erneut

Als Antwort auf Evan Minto

@Evan Minto most of them are convinced that Mastodon is the entire fediverse and that their experience of it is the "one-true-fedi"
Als Antwort auf hazelnot :yell:

@hazelnot :yell: I don't get why people get angry over a freakin' bridge, yet they have no issue with the existence of projects like #BirdsiteLIVE. This is just so entitled. If you don't want to have your content available live on every place, just post it with a different privacy option smh

teilten dies erneut

Als Antwort auf Cătă

techbros understand consent challenge (impossible)

teilten dies erneut

Als Antwort auf hazelnot :yell:

@hazelnot :yell: you give consent when you publicly post something online. In fact, guess what, I can see your profile and whatever you publicly post without even logging in to your instance. How? I use a web browser.

Did you also give your consent to an obscure 3rd party app to display your content inside it? No. Let's just ban them all then, just like Xitter and Reddshit did, or like Meta/Faceshit did in the 1st place.

Oh, it's so great when we have stuff to help us reach content, from friends, from people we follow, but God forbid someone else reaches our content from other parts of the internet. Those that want that are just techbros.

teilten dies erneut

Als Antwort auf Ryan Barrett

Opt-out violates consent. Peter posts on the Fediverse, so that his friends on another Fedi instance can read his daily thoughts. He knows that there are many other people on the Fedi who can also see his posts. He is OK with that; indeed, he hopes for a wider Fedi audience. But he hates all commercial platforms, including BS. He wants his posts hidden from BS. Regardless, your bridge links Peter's posts into BS, against his wishes and without his knowledge. Don't!
Als Antwort auf the roamer

yes FFS why must we opt out every time someone creates some new bullshit we hate!
Dieser Beitrag wurde bearbeitet. (2 Monate her)
Als Antwort auf Tattooed Mummy

On this other platform was a hashtag 'followfriday'. Does the fediverse need an 'optoutfriday'?
Als Antwort auf Ryan Barrett

So,
if me or other trans* individuals, or other marginalized groups (many of whom I'm sure will *never* see your post with the genuinely shit opt-out option) are harassed or otherwise receive uninvited abuse and commentary through your bridge, are you prepared to face legal challenges brought against you?
Als Antwort auf Ryan Barrett

Cool! Looks interesting, sucks you are getting some piss poor negative feedback but the Fediverse does like to hurt itself pretty bad with stuff like this. I hope everything goes smoothly. Don't take the fedi mob seriously.
Als Antwort auf Ryan Barrett

i don't want anything to do with this and i'm not putting some shit in my profile to help enable your weird "just opt out!" philosophy
Als Antwort auf Ryan Barrett

thanks for the heads-up! Blocked the domain on the server level. Centralized corporate social media always goes to shit, so it's nice to block it out from day 1.
Als Antwort auf Ryan Barrett

Making this on an opt-out basis was a horrible, horrible decision. Please opt me out, and never, ever, include me in any future bridges.
Als Antwort auf Ryan Barrett

@gogobonobo You need to make this opt IN not opt OUT. It absolutely fucking sucks that you want to force the majority of decentralized posts here into content for Jack fucking Dorsey.
@Jake
Als Antwort auf Cyrus.Dog

@Cyrus (still a bit spooky tbh) @Jake @Ryan Barrett I get the feeling you think a bridge is a scraper...

Bluesky is about to start federating just under it's own protocol (their equivalent of ActivityPub which others will be able to host servers on the same as we can host servers on AP). A bridge translates between two protocols. Your content isn't getting scraped and uploaded to Bluesky.

A bridge just means that Bluesky users will show up to us like new users on this bridge. user1@bluesky will turn into something like user1.bluesky@brid.gy.

teilten dies erneut

Als Antwort auf Ryan Barrett

Such a service should be opt-in only, for the handful of folks who DO want their content used to generate traffic for Bluesky.

As I'm not one of those people, I am notifying you that I am opting out. It'd be nice if that request was honored, but realistically I know it won't be.

So fuck you.

Als Antwort auf Ryan Barrett

So,
if me or other trans* individuals, or other marginalized groups (many of whom I'm sure will *never* see your post with the genuinely shit opt-out option) are harassed or otherwise receive uninvited abuse and commentary through your bridge, are you prepared to face legal challenges brought against you?
Als Antwort auf Jess

@Jess @Ryan Barrett as a fellow trans* individual: you're either probably not familiar with how bridges work or you are not using safe practices and taking things for granted.

There are already many bridges on ActivityPub to much worse parts of the fediverse and they're not making waves (if you think Bluesky is bad, you should see Nostr). If they start harassing a user you treat it exactly the same as you would someone showing up to harass you from a new Neo-Nazi Mastodon instance, you can either block the user or block the whole bridge (only downside of a bridge is that you can't really block by individual server on the other side, it's either block individual users or the whole bridge).

This also has absolutely no threat of legal challenges to go along with it, it falls under numerous legal protections. Let alone the argument will absolutely fall apart in court that someone would complain about easily blockable abuse on a public post.

In case you're not aware, because it seems a lot of people think a bridge is some sort of web-scraper... it's a translator between protocols. It's not scraping your profile and copying posts, it's translating ActivityPub requests to Bluesky requests and back.

teilten dies erneut

Als Antwort auf Johannes Hentschel

@Johannes Hentschel @Ryan Barrett If you take issue with your post being federated then you really should note that you've opted in already by posting publicly and on a non-whitelist server.

teilten dies erneut

Als Antwort auf Shiri Bailem

OK it's good that you're going around explaining to people what a bridge is but I don't see a lot effort on your side to understand the deeper implications that people associate with bsky, the ones that sets it apart from "worse bridges". As a privacy advocate you must have come across people who take issue with their friends storing photos of them on gPhotos? That's the spirit. Yes, a bridge translates: we eschew what follows after.
@snarfed.org

teilten dies erneut

Als Antwort auf Johannes Hentschel

@Johannes Hentschel @Ryan Barrett oh I know full well, I'm deeply conscious of the bounds of my privacy, both what is under my control and what isn't.

I'm tired of the ideological purism present on the fediverse, especially from the Mastodon users who think they own the place and that their clique's reflect not only the norms, but the reality of how the world works.

If you care about the privacy to that extent, then you should be making your posts private to begin with, full stop. I recognize the difference between concerns and paranoia, it's why I've told many people throughout the thread that if they really mean what they say they should find a whitelist server.

People assume my cavalier attitude means I don't care about privacy or security... it doesn't come from not caring, it comes from being explicitly conscious of the decisions I've made regarding each. The fear comes from people who want others to accommodate their fear while they do nothing.

Als Antwort auf :PUA: Shlee fucked around and

eh ... as with Threads + fedipact, there's likely a spectrum where the louder voices can mask the "middle of the road" voices, for better or worse. Anti-Bridge-Pact?

What exactly is the difference between this and a new instance? I'm genuinely unclear?

Like, do kbin instances respect search indexing preferences? What about other commercial instances like moth?

Is it the relative size of bksy?

Als Antwort auf maegul

Agreed. I just want to actually interact with people I actually know on other platforms from the comfort of Mastodon. I miss people I actually know in real life.
Als Antwort auf James Harris

Yea, for me, the whole "I want a relatively anti-social social media" motive of many on masto seems like something that requires better institutional/infrastructural devices rather than merely distributing it amongst defed, personal blocks and outcries over opt-in/opt-out.

At some point, it seems, some people just want a different system than what this is. Like a closed FOSS Discord.

Als Antwort auf maegul

Which, TBC, is all good by me.

It's just that the amount of noise and "drama" necessary to maintain this constant vigilance against what a decentralised social media protocol naturally allows seems like a potential dead end with diminishing returns.

EG, many on bsky that those here would like to talk to have probably left here because of this "noise" however much they align with the values here.

Als Antwort auf maegul

@maegul @:PUA: Shlee fucked around and @Ryan Barrett @James Harris I've seen this for a while, many people on here are highly xenophobic. They found a place for themselves and they now want to close the gates on anyone else joining, seeing "foreigners" (other platforms) as threats rather than a foundational part of how this service works.

On top of that, they often demand ideological purity... it's actually one of the reasons Twitter survives and people use other shitty platforms... because they hopped on here and found only hostility to any way in which their social norms differed from what people considered acceptable.

teilten dies erneut

Als Antwort auf maegul

I just checked and Mastodon does have a whitelist mode instances can use of they really want control over their data.

"This mode is intended for private use only, such as in academic institutions or internal company networks, as it effectively creates a data silo, which is contrary to Mastodon's mission of decentralization. This setting was known as WHITELIST_MODE prior to 3.1."

docs.joinmastodon.org/admin/co….

@jbwharris @shlee @snarfed.org @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf Ryan Barrett

A lot of people are upset about this but ya'll know, straight up, if your feed is live & people not auth'd can read your server feed you *don't have privacy*. Mastodon and the fediverse in general never said anything about expectations of privacy.

Snarfed here could have been a bad actor and never told you anything and as far as I know it's in the clear.

If you don't like it, block the bridge and move on.

Als Antwort auf Shanie

“They could have been a bad actor and you would never know” does not seem to be a good point to make to convince people of bridging.

teilten dies erneut

Als Antwort auf chris@strafpla.net

Lucky for you they gave admins an option of what you want done. Good actor.

A bad actor, for example, is likely already gathering your servers data and training it on a LLM as you have no power over THEIR server; you have *volunteered that data by federating*. Your ToS means nothing. Oops.

Someone truly worried about privacy would not be federating at all.

teilten dies erneut

Als Antwort auf Shanie

At what point do privacy concerns interfere with basic functionality?

teilten dies erneut

Als Antwort auf dogzilla

that’s extremely dependent on what kind of privacy violation, but privacy concerns interfere with basic functionality when the admin(s) of your instance get(s) lazy, really.

If you have active Admins and you can bring your concerns to their table, or they pay attention to #mastoadmin and do their due diligence, you will have a “safer” server.

teilten dies erneut

Als Antwort auf Shanie

Unlike every other social media, you can just spin up your own instance and be your own admin. Unless you’re paying your admin, you have zero right to demand or expect anything from them and it’s on *you* as a user to whom this (or any other issue) is important to follow that stuff.

If you don’t agree with how your admin runs their instance, fire up your own

teilten dies erneut

Als Antwort auf dogzilla

I never said anything about “demanding” anything from anyone. If you have a shit admin though, or believe they are not healthy for you, yes, feel free to change servers. Only weakness is you “lose” your previous posts but whatever.

But if you are an admin and don’t at least sit and listen to your server, why are you an admin of social media?

teilten dies erneut

Als Antwort auf dogzilla

@dogzilla @chris@strafpla.net @Shanie basically always. You're either constantly consciously deciding what level of compromise you're willing to make or you're giving away your privacy and freaking out over nothing.

teilten dies erneut

Als Antwort auf Shanie

"it's possible to do bad thing, so there's nothing wrong with bad thing actually"

teilten dies erneut

Als Antwort auf lily 🏳️‍⚧️ :flag_pansexual: θΔ ⋐ &

How to take a point and not at all understand what it means for $500, Alex.

It’s possible to do bad thing, so take control of your server and prevent it in an active way.

teilten dies erneut

Als Antwort auf Ryan Barrett

This should be opt-in, not opt-out. BlueSky doesn't use ActivityPub and, therefore, the tools users have to protect themselves on Mastodon are incompatible with your bridge.

I'll be talking with the other moderators and admins of furry-focused servers to inform them of this new risk to marginalized users and I'm confident they'll be taking appropriate actions to keep our communities safe.

Als Antwort auf Kinky Kobolds

@Kinky Kobolds @Ryan Barrett The entire fediverse is opt-out structure by default.

If you want opt-in I recommend moving to or setting up a whitelist instance (an instance configured to only federate with instances added to the whitelist, meaning all instances are opt-in by your admin).

teilten dies erneut

Als Antwort auf Shiri Bailem

I know that public posting means it's readable to anyone on the Internet who finds it. But as long as it's on Mastodon, I still have controls to edit and remove things as necessary. My account being mirrored to another service without my consent removes the ability to control my content.

And besides, the right to reproduce a work belongs to a copyright holder. All it takes is one person who can afford to lawyer up and this becomes a prohibitively expensive lesson in copyright law.

teilten dies erneut

Als Antwort auf Kinky Kobolds

@Kinky Kobolds it's a bridge, so it'll try to reflect those edits across as well... but those edits are also security theater, you only have as much control as each user chooses to let you have (any number of instances may not support those features, or choose to disable them... and you'll immediately have no control).

And as far as copyright: that argument only holds up if you also believe you can also sue every instance in the fediverse for viewing your post.

On top of that even if applicable, Ryan is in the US and the DMCA applies. If you go to a lawyer they'll just write a letter to Ryan and he'll opt you out... you'll get a really expensive lesson in copyright law and he'll just get a really fancy and overly formal opt-out request. (DMCA protects sites like fediverse instances and bridges, you have to issue a take-down request first and then you can't sue until they ignore that take-down request... or in other words, they would have to ignore your opt-out request).

And that's before even getting to the fact that a bridge isn't a host, it's a translator. A lot of people don't understand how federation, let alone bridging works and think this is just scraping accounts and posting the content on bluesky...

Als Antwort auf Kinky Kobolds

@activitypubblueskybridge this is an excellent point. The bridge would effectively remove a significant layer of control that is inherent in the Fediverse and ActivityPub.

teilten dies erneut

Als Antwort auf Kinky Kobolds

I hear you on the distrust of BlueSky. I think it's also important to remember that a lot of these same issues apply to other Mastadon or ActivityPub servers as well.

Mastodon instances honor edits to posts as they want to present the most up-to-date information, but I could see easily imagine an instance presenting a history of edits; that's something we wouldn't really know unless we started looking around the internet.

teilten dies erneut

Als Antwort auf Miles

@Miles @Kinky Kobolds a history of edits is an explicit feature that some demand. Now I'm trying to remember if my server software supports that... would definitely turn it off if it was an optional feature regardless.

Edits are not security, I'd honor a delete but edits? pfft, show me the edit trail so people can't use it to gaslight.

Als Antwort auf Ryan Barrett

you should not be setting this up as opt-out

I didn't consent to be part of your experiment, and if I wanted an account on some other network I'd have one

Als Antwort auf jeremiah

@jeremiah @Ryan Barrett @Sara The entire fediverse is opt-out structure by default.

If you want opt-in I recommend moving to or setting up a whitelist instance (an instance configured to only federate with instances added to the whitelist, meaning all instances are opt-in by your admin).

teilten dies erneut

Als Antwort auf Shiri Bailem

Sure, but this isn't bridging to another Fediverse server.

I have tools within Mastodon to deal with other ActivityPub servers without talking to admins. This isn't that. This is bridging to corporate networks which is what many of us are explicitly trying to avoid.

teilten dies erneut

Als Antwort auf jeremiah

@jeremiah @Ryan Barrett @Sara ... this really is the same as another fediverse server.

A bridge translates between networks, and the typical format is something like user1@bluesky because user1.bluesky@brid.gy, likewise user2@ap turns into user2.ap@brid.gy. You block brid.gy and you've blocked all of it.

The only difference between a bridge and a bluesky instance being on the network is that you won't be able to block just a server on the other network, you have to block either the entire bridge or just one user at a time.

There are already tons of bridges on activitypub to other platforms (if you think Bluesky is bad, look up Nostr...).

Als Antwort auf Ryan Barrett

Just want to say thank you for all your work on this! I'm on BlueSky as well but not comfortable with their VC backing. It's going to be nice to be able to interact with folks on there from my Mastodon account!
Als Antwort auf Ryan Barrett

build bridges not walls is great! being able to add #nobridge to individual profiles seems like a reasonable way for folks to opt out. Thanks for all your work!
Als Antwort auf Ryan Barrett

This need to be opt *in*, not opt out! What the heck were you thinking? I suppose this makes sense if Bluesky is paying you...
Als Antwort auf chronohart

@chronohart @Ryan Barrett because this is the fediverse and people are getting upset that their public federated posts are... getting federated?

"Opt out" is basically just a nice gesture since not all platforms have user level instance blocking.

I've also seen a few people complaining who confuse a bridge with a webscraper and have no idea how a bridge works...

teilten dies erneut

Als Antwort auf Shiri Bailem

There are several reasons people are complaining. One good reason I've seen is that this will expose users to a social media ecosystem that they *explicitly* chose to stay away from for their own personal safety. This would be kind of similar to someone creating a new system to forcibly connect your server to one that your admin already blocked due to its members constantly harassing folks on your server.

Just because you can't imagine this being a problem in your own life, that doesn't mean the problems other people have should be ignored.

You can tell the developer doesn't give a shit what people actually want because he stated, in almost these exact words, if people got the warning about this bridge that an opt in would provide, no one would want to use it. Or "my product will be so unlikable, the only way people will use it is if they don't know it's there".

teilten dies erneut

Als Antwort auf chronohart

@chronohart @Ryan Barrett the only reason I can't imagine it being a problem is because it's so completely manageable... if I get too much trouble over the bridge? I block the bridge.

Starts coming through over a different bridge? Another quick and easy block. And mind you that they have to find a bridge to harass me over and they get what... one harassing post before they have to go find another bridge? That's alot of extra work on their part as bridges aren't that plentiful.

That's before getting to the array of other moderation tools available, well before talking the tools available as a server admin.

On top of that, their opt out system is fantastic, just by a simple tag dropped in my profile block all bridges using this software? Hell yeah, that's a great measure and I hope it catches on elsewhere.

Altogether... I'm more worried about people already here than people accessing through a bridge. I think there are more self-righteous people here than any other platform.

teilten dies erneut

Als Antwort auf Shiri Bailem

@Ryan Barrett @chronohart you also mistake "loudest" for majority, much like the "fedipact" nonsense where a lot of people thought they had enough support to bully Facebook... They were absolutely a small minority of the fediverse, they weren't numerous... just loud.

Most of the people here? We just welcome more people to talk to and more ways out of corporate networks (and this is a way out of a corporate network).

Als Antwort auf Shiri Bailem

bridges that slurp content from the fediverse to bsky isn't getting people out of corporate networks... It's pulling people into one: bsky.
Als Antwort auf Shiri Bailem

so what does the bridge do? Just pretend it's passing content between the two?
Als Antwort auf Ubergeek

@Ubergeek @Ryan Barrett @chronohart it translates protocols, it means when a bluesky user wants to connect to ubergeek@tilde.zone they' try to to go to something like ubergeek_tilde.zone:ap.bridge, the request for the profile will be sent to the bridge which will translate the request to an AP request for a profile to tilde.zone. When tilde.zone replies the bridge will translate the AP profile format to the AT (bluesky's protocol) format for a profile. They'll then click follow, which will send an AT follow request to the bridge which will translate it to an AP follow request to tilde.zone and so on.
Als Antwort auf Shiri Bailem

so... It slurps content from one network, into another, without consent from at least one party, correct?

Because I never consented to being tracked by bsky and used in their LLM and advertising data...

Dieser Beitrag wurde bearbeitet. (2 Monate her)
Als Antwort auf Ubergeek

Then back to my usual suggestion of joining a whitelist instance or only post privately, you're already being fed into LLMs and advertising data from activitypub... and there's nothing you can do to stop that without going full whitelist.
Als Antwort auf Shiri Bailem

If it's so fantastically easy to just drop a hashtag in your bio to block the bridge, why can't that method be used to *join* the bridge instead? We should be operating from a consent-first model. Folks already chose to avoid bluesky *by joining a network that isn't bluesky* and now this bridge is going to force them to actively reinforce that decision.

That's assuming they even know this bridge exists in the first place! As much discussion as there is about this thing right now, there are and always will be folks that don't know anything about the bridge in time to prevent it from touching them. This is going to be yet another complication that folks have to consider when they join the fediverse, which is already criticised for being very complicated for new users.

teilten dies erneut

Als Antwort auf chronohart

@chronohart @Ryan Barrett they're not being ignored, they're just living in an imaginary world.

Here's a simpler way to put it: if this makes anyone feel less safe, then the safety they felt was an ILLUSION, that safety was a lie. Shutting down this one developer doesn't bring back that safety, it just preserves the illusion.

The fediverse is and never was the place to avoid being "on" the other networks. The entire model of it is to be on everything.

If you want the features you claim are being violated you need to be on a whitelist server (a server configured to only federate with pre-approved other servers).

If you joined the fediverse to "not be on Bluesky" then you didn't remotely understand what you were joining. That's not a fault on this bridge, that's a fault on you and whomever might have told you otherwise.

The fediverse is not some enclave, it's not some isolated space, it never will be.

And the fediverse is not safe, never was meant to be a safe place and again never will be.

And why? Because the first and central premise of the entire fediverse is being open. It's safety is about always having an escape hatch... you're safer from horrible admins because you can always jump to another instance and more-or-less stay in touch with everyone... unlike the isolated networks of Twitter or Facebook where you can't move without losing connection to everyone.

And anyone who knows more anything about the history and point of federation knows that bridges are unavoidable and accepted either enthusiastically or reluctantly.

The whole situation here is that you're joining a space and getting upset at the people in that space for doing entirely normal things because you had ideas in your head about what that space was and those entirely normal things violated your imagined ideas.

teilten dies erneut

Als Antwort auf Shiri Bailem

@Ryan Barrett @chronohart and like I've said many many many times throughout here, if you feel bridges violate your privacy, if you feel uncontrolled federation violates your security... that's explicitly what a whitelist server is for, either join or make one and then you'll have the control and isolation you want.

teilten dies erneut

Als Antwort auf Shiri Bailem

Oh *FUCK* you. You do not get to tell people the harm they experienced and the safety they now have is *imaginary*. Wow. There's no help for you. We're done.

@snarfed.org

Als Antwort auf chronohart

@chronohart @Ryan Barrett I'm sure you've already blocked me, but if nothing else for other's sake:

I said nothing about calling harm imaginary, I just called the safety imaginary. That's not dismissing experiences, that's just pointing out that a person's experience to date doesn't mean they are safe.

This is how the fediverse works, and for good or ill, it's part and parcel of being here. I'm not tolerating people calling this harm just because the "harm" is the "perceived loss of security" a security that explicitly does not exist and never did.

A person picks up a revolver and puts it to their head thinking it's got now bullets in it... this situation is like disparaging someone for telling you that there is in fact 1 bullet in that revolver, so you keep pulling the trigger and telling people they're awful for telling you there's a bullet in the gun... all the way up until you find the bullet.

Like I said, if this makes someone feel less safe here, then you were never as safe as you believed yourself to be.

Als Antwort auf chronohart

One thing that occurs to me is the bluesky TOS:

"By sharing User Content through Bluesky Social, you grant us permission to: <lots of stuff>"

An opt out bridge simply can't obey that.. they don't have rights to grant permission to mastodon posts they don't own. Opt in they can have a TOS with similar wording that says you agree to allow that stuff to happen.
1/2

teilten dies erneut

Als Antwort auf Tony Hoyle

2/2
(Some of that is solvable by people licensing their posts under CC for example, but there's no common mechanism for it yet.. and it's not certain whether BS would accept that as complying).
Als Antwort auf Tony Hoyle

@Tony Hoyle @Ryan Barrett @chronohart That's one of those things that applies equally to ActivityPub servers and bridges, the bridge doesn't change this situation, if Bluesky gets sued successfully over that then all of ActivityPub shuts down too.

Regardless, TOS isn't required, the counter argument as that you're explicitly sharing your posts to be publicly federated, shared, and reshared across servers.

TOS isn't about it being necessary to function at all, it's just "cover-your-ass" legal text to make things simpler (ie. rather than having to make arguments they can just point to a line in the TOS).

Als Antwort auf Ryan Barrett

This is bad news. Don’t do it. You seem to have decided that everyone should be subjected to your brilliant idea.
Als Antwort auf Don Ray

@Don Ray @Ryan Barrett yet you decided the same for us with this comment?

If you take issue with how your public federated post is federated... then you should join a whitelist instance.

teilten dies erneut

Als Antwort auf Ryan Barrett

Wow. This is just such an epically bad call. I can't imagine reading the room this badly.

ANY privacy advocate you talk to - and I really suggest you talk to a few - will give you the burning side-eye for thinking you have the right to force folks to opt out.

And you should definitely look into the fact that you may be violating the GDPR. Someone else certainly will.

Als Antwort auf Grrrr, Darth Moose Shark

@Grrrr, Darth Moose Shark @Ryan Barrett it neither violates the GDPR (and if you think it does you either woefully misunderstand what a bridge is or what the GDPR covers), and as a privacy advocate... any privacy advocate that actually cares about their privacy rather than the vague concept of privacy would shrug at this.

You posted publicly and it's visible on another instance... that's all that's happening here.

I've noticed others below seem to think this is something like a web scraper or that it will do something invasive? A bridge just translates between protocols, once this is up it just means that bluesky users and activitypub users would be able to talk to eachother through this instance with it translating requests between the two (ie. user1@bluesky wants to follow user2@mastodon, they'd follow something like user2.mastodon@brid.gy; user2 will get a follow request from something like user1.bluesky@brid.gy; if they accept then they'll be sharing their posts between eachother)

teilten dies erneut

Als Antwort auf Shiri Bailem

Just thinking out loud: I‘m not so sure about that. I think even „regular“ federation among Mastodon instances might be problematic in a GDPR context, no? If your instance is not using a whitelist-concept, but federates with everyone, there’s no way for the user to agree or be informed about all the servers which are processing your data.
Als Antwort auf Michael T. Richter

I did not consent to your dumb post getting federated to my good server, shut the fuck up
Als Antwort auf Michael T. Richter

you have to appreciate someone so openly breaking their instance rules about proper conduct.

It makes it easier to report and block them.

teilten dies erneut

Als Antwort auf Ryan Barrett

Ryan,

How refreshing!

Another bridging mechanism to extend the reach and interoperability with other Fediverse protocols in the #DeSoc space is most welcome, and from the limited analysis I've been able to perform so far this is a novel approach to what some point in the future will find other Fediverse platforms incorporating in their network stacks.

So far, we've got seamless nostr interoperability to add to the other fine protocols such as Diaspora, ZOT, Nomad, OStatus, ActivityPub, and others in the mix. You might also wish to take a look at the repo for Minds to see how they've made seamless integration between the ActivityPub and nostr portions of the #Fediverse as well, and oh, pay no mind to the infantile and disparaging remarks that some small minded folks in this thread have exhibited - they are free to *defederate themselves from the Fediverse at any time.

We've been following withe some enthusiasm your project in the Fediverse-City community and it would be a pleasure to have you participate there. Your insight into the open and public aspects of Fediverse traffic in the #DeSoc world is a testament to the innovation and evolution that is possible in obviating the proprietary, privacy disrespecting, deprecated monolothic silo networks that have sowed so much acrimony and subjugation over the very people whom they seek to quantify as their business products.

You're performing a great service here, feel free to block any miscreants in this thread who don't understand the definition of public.

Also, might I suggest that instead of offering a `#nobridge keyword index, you think about offering a solution as a FEP here?:
codeberg.org/fediverse/fep/

There are a lot of Fediverse platform developers I'm sure that you'll find welcoming, encouraging, and willing to offer assistance in formulating solutions to silence the adolescent juvenile mindsets that have been berating you in this thread for your selfless commitment to the well being of us all.

In the future, the Fediverse that we perceive and interact within will become its own heterogeneous superset of networking protocols to facilitate effortless communications between individual parties regardless of which portions of the Fediverse and their associated protocols implemented. Just like #OStatus has been largely supplanted by ActivityPub, and #ZOT has been superseded by #Nomad, the ActivityPub portion of the Fediverse will also eventually be deprecated and replaced by other stacks that will emerge from the ether of creativity. In the meantime, we'll be bridging between the various protocol stacks, and Bridgy-fed is one of those tools that serves to make that a reality :)

Thank you again, for your selfless contribution to #DeSoc and the Fediverse. it's a fantastic achievement that will serve to benefit many in both the #ATP and #ActivityPub portions of the Fediverse!

#tallship #bridgy #FOSS #Fediverse #DeSoc #innovation

⛵️

.

Als Antwort auf Ryan Barrett

To the people on this thread who talk about GDPR violations: I’d be interested in the specific clause in the GDPR that you believe a bridge like this violates. Curious.
Als Antwort auf Johannes Ernst

Johannes, There isn't one - they're talking out of their ass.

They're just making noise and emotionally distressed to discover that this is how the #Fediverse currently works, and always has worked - and it's not just the #ActivityPub portions of the Fediverse, or even the Fediverse - it's the entire #Internet...

"If you affect a public post, you have no expectation of privacy".

For those who still feel some sense of having been offended, I welcome them to unplug their computers and toss their iPhones and Androids into the trash. That's really their only option, and they'll come to that realization some day, maybe, and it is of no consequence for anyone else in the world if they don't.

#tallship #FOSS #networking #privacy #ignorance

⛵️

.

teilten dies erneut

Als Antwort auf tallship

The counterpoint is that people generally respect CC licenses (weakly) attached to their creations. (For people != the AI crowd)

We need something similar to that — well, inspired by — for posts. I’m sure Ryan would gladly honor “do not propagate to for-profit entities”, for example, if it could be attached to a post.

@fediversenews @fedidevs @activitypubblueskybridge @snarfed.org

teilten dies erneut

Als Antwort auf Johannes Ernst

Yes, we do try to respect the Creative Commons licenses - it's a great thing.

And statistically, studies have revealed that we also do our very best to respect the wishes of publishers who rebuke and refuse to allow their works in a distribution channel where items are DRM encoded.

People should have more faith in the intentions of folks trying to do good, methinks :)

There will always be bad actors

teilten dies erneut

Als Antwort auf tallship

a believer in the goodness of people! I thought that species went extinct! Is there a club I can join?

teilten dies erneut

Als Antwort auf Ryan Barrett

honestly fuck you. Do you really expect everybody to have enough space in their bios to opt-out of your fucking bs? How many opt-out bs am I supposed to put there?

teilten dies erneut

Als Antwort auf Joshix


I'm happy to opt you out manually, as I mentioned, you don't have to change your bio.


honestly fuck you. Do you really expect everybody to have enough space in their bios to opt-out of your fucking bs? How many opt-out bs am I supposed to put there?

Als Antwort auf Ryan Barrett

@snarfed.org@fed.brid.gy I think you do not – or perhaps deliberately do not – understand the concept of “informed consent”. I am going to give you the benefit of the doubt and assume that you have good intentions here. The road to hell is paved with those, and this is going to be another slab.

You are also assuming that people who do not want this will somehow be aware that this is happening, find your blog post (that nobody will ever read) and then realise they should put a hashtag in their bio to remove themselves. That’s not really an “opt-out” because how will anyone know this is happening? Even if a hundred people boost your primary post, that is only a small selection of all fediverse users, let alone instances that even know.

That means there is no way that any given user will even know they can opt-out of something that they do not even know is scraping them. How can you moderate user behaivour when you do not even know this is happening in the first place?

Especially since this means our posts will be on BlueSky, without any recourse for us to remove them from BlueSky because we do not have a consent agreement with BlueSky.

This is also highly illegal under the GDPR, which applies in the EEA and UK, which means you are breaking the law of 30+ nations at the same time. So not only are you just oblivious to the concept of “hey, I don’t like my posts being on BlueSky”, you are also oblivious to your legal requirements as a data handler.

Als Antwort auf Yasberry Pi 3 Model B+ :baba_baba_yaseen: :agenderFlag: :transgenderFlag:

@New Yastendo 3DS XL :baba_baba_yaseen: :agenderFlag: :transgenderFlag: @Ryan Barrett consent comes from posting publicly on the fediverse and is easily revocable by blocking their bridge.

Additionally, the way bridges operate normal moderation tools continue to exist just fine. Users and instances can block the bridge easily from their end if they have any issues, the opt-out mechanism here really is just an extra courtesy that's largely unecessary.

As far as posts being "on Bluesky" it's really important to note that your post will be "on Bluesky" to the exact same extent that it is on my server. Bluesky promised ages ago to federate, just under their own protocol which they're releasing and subsequently federating to. This is not echoing posts onto the Bluesky server (that's explicitly not a bridge, that's a mirror account), as a bridge all it's doing is translating requests between ActivityPub and AT (their protocol).

Additionally GDPR only applies within compliant countries (OP is in the US), this could theoretically apply if someone were to run their own copy of this in a GDPR compliant country, but it would also apply similarly to many other ActivityPub functions and activities (is every server using a relay in violation of the GDPR because it's a nearly identical process on a technical level?)

Als Antwort auf Joshix

@Joshix 🦣 @Ryan Barrett ... notice that they didn't make that the only option, just a passive option that doesn't involve sending a special request. Just ping them a message with "I'd like to opt out of your bridge", done.

Or if you don't want to interact with them, lookup how to block a domain in mastodon and you'll be covered even better.

Als Antwort auf Ryan Barrett

@Ryan Barrett @Ryan Barrett

I use Friendica. And friendica hast a bluesky-adapter built-in.
As admin i can activate it, and users can configure it for their needs...

So... instead of building such bridges it would be a great idea to build native support for different protocols in the services like mastodon, pleroma, *key...

Fill feature-requests to your projects to build a pressure-peergroup for your devs to demonstrate the need for.

For my part...
I left the commercial serviceproviders, when i discovered the fediverse. They are destroying the internet and they are also destroying democraties all over the world with their algorithms and monetarization of their users ...

This is evident. Free democratic countries do not need humanophobe tech-bros from silicon-valley or somewhere else.

So... i won't support their business-model. Free internet works by people like me, who host their own services, and work by devs of free software, who build code for selfhosters.

Think about, whose business you will support with your bridge.

Als Antwort auf jakob 🇦🇹 ✅

@jakob 🇦🇹 ✅

> I use Friendica. And friendica hast a bluesky-adapter built-in.
> As admin i can activate it, and users can configure it for their needs...
>
> So... instead of building such bridges it would be a great idea to build native support for different protocols in the services like mastodon, pleroma, *key...

I am also an administrator of Friendica and for this very reason I know that I cannot ask the developers of the other social networks in the Fediverse to develop special connection bridges with other social networks.

In fact, Friendica is a software that was born "hyperconnected by design": today it supports Bluesky and Tumbir and I remind you that Friendica also supported Facebook and Twitter, at least until these social networks removed support for their APIs!

For this reason you shouldn't worry about the bridges that are about to be built: the nice thing about bridges is that they connect to other places, but in case of danger they can be blown up.

@Ryan Barrett @Ryan Barrett

teilten dies erneut

Als Antwort auf Ryan Barrett

Hi @Ryan Barrett
as a Friendica user I already have the possibility to connect to the world of Bluesky, but I'm really happy that you are creating a useful tool for all other users of the fediverse!

Bluesky is a project with many critical issues and with volumes that can be problematic to manage for the instances of the Fediverse, but it is objectively a very interesting environment that is attracting the best of the users who had remained on Twitter but who unfortunately had not managed to settle into the architecture of the Fediverse.

Every project designed to create bridges deserves to be respected and supported.

For this I thank you!

@Ryan Barrett

teilten dies erneut

Als Antwort auf Ryan Barrett

You can go ahead and opt out all of mastodon.art until your bridge is FULLY opt-in.

You've been here since 2017? Long enough to have seen enough entitled techbros think they can claim some kind of ownership over people's data here and use it without consent, and get railed for it.

Opt out is not consent. Fuck off.

teilten dies erneut

Als Antwort auf Mastodon•ART 🎨 Curator

@Mastodon•ART 🎨 Curator @Ryan Barrett ... why don't you just block the instance?

You've been here how long and you think you're entitled to how your posts are federated beyond who you block? Sure you don't want to switch your server to a whitelist server instead?

teilten dies erneut

Als Antwort auf Shiri Bailem

@snarfed.org@snarfed.org We did block the servers ;)

teilten dies erneut

Als Antwort auf Mastodon•ART 🎨 Curator

You may want to reconsider your "Fuck off" comment while on mastodon.art:

mastodon.art/about/more#code-o…

teilten dies erneut

Als Antwort auf Anders Borch

I left mastodon.art because of these types of inappropriate admin behaviour and (imho) questionable admin decisions a long time ago. They want to control how and with whom their users communicate instead of leaving that to the users as it should be.

teilten dies erneut

Als Antwort auf Ryan Barrett

i like the #nobridge in the account description, but I think you also should respect the #nobot. I don't want to finish with 3000000 hashtags in my description

teilten dies erneut

Als Antwort auf retiolus

@retiolus @Ryan Barrett Biggest problem is that there are plenty (and likely more) people who don't want to deal with bots but who don't mind bridges

The hashtags in description is unfortunately just a limitation of AP until they come up with some other method to set a flag like that. (Think of it like how hashtags themselves weren't a feature anywhere until after people had already been using them in their posts on Twitter for quite a while)

teilten dies erneut

Als Antwort auf Ryan Barrett

Thanks for your work on this valuable feature for the Fediverse AND for your transparency and willingness to listen to the feedback of the community.

Please, don't let the loudest and most hostile voices discourage you.

Clearly, we all need to do better at communicating how the Fediverse works and setting realistic expectations about privacy on this network.

teilten dies erneut

Als Antwort auf Ryan Barrett

lovely, thanks for creating this, looking forward to talking to old and new friends on #Bluesky from the comfort of my #Mastodon account !! so please by any means opt me in (should it come to it)

teilten dies erneut

Als Antwort auf Ryan Barrett

If you'd like to use our content, how about paying us for it?

Or at least consider the copyright position of each post/account rather than assuming what we produce is free for you to re-use.

teilten dies erneut

Als Antwort auf Andre

@snarfed.org@snarfed.org
Andre, you know, this public post you just wrote, has been temporarily cached by my pleroma server. I wonder if you consider that i'm using your content by simply answering you.

teilten dies erneut

Als Antwort auf Luca Sironi

That would be using the content as intended. In the same way that allowing a browser to cache a web page doesn't entitle the browser use to then republish that content under their own domain.

Similarly, owning and using a DVR doesn't grant one the right to sell copies of a TV show.

I can borrow a book from a library, but that doesn't entitle me to photocopy it, rebind it and sell it to another library.

teilten dies erneut

Als Antwort auf Andre

so i'm preemptively good person/ server because i use activitypub but you don't trust bluesky the company, because they are using that other AT protocol.

But once they opened their protocol, it's not just their company using it, other no profit actors can use it as well.

There are mastodon servers owned by company already.

teilten dies erneut

Als Antwort auf Luca Sironi

I'm not anti-corporate at all. I have no problem with a large entity implementing native activitypub and interacting natively with the community.

I do not see bridges/gateways that republish content as that at all.

Further, I understand there's a difference between offering someone a beer and having them walk into my house and help themselves to the fridge.

teilten dies erneut

Als Antwort auf Andre

@Andre @Luca Sironi in your metaphor this isn't them coming into your house, this is you put a beer on a table labeled free beer for people to come and take. Most people are just taking them and drinking it themselves. You're upset because someone took it and gave it to their friend.

teilten dies erneut

Als Antwort auf Shiri Bailem

No, I'm upset because this is a private beer party and you gatecrashed and you're handing the beer to your shady friends in the back alley.

I get your mindset. If you get touch it, it's yours. The mindset that sees nothing wrong with ripping people's writings and republishing them. Nothing wrong with helping yourself to any photograph you see on the internet and using it for whatever purpose you see fit. Scrubbing the author's names off and feeding them into your content farm.

You are not invited to my party.

teilten dies erneut

Als Antwort auf Andre

@Andre @Luca Sironi that just means you joined the fediverse and had bad assumptions about what it is. A "private beer party" in terms of the fediverse is a whitelist instance (an instance that only federates with explicitly pre-approved instances).

You don't get my mindset, what you don't get is what the hell federation is and what the fediverse is all about. This has been the norm for longer than the fediverse existed and sure as hell longer than you've ever been on it. Stop pretending the fediverse is Mastodon and new, and that your assumptions about a space are the absolute truth.

Bridges between federated networks are normal, they don't do opt-in, doesn't matter if one is commercial or not. If you're upset about this then that only means you made assumptions about what you were signing up for or you were outright mislead by someone else.

Als Antwort auf Luca Sironi

It's not a matter of trust; it's a matter of choice. I (and many others) made the *choice* to not touch bluesky and now that choice is being taken away from everyone, by default, unless the individual user happens to know this is coming and hoe to stop it.

When the alternative is to flip this "simple" opt-out to an *equally simple* opt-in, the decision to make it opt-out is a decision to take choice away from your demographic in order to artificially enhance the user uptake of your product.

@PCOWandre @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf chronohart

Let's be honest most people have no idea this bridge is going to exist. So, they can't opt-in. If nobody opts-in, you won't be able to search for them by their ActivityPub handles. The bridge isn't useful. People on both sides who would like to reconnect with their friends won't be able to. However, if you know you hate BS, you can add the bridge to your personal block list and it isn't an issue for you.

teilten dies erneut

Als Antwort auf Jamie Booth

What if I block #BS (just love the acronym 😉) and the BS #bridge but one or more of my followers who ARE "bridged" boost or link my content? Will it appear on #BS?

@chronohart @luca @PCOWandre @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf HistoPol (#HP)

This is a really good question and I don't know the answer. This is the kinda of thing I think we should be asking about the bridge.

@snarfed do you know the answer to this?

teilten dies erneut

Als Antwort auf Jamie Booth

It’s seems likely this will happen as a boost creates a new post.

teilten dies erneut

Als Antwort auf Oliphant

@snarfed.org
I'm wondering if that means there may be a functional difference between blocking the bridge vs adding the #nobridge tag?

teilten dies erneut

Als Antwort auf Jamie Booth

@Jamie Booth @Ryan Barrett @Oli @HistoPol @Luca Sironi @Andre @chronohart @Ryan Barrett a boost in this case will operate the same as with normal ActivityPub, in which case the block should remain honored. It'll be the exact same as someone boosting your post and whether someone you blocked on AP can see that post.

I'll note however that the bridge should not be a concern if you're worried about that, instead you should be concerned of the thousands of instances like mine (Friendica and Hubzilla) that will natively support Bluesky. If we boost your post, then it'll be copied over to Bluesky with no actual connection to you in the network, so your blocks will not apply and you will have no control over the post afterwards.

teilten dies erneut

Als Antwort auf Shiri Bailem

#Bluesky #Block

Very concerning, indeed.
How would I go about this?

Would I need to block any and all friendica and hubzillla instances?

"you should be concerned of the thousands of instances like mine (Friendica and Hubzilla) ...boost your post, then it'll be copied over to Bluesky with no actual connection to you in the network, so your blocks will not apply and you will have no control over the post afterwards."

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol It is my understanding that boosts won't be passed on if you block the bridge or add #nobridge to your profile because the boost still has you as the original author. This would be true no matter which software a person is using.

But if someone quotes you (on any platform, not just the ones mentioned) or takes a screenshot of your post, that would not be blocked. And people can do that now without the bridge. Windows comes with software that allows people to take screenshots. So do phones. And most other fediverse platforms other than Mastodon allow quoting.

The fediverse has over 100 different projects and multiple protocols already connected to it. If you are concerned that people will quote you or boost you on other networks, you might want to consider a whitelist servers where you only allow approved Mastodon instances.

With or without the Bluesky bridge, you are about to be outnumbered by Threads, WordPress, and other projects coming online. ActivityPub is an open network, after all. Always has been.

But the nice thing is that you can control who you connect with by blocking or whitelisting. In your case, being on a whitelist server would probably address your concerns.

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf Scott M. Stolz

Thanks a lot, Scott.

I am aware of several of these things. A friend of mine, stefanbohacek.online/@stefan, created jointhefediverse.net to remedy this lack of undesirable for newbies and no-nerds.

I know what #whitelisting is general, but how would I go about this on #Mastodon?

The whitelist, if I don't want to do everything manually (no-go,) would need to be "intelligent" and able to discern the platform s.o. is using for his handle...

I can live with the screenshot issue.

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol

I know what #whitelisting is general, but how would I go about this on #Mastodon?

The whitelist, if I don't want to do everything manually (no-go,) would need to be "intelligent" and able to discern the platform s.o. is using for his handle...


I don't use Mastodon, so I don't know for sure. Some people have mentioned that there is a whitelist mode that is called "limited federation mode" or something like that. The admin would have to turn that on since it is for the whole instance.

If you don't want to use whitelist mode, people have been talking about blocklists that can be imported into Mastodon. I am not familiar with how they work. Maybe someone who uses Mastodon could answer this one?

teilten dies erneut

Als Antwort auf Scott M. Stolz

In short, it's just like blocking one-by-one but as batch-action. Admins can also block domains using wildcards, I think.

However, either would not work to block specific software. You would indeed have to use an instance in limited federation mode, where each connection is checked one-by-one, to avoid federating with Friendica and Hubzilla instances that could copy your posts over.

teilten dies erneut

Als Antwort auf Qazm

@Qazm There are other options, like using a platform that has privacy, access lists, permissions, and better moderation tools. Mastodon only has block lists, which limits user's control over their own posts.

For example, on Mastodon you can block someone so you can't see their posts, but you can't stop them from replying to posts they have already seen. On Hubzilla, you can actually turn off commenting on your posts so no one can reply or so that specific people can't reply, and can even delete other people's replies to your thread. You control the conversation in your thread. You can't do that on platforms like Mastodon.

Also, on Hubzilla, it is all about user choice. So if Hubzilla implements the Bluesky protocol, both the admin AND the user would have to opt-in. Users would have to actively turn on the Bluesky addon to federate with Bluesky. Otherwise none of their posts will ever be sent to Bluesky. I am pretty sure Friendica will work the same way.

So Hubzilla and Friendica would actually do a better job at blocking Bluesky than the bridge does. And the bridge actually has a lot of options for blocking Bluesky.

So instead of blocking Hubzilla and Friendica, you probably want to start using it instead, since it gives you better protection against Threads and Bluesky than Mastodon does.

@Qazm

teilten dies erneut

Als Antwort auf Scott M. Stolz

@scott I don't think so. Other Hubzilla or Friendica instances that receive a Hubzilla post over AP can still boost it over there, right?

The reply control from your instance won't stop Mastodon users from replying either (though it will stop you seeing those replies, and to some extent will reduce the visibility of replies).

I think it all comes down to what's outlined in foggyminds.com/display/c6ef095… (saw that post a little after my reply above) and open federated social media in general being built around own-access-choices rather than data control, outside of posting modes with very limited reach which *should* be implemented with more privacy than they are.


@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett The gist is that if you want to prevent your posts from being shared outside of screenshots and quote-posts (where the contents of the post are just copied) the only option is to join a whitelist-only server.

These are servers that federate only with explicitly approved servers, ie. if someone tries to connect from any instance not on that list they're blocked by default.

That's kinda the root of the argument here where a great many people have a false assumption that the fediverse is about control of your data when it is quite the opposite. It's like trying to protect your art from being used by others... by marking it Creative Commons.

The entire design of all federated systems is around open sharing, you can only get control over how your posts spread in a closed system with little or no federation.

As far as whether or not you use those platforms, my example was regardless of whether you're a user.

My server federates across multiple different protocols, if I boost your post then your post is probably being made available to multiple different networks automatically.

The protections and control involved in federated networks is not in how your data is shared, but in how your access is controlled.

In the fediverse you don't have to worry about a bad admin blocking your access to everyone you know, you can freely move accounts between instances. If you piss of Elon for instance, you're cut off from Twitter and everyone on it... full stop... but if you piss off your instance admin, you just move instances and can still connect with everyone.

It's also control over your experience in that you're not relying purely on what their algorithms think you should see. If the instance your on has an algorithm set up that you don't like, then you can move instances to one that has the algorithm you like.

You also have protections against enshittification (the process by which those other networks will draw you in with great features, and then once you're locked in slowly shut down or degrade those features). If features that are important to you start getting shut down on your server... you can move to one that keeps them. If a platform developer does it, another developer can fork the project to keep those features alive.

You also have choice in terms of clients and experiences. You're using Mastodon and I'm on Friendica (I know your instance type because Friendica shows me a little icon beside posts). I vastly prefer the Friendica experience, and I have the choice to use that. And I can use that without forcing you to use the same interface.


Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf Qazm

@Qazm That was sort of my point. If you want to have more control over who can see and respond to your posts, you probably should stop using Mastodon and switch to a platform that supports privacy, access control, permissions, and moderation.
@Qazm

teilten dies erneut

Als Antwort auf HistoPol (#HP)

Very concerning indeed. I would suggest logging off and going outside if this is a concern for you.

teilten dies erneut

Als Antwort auf Shiri Bailem

"...Friendica and Hubzilla) that will natively support Bluesky. If we boost your post, then it'll be copied over to Bluesky with no actual connection to you in the network,..."

Besser another question, as so far, I had been in favor of #Friendica;

Does this mean if I were 2 use these 2 platforms, I could never prevent my posts / content from being seen on #Elmo's PayPal platform?!?
Or is there really no difference?
@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett The gist is that if you want to prevent your posts from being shared outside of screenshots and quote-posts (where the contents of the post are just copied) the only option is to join a whitelist-only server.

These are servers that federate only with explicitly approved servers, ie. if someone tries to connect from any instance not on that list they're blocked by default.

That's kinda the root of the argument here where a great many people have a false assumption that the fediverse is about control of your data when it is quite the opposite. It's like trying to protect your art from being used by others... by marking it Creative Commons.

The entire design of all federated systems is around open sharing, you can only get control over how your posts spread in a closed system with little or no federation.

As far as whether or not you use those platforms, my example was regardless of whether you're a user.

My server federates across multiple different protocols, if I boost your post then your post is probably being made available to multiple different networks automatically.

The protections and control involved in federated networks is not in how your data is shared, but in how your access is controlled.

In the fediverse you don't have to worry about a bad admin blocking your access to everyone you know, you can freely move accounts between instances. If you piss of Elon for instance, you're cut off from Twitter and everyone on it... full stop... but if you piss off your instance admin, you just move instances and can still connect with everyone.

It's also control over your experience in that you're not relying purely on what their algorithms think you should see. If the instance your on has an algorithm set up that you don't like, then you can move instances to one that has the algorithm you like.

You also have protections against enshittification (the process by which those other networks will draw you in with great features, and then once you're locked in slowly shut down or degrade those features). If features that are important to you start getting shut down on your server... you can move to one that keeps them. If a platform developer does it, another developer can fork the project to keep those features alive.

You also have choice in terms of clients and experiences. You're using Mastodon and I'm on Friendica (I know your instance type because Friendica shows me a little icon beside posts). I vastly prefer the Friendica experience, and I have the choice to use that. And I can use that without forcing you to use the same interface.

teilten dies erneut

Als Antwort auf Shiri Bailem

(1/n)

I think I owe you a quick #INTRO, as I have not been in contact with you before, so you might better understand my concerns.

I am a political commentator, as well as an activist. This is why I cannot remain silent:

This is a global super-election year. #Democracy is up for grabs in about 50 countries.1)--This is how the billionaires and the #autocrats like #Putin and #Xi see it, or how #YoelRoth...

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@activitypubblueskybridge
AP-AT-BridgeGroup

Very interesting, how is it possible that you boosted my #Intro thread, even though I have #NoBridge in my bio and am not even a member of your group?!?

@shiri @jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

It's because that's not the bridge, that's a Friendica group about working on such bridges. Friendica supports group accounts that you post to by tagging the group.

Group accounts work by boosting every post that tags them.

The initial post was made to the Fediverse News, Fediverse Developer Discussion, and AP-AT-Bridge Group groups, which is why you'll see them boosting almost every comment throughout this entire thread. Anyone who didn't explicitly removed them from the references is posting to that group as well.

The bridge will not appear as a single account. The bridge will translate accounts through it, so if I made an account named Shiri on the official bluesky server, then followed you through the bridge you would see a follow request from shiri:bsky.social@bsky.brid.gy (name formatting probably will differ slightly), likewise that would be the name that would appear for everything I do through the bridge with your account.

If you wanted to block my specific bluesky account from accessing your account, you could block it as normal and it'll work just the same as it always has.

With # NoBridge in your bio, when I go to look up your account through the bridge I either won't get anything at all as if you don't exist or it'll tell me that you've opted out of the bridge.

@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett

teilten dies erneut

Als Antwort auf Shiri Bailem

Thanks for the explanation, Shiri.
I pay attention to such thinks, but even with hindsight, I do not see such a group reference.
On #Mastodon, groups are also possible, but I forgot how to use them, as I used them so little.

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

Unless it was recently added, groups are not a thing on Mastodon itself. I do know in the Mastodon side of things a lot of people use Guppe: a.gup.pe/ for groups, which work in the same fashion as Friendica groups, just with no moderator/admin.

In the case of the groups, all 3 have it in their description that they're groups.

Because Mastodon has no support for groups there's no indicator anywhere other than the description that an account is a group account.

@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol

I pay attention to such thinks, but even with hindsight, I do not see such a group reference.


That's because Mastodon doesn't tell you that

  • it's a group (because Mastodon doesn't understand the concept of groups)
  • it's on Friendica (because Mastodon does its best to shield the existence of non-Mastodon Fediverse projects from its users)


On #Mastodon, groups are also possible, but I forgot how to use them, as I used them so little.


Not yet. They're working on it. And everything else that has working groups/forums now is afraid that Mastodon will re-invent the wheel in a way that's the most incompatible possible to what already exists on more than half a dozen Fediverse projects.

What you mean is probably Guppe, but that isn't built into Mastodon and a far cry from what's possible on Friendica.

CC: @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Groups

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol

I am a political commentator, as well as an activist. This is why I cannot remain silent:


For someone like you, you would probably want to post publicly, to as many platforms and protocols as you can, so you reach a wider audience. But you would need to choose a platform with better permissions and moderation tools.

For example, you would want to control who can comment on your posts and be able to delete comments that are toxic. Mastodon does not have this capability, but most platforms that have threaded conversations give you that ability.

teilten dies erneut

Als Antwort auf Scott M. Stolz

" But you would need to choose a platform with better permissions and moderation tools.

For example, you would want to control who can comment on your posts and be able to delete comments that are toxic. "

Very true.
However, I have a very strick block policy and in 98% of cases, the threat of using it, helps.
I always wonder a little bit what happens, after I block s.o.
My understanding is, that his/her posts remain, but we cannot see each others posts anymore (counter-block, mostly)

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol On platforms like Hubzilla and Streams (and most other platforms that support threaded conversations), you have more control.

Basically, a threaded conversation is a container, and the person who started the conversation controls what goes into that container. If you, as the person who started the conversation, don't like what someone said, you can delete their post. Since it is part of your container, a delete notification goes out to everyone participating on your thread and the post gets deleted for them too. The person who originally posted it would still have their copy, and their followers might still see it, but it would no longer be distributed via your thread to people following the thread. You can also prevent someone from commenting on your post at all, which in that case, their comment gets rejected and is not distributed to anyone.

It works similar with forum topics, except the forum owns the initial conversation. The administrator or moderator can delete posts and restrict commenting.

The threaded conversation model gives you more control over the conversation than non-threaded platforms based on pre-X Twitter.

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf HistoPol (#HP)

(2/n)

...former head of #Twitter's Trust and Security department, might have phrased it. 2)

We have all seen what has happened to #Twitter. What many still don't know, is why he is supposedly burning a lot of money with the purchase: 3).

#Musk and his #TESCREAL 4) adherents from Silicon Valley are vying for world domination. #Elmo already is the world's most...

Als Antwort auf HistoPol (#HP)

(3/n)

...influential fascist, just considering his market power regarding #SpaceX 5) and the "voice" he has as #X owner. By turning off his #StarLink service in #Crimea, he has successfully prevented potentially victorious strikes by #Ukraine against #Russia's invasion force.

But they are not the only #billionaire group vying for even more power. The most...

Als Antwort auf HistoPol (#HP)

(4/n)

... successful has so far been the #FederalistSociety in conjunction with the #CenterForNationalPolicy (#CNP), among whose major feats are putting #Trump in the #WhiteHouse and hijacking the #US #SupremeCourt. 6)

#Autocrats like #Putin and #Xi trying to gain influence through military and economic means are the other group of people trying to destroy #Western #democracies by disseminating...

Als Antwort auf HistoPol (#HP)

(5/n)

... #disinformation and carrying out #CyberWarfare.

And, last but not least, another, even more dangerous #PayPal of #Elmo, #PeterThiel, is enabling governments around the globe to get rid of opponents. The dangerous spyware he owns, #Palantir, is being used e.g. to hunt down investigative journalists in #SouthAmerica 8) and elsewhere 7) and for #discriminatory...

Als Antwort auf HistoPol (#HP)

(6/n)

...#PredictivePolicing. 8)

*2024 certainly isn't the year to remain silent:*

#Poland lost and regained its democracy twice already.

The *US* might lose it to a ruthless autocrat in 2025.

And #Ukraine is fighting tooth and nail for its #democracy.

//

FOOTNOTES:

1) weforum.org/agenda/2023/12/202…

2) mastodon.social/@HistoPol/1110…

3) mastodon.social/@HistoPol/1100…

4) mastodon.social/@HistoPol/1105…

...


(1/n)

I know a lot of people don't want to hear about the #BorgSite or #Elmo anymore.

However, until #Twitter is either broke or #nationalized, or #Elmo in jail, or at least not able to control the #DeadBirdSite anymore, the following is very important to know about #Musk’s #TwitterTakeover:

One central key to understanding is this insightful article by @davetroy :

"👉#Musk’s Twitter Buy Makes No Sense — Unless It’s Part of Something Bigger👈"

I had this...

bylinetimes.com/2022/11/07/mus…


Als Antwort auf HistoPol (#HP)

For journalists the value of the fediverse is in not getting silenced. It's here to amplify voices in that fashion so that nobody can be silenced, for good or ill (ie. you can block Nazi instances so you don't see them, but you can't stop a Nazi instance from existing or sharing content).

If you operate in a "I control where my message goes" manner, then you're operating in a manner that can be very easily silenced. It drastically limits your reach.

It's one of those fundamental things where you can't have it both ways, control over your reach is inherently limiting to your reach.

And when talking about the fight against fascism, uncontrolled spread is very much preferable as they can't silence you. If you are careful in your security you can post from an account until the fascists shut down your server... but the post will still be out there floating around. And you can just as easily stay on the network by starting a new account every time they shut down a server... they'd have to shut down the whole network to stop you.

Bridges make it even harder for them because then you can also jump between platforms and if they can't shut down your server they'd have to shut down every single bridge... which new ones can be started with trivial ease (a lot less work and resources than starting up normal instances).

There's nothing they can do to you over a bridge that they can't already do without a bridge, in fact they have less control through a bridge. But you on the other hand have your voice amplified even further.

Additionally the whole fediverse gets stronger as it encourages development on both sides, if one starts lagging behind in features/quality it permits users to move without "leaving" the fediverse.

If Bluesky starts pumping hardcore propaganda and silencing leftist voices... then the bridge offers a light, showing the abuse and giving them a way out that doesn't involve starting over from scratch.

@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett

teilten dies erneut

Als Antwort auf Shiri Bailem

"If you operate in a "I control where my message goes" manner, then you're operating in a manner that can be very easily silenced. It drastically limits your reach.

It's one of those fundamental things where you can't have it both ways, control over your reach is inherently limiting to your reach."

Excellent point, Shiri. Taken.

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf Shiri Bailem

(1/2)

"If you operate in a "I control where my message goes" manner, then you're operating in a manner that can be very easily silenced. It drastically limits your reach.

It's one of those fundamental things where you can't have it both ways, control over your reach is inherently limiting to your reach."

Excellent point, Shiri. Taken.

However, please...

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf Shiri Bailem

"...have to shut down the whole network to stop you.

Bridges make it even harder for them because then you can also jump between platforms and if they can't shut down your server they'd have to shut down every single bridge..."

I begin to like #bridges. #FascismProof and #AutocracyProof, so-to-speak :)

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol

I begin to like #bridges. #FascismProof and #AutocracyProof, so-to-speak :)


That is one of the main reasons the fediverse exists and and is structured the way it is.

There still are some concerns about trolls commenting on your posts, but that can be dealt with using the proper tools.

“The Net interprets censorship as damage and routes around it.” -- John Gilmore


This applies to the fediverse as well.

teilten dies erneut

Als Antwort auf Shiri Bailem

(1/2)

"If Bluesky starts pumping hardcore propaganda and silencing leftist voices... then the bridge offers a light, showing the abuse and giving them a way out that doesn't involve starting over from scratch."

How so? I have not read that you can migrate you #BlueSky account to another #Fediverse platform, say, #friendica

However, for me the single biggest #exit barrier is, that I...

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

(2/2)

...would lose my over 40k posts again, and *a lot* of them are important to me, as I regularly reference back to older posts. Furthermore, convos/discussions, such as these, are of value and are also worth keeping for future reference. They'd be lost, too, by moving. AFAIC, there is only one #Fediverse platform that permits migrating posts, but only internally, too.
//

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett missed this earlier, but the way out isn't usually account migration, that's a very specific and non-standard function that Mastodon implemented (Mastodon has a bad habit of only half-implementing ActivityPub and then rolling out it's own features and forcing everyone else to comply with their non-standard nonsense... they're kinda the internet explorer of the fediverse)

The way out is because you can leave without severing connections. I'm not saying you won't have to re-add people... but that you still have the option to re-add people. If someone deletes their Twitter account... they lose access to everyone that's only on Twitter. If Bluesky is bridged (and no ifs ands or buts, open bridges will exist despite people's complaints) and they delete their Bluesky account... they'd still have access to those same people.

The whole reason Facebook sticks around and maintains enormous power is because so many people don't have the option to leave without making themselves second class citizens in their communities. (Literally the only reason I have a facebook account... if I could access them over fedi, I'd delete my account in a heartbeat)

teilten dies erneut

Als Antwort auf Shiri Bailem

Highly interesting.

I think this sentence is missing the alternative method to #AccountMigration:

"The way out is because you can leave without severing connections."

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett The alternative is making a new account and re-adding the same people.

I had to do that when I moved from Mastodon to Friendica.

teilten dies erneut

Als Antwort auf Shiri Bailem

I did this using a Tool migrating from the (now) #DeadBirdSite.

Still, not being able to migrate the convos is NOT an "alternative", but an *escape hatch*."

One example, that many will know:

Imagine, that you invented 1000's of hours uploading and curating pics and shorts on your #Instagram account.
For whatever reason, you cannot maintain your account. Starting a new one, you lose all your work (it's not just...

@jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

(2/2)

...just the pics, but the interaction with contacts.)

PS:
I know:
...there are tools for exporting (beside the point)
...many people here even autodelete there posts (utterly different use-case)
...it's better than on most corporate sites (yes, but still just "rudimentary" flexibility, at least on #Mastodon.)
...that #Firefish(?) (still?) supports own-post migration (but that was no choice when I joined)

//

teilten dies erneut

Als Antwort auf HistoPol (#HP)

Like I said before, all of that is non-standard functions that the vast majority of the fediverse doesn't even support.

I think you might be confusing ease and possibility. Few people even when moving instances within the fediverse are going to have that option (save for those moving between two instances of the same platform).

It's not whether there's some convenient tool to move your posts or other data.

It's about whether after the move you can still get the same updates and talk to the same people.

Think of it in terms of the oldest surviving federated network: changing email accounts.

Before SMTP (the federated email protocol), you had to have accounts on every server with people you wanted to talk to. After you only had to have one account, but could readily move about the network to other servers if you got fed up with your server's bullshit or another offered better services.

(And for the record, public bridges with no opt-out methods exist for email as well)

@HistoPol @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart @Ryan Barrett

teilten dies erneut

Als Antwort auf Shiri Bailem

I didn't knew this thing that you can't migrate your follower from mastodon to friendica 😐

From mastodon to pleroma (and i think also misskey) it works.

cc @informapirata

teilten dies erneut

Als Antwort auf Luca Sironi

@Luca Sironi @informapirata :privacypride: Some platforms have specifically gone out of their way to support Mastodon's non-standard functions... that doesn't make them standard or a platform as deficient for not supporting them.

A lot of that has to do with the relationship between them, where many of those are newer platforms inspired by and emulating Mastodon. Friendica on the other hand is one of the old school platforms that looooong predates Mastodon, so supporting any of their non-standard stuff is a monumental task (it's easy to support something when you're starting from scratch)

teilten dies erneut

Als Antwort auf Luca Sironi

I understand your difficulties, but always remember that Friendica is compatible with ActivityPub BUT it works with a different protocol and its profiles are particular objects that contain a kind of unique key

@shiri

Als Antwort auf informapirata :privacypride:

@informapirata :privacypride: @Luca Sironi it used to work with a different protocol, Friendica has been ActivityPub based longer than Mastodon has been alive.

Always remember that Mastodon is well established to be a poor neighbor in the AP community, not supporting the full spec and often implementing their own non-standard solutions.

teilten dies erneut

Als Antwort auf Shiri Bailem

@activitypubblueskybridge @fedidevs @fediversenews

Well, migrating followers (just followers) should really be a standard feature of ActivityPub then.
One that must be implemented by all the supposed AP compatible projects

Nobody is gonna buy the theoretical reach of all the same people, like real freedom to change fediverse provider.

cc @evan

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf Luca Sironi

In reality, when it comes to migrations, Friendica does much more than any other ActivityPub-compatible platform, such as importing all the messages and contents of the old profile...
Friendica cannot be responsible for Mastodon's flaws 🤷🏽‍♂️

@evan @shiri @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf Shiri Bailem

I'm actually pretty sure Friendica put up Activitypub a few months later than mastodon, but otherwise I agree with what you say.

@luca

teilten dies erneut

Als Antwort auf Shiri Bailem

From reading some of the other posts and his answer to my earlier post, it seems he is accepting AP blocks in the software. So, both the tag and a block (domain or user) should work the same way.

teilten dies erneut

Als Antwort auf HistoPol (#HP)

Based on Ryan's response and some of the other descriptions, it sounds like the bridge software knows how to handle AP block requests. So, they should be the same.

teilten dies erneut

Als Antwort auf Hartmut Neubauer

(1/2)
I guess I can answer this question now: once s.o. quotes or boosts your content (= new post) you lose control of your content and cannot prevent it from being shared.

I'd say, unless you limited the post to your followers, however if one of your followers were on the #Friendica or #Hubzilla platform, they'd still be able to quote your post and then you'd still lose control,...

@jamie @chronohart @luca @PCOWandre @activitypubblueskybridge @fedidevs @fediversenews @snarfed

teilten dies erneut

Als Antwort auf HistoPol (#HP)

(2/2)

...correct @shiri? (I hope I have understood everything correctly that all of you had such great patience to explain to me today.
//

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol

I'd say, unless you limited the post to your followers, however if one of your followers were on the #Friendica or #Hubzilla platform, they'd still be able to quote your post and then you'd still lose control,...


Not exactly accurate. Anyone can copy and paste your words into the post box and quote you. Some platforms make it easier than others though.

Also, Mastodon is rumored to be including quote posts soon, so even on Mastodon, people will be able to quote you.

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf Scott M. Stolz

Copy and paste is possible, anywhere, always, yes.

Difference: copy & paste will not leave a trail to your original post, a link will.

#Mastodon was supposed to have quote posts last summer. Then @Gargron sent a lengthy explanation that resources had to be recomitted to fix backend features. Since, I haven't heard anyhting new regarding this, but I have not searched for it either.

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@HistoPol

Copy and paste is possible, anywhere, always, yes.

Difference: copy & paste will not leave a trail to your original post, a link will.


Actually, it can. I can manually type your handle and what you said and it will reference you. Just mentioning someone's handle such as @HistoPol@mastodon.social references them (i.e. @HistoPol)

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf HistoPol (#HP)

@shiri
Of course, you are right regarding the issue of boosting content. So I would like to intervene a little bit earlier.
If, e.g., Babsi on Bluesky follows Mary on Mastodon, Mary already has given her consent to interact with BS via the Bridge. But now Freddie, another fediverse user who has NOT given this consent, answers to Mary's post. Question: Can Babsi read Freddie's comments?
->

teilten dies erneut

Als Antwort auf Hartmut Neubauer

Proposal 1:
Yes, but the "like", "share" and "answer" buttons are hidden or disabled for Babsi; furthermore Freddie's fediverse address ("@freddiemiller@friendica.xyz") is hidden so that it is not easy for Babsi to mention him. Perhaps it is even possible to prevent textwise selection and copying. But even if copy & paste would be possible, as @HistoPol mentioned, no trail would be left. ->

teilten dies erneut

Als Antwort auf Hartmut Neubauer

2nd possibility: to hide Freddie's posts to Babsi. Okay, in this case not the whole discussion would be visible. But this might be done if Freddie has actively contradicted to the Bridge.
3rd: to display and allow all. But this might be difficult and a contradiction to that what Freddie has agreed to.

teilten dies erneut

Als Antwort auf Hartmut Neubauer

Maybe that there is still something to do for the development. For example, if Mary answers to a couple of users (and usually you see all their fediverse names in the head of the message), Babsi sees a copy of this message with only the @ names of the Bluesky users and those Fediverse users who have agreed to the Bridge, but without those who have not.

teilten dies erneut

Als Antwort auf Jamie Booth

If you are an ActivityPub user that wishes to connect with bsky, you will likely find information about this bridge, assuming it isn't an immediate failure, as soon as you search the web for a method to connect ActivityPub to bsky.

@luca @PCOWandre @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf chronohart

What about if the person reaching out is from BS? If my friend on the AP side hasn't found this bridge and opted in, they won't show up when I try to add them. A lot has to go right for these people to reconnect if they have to opt in. In my case, all I have are remembered Twitter handles that I'll try to search across the bridge fir that handle. If I get results, I'll try to follow.

teilten dies erneut

Als Antwort auf Jamie Booth

What about people that came to ActivityPub specifically because people that were harassing them are not here? This bridge makes it just that much easier for abusers to find their victims again because all they have to do is try a remembered Twitter handle to see if they get a hit through the bridge.

Do you disagree that this sort of abuse can happen?

@luca @PCOWandre @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf chronohart

No, but they could also create an AP account and harass the person. This bridge doesn't make that any more or less likely. You still have the same tools to block a user even if they are over the bridge.

I think there are a lot of positives to connect people who landed on different platforms. The possibility of harassment is really a more global Internet problem not AP/BS/Threads specific.

teilten dies erneut

Als Antwort auf Jamie Booth

You're confusing "possible" with "likely". Yes, it is absolutely *possible* for an abuser to join AP in order to find their victim, but it's less *likely* because that is an additional barrier.

On the other hand, if the abuser joins BS because they prefer that network and the only way to find their victim is to join AP, that will be enough of a barrier for many abusers to give up, making it less *likely* for the abuse to happen.

I agree that there are a lot of positives to connecting folks across networks *when they actively want to do so*, but it shouldn't be foised on people that already actively chose to join AP *instead* of BS.

@luca @PCOWandre @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf chronohart

I don't believe the choice of network matters that much. I think the harasser is more likely to go that extra step. If not, then a simple AP block solves that problem and that's a minor cost to enable better communication between people.

If this conversation around Bridgy Fed proves anything it's that we need more, less hostile communication between people.

teilten dies erneut

Als Antwort auf Jamie Booth

@activitypubblueskybridge@venera.social @fedidevs @fediversenews if nobody opts into a shitty service, people won't use it!

teilten dies erneut

Als Antwort auf Jamie Booth

I would disagree. First, only a few people would use the bridge. But then the new connection would spread out like a seed - slowly, but spread. Then the number of bridge users will grow exponentially. That means, an opt-in (or at least no pure opt-out) would be a good option.
@chronohart @luca @PCOWandre @activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf Hartmut Neubauer

That takes a lot of time, and as someone in IT, most people take the defaults and are SHOCKED to learn some features exist. 😁

Having this behave like the rest of the fediverse accelerates the awareness and usefulness of the bridge.

You can more rapidly achieve the goal of allowing people to connect and converse. That is after all why the fediverse exists. The rest of this is semantics.

teilten dies erneut

Als Antwort auf Jamie Booth

@Jamie Booth @Luca Sironi @Andre @Hartmut Neubauer @chronohart Hell, I'm aware of a few bridges and don't use them and have never even seen traffic from them... There's a few that I'm wary about, but again... I've never even seen any of the traffic from them.

teilten dies erneut

Als Antwort auf Jamie Booth

Okay, this is the other side. On the other hand, one can admit that we discuss about a bridge to bluesky, but if, anywhere in the world, a server would join the fediverse spreading hatred, bad thoughts and dangerous algorithms, nobody would discuss.
Anyway. Before the new bridge service starts, I would strongly recommend to deal with European data protection laws for they are stronger in the EU than elsewhere.

teilten dies erneut

Als Antwort auf Hartmut Neubauer

I'm not a GDPR expert, but because the bridge isn't stateful (ie just forwards posts) I don't think you are going to apply any of the data directives. Worst case, you might have to do something for instances hosted in Europe. But whatever you do applies much more strongly to actual instance servers. Those are hosting data created by and about users.

teilten dies erneut

Als Antwort auf Ryan Barrett

"Moderate people, not code" fails to learn from the simple fact that technology is not, and has never been, neutral.

You have to do both.

Nice catchphrase, but completely meaningless.

teilten dies erneut

Als Antwort auf Ryan Barrett

Please excuse my tone, but: why the fuck isn't this opt-in instead of opt-out?

teilten dies erneut

Als Antwort auf Csepp 🌢

@Csepp 🌢 @Ryan Barrett because you're on a federated network. If you want opt-in you join a whitelist instance.

teilten dies erneut

Als Antwort auf Shiri Bailem

See my other replies, not going to repeat myself.

teilten dies erneut

Als Antwort auf Shiri Bailem

no. Our freedom of choice is not being respected here. This is bad and will explode. You cant force us against our will.

teilten dies erneut

Als Antwort auf F4GRX Sébastien

@F4GRX Sébastien @Ryan Barrett @Csepp 🌢 you just woefully misunderstand what you're working with then. This is a federated platform, the entire platform is opt-out by default.

Your freedom of choice on the fediverse is very simple: unless you're on a whitelist server (in which case it only federates with pre-approved instances and no one else), then you have consented to your posts being federated, you have made the choice to have your posts federated.

Federation doesn't mean "my posts will only be on activitypub", it means "my posts will be freely accessible to everyone".

Your response here makes it very clear that you have no familiarity with how the fediverse works, how bridges work, or even the history of the fediverse.

Everyone actually behind the development of the fediverse is keenly aware of bridges like this and accepts them as a natural part of the fediverse. The original developers of the fediverse see them as a blessing to the fediverse.

Your complaints about consent and being "forced against our will" are akin to the people who go to a waterpark and complain about not consenting to getting wet... by being here you have consented to this. It's not anyone else's fault that you joined a federated platform with no understanding of what federation means.

teilten dies erneut

Als Antwort auf Ryan Barrett

@Gargron can we opt out of this bridge on mastodon.online please? Thanks.

teilten dies erneut

Als Antwort auf Allen

I sent a message to snarfed telling him what I thought of his outrageous "opt-out" option ...what a way to pad the numbers count for bluesky!
Who would want to deal with an organization that has the audacity to pull this stunt!

teilten dies erneut

Als Antwort auf Snowshadow

Agree! Though for me, part of the appeal of being in an open world (Fediverse) is not having someone sign me up for something I didn’t ask for. It’s a simple as that.

teilten dies erneut

Als Antwort auf Allen

That is my point. That is why I am outraged. I am still swearing every time I think about it. Unbelievable the nerve!!
The Arrogance!!

teilten dies erneut

Als Antwort auf Snowshadow

@Snowshadow @Allen you are not being signed up for anything with this, it's just another instance translating between the two protocols and all normal tools still apply.

The arrogance is thinking you can make public posts on a federate platform and dictate how they federate.

I'll also note that this isn't a corporate person doing this, it's a private individual. Bluesky has promised to federate under it's own protocol since it's beginning, once it does so you will see many instances on the bluesky protocol much the same as we're talking on the activitypub protocol, this bridge just connects the two protocols and a lot of people are interested in implementing such tools because that's the whole point of federation.

teilten dies erneut

Als Antwort auf Shiri Bailem

Am I understanding correctly that you think it’s arrogant to simply ask an instance moderator a question, while not threatening to burn the village down?

It’s cool that people are interested. Where there’s one side, there’s another. The point we’re trying to make is this should be OptIn BECAUSE it’s created by a private entity, that’s all. It’s not an outrageous take.

teilten dies erneut

Als Antwort auf Allen

@Allen

The point we’re trying to make is this should be OptIn BECAUSE it’s created by a private entity, that’s all. It’s not an outrageous take.


Out of the over 46,000 independently operated servers on the fediverse, how many are run by private entities? I don't know but I am guessing that it is more than 1.

At least with Bluesky and Threads, it is easy to block. But I am guessing that it would be nearly impossible to figure out which of the 46,000 ActivityPub-enabled servers are commercial and which are not.

And Threads will be connecting to ActivityPub natively. And so will WordPress. Both will bring in millions of users.

I respect people's choice to block whomever they want, but the ActivityPub part of the fediverse already has commercial servers in it. Bluesky would just be one more, which you are free to block.

teilten dies erneut

Als Antwort auf Allen

Mastodon federates by default to all new instances. Bluesky Bridge is only a new instance.

Your problem is with Mastodon, not with this bridge.

teilten dies erneut

Als Antwort auf Proxima Centauri

Which is why I asked @Gargron to opt out.

And, being ok with seeing several problems in one scenario, I also don’t like being opted into something I didn’t ask for.

teilten dies erneut

Als Antwort auf Allen

You can also block all bridged bluesky instances. This bridge is a big chance for the fediverse to gain more relevancy. You can go to an instance not federating with them, but you shouldn’t expect @Gargron’s mainstream instances to do so.

teilten dies erneut

Als Antwort auf user8e8f87e

I completely agree… And that would be the next step. I would simply spin up my own instance. But as a resident of this instant, I see no harm in asking.

teilten dies erneut

Als Antwort auf user8e8f87e

I have yet to find someone explain to me the difference between the proposed #bluesky bridge and someone following me from a Hubzilla instance.
While my instinctive reaction was “leave us alone” I didn’t find a definition for “us” and I don’t think that the angry people have.
My conclusion is that the bridge is *exactly* what the rest of the #fedi is. All the drama is stupid.
Shun it for size or lack of moderation, not for existing.

teilten dies erneut

Als Antwort auf chris@strafpla.net

@fediversenews Isn’t this an example of the Fediverse working exactly as designed? Anybody who really objects to it can just block it. I don’t understand why they’re trying to get the rest of us to do it too – it’s their decision, but it’s not necessarily mine or anyone else’s

teilten dies erneut

Als Antwort auf dogzilla

Yes. Implement the AP protocol and you are part of it; then anybody can decide to block you. That’s how it works. I really hope @snarfed will just implement it.

(Nice profile picture btw! 🖤❤️)

teilten dies erneut

Als Antwort auf user8e8f87e

@user8e8f87e @Ryan Barrett @Eugen Rochko @Proxima Centauri @chris@strafpla.net @Allen @Snowshadow @dogzilla you missed the point of what a bridge is if you're saying you hope they implement it... A bridge isn't some web scraper, it's a translator between protocols. It speaks the AP protocol and one side and the AT protocol on the other.

teilten dies erneut

Als Antwort auf Shiri Bailem

I had messaged @snarfed.org to ask about opting out and Ryan couldn’t have been any more respectful. He’s also looking at a way to make it opt in (github.com/snarfed/bridgy-fed/…)

I apologized for being part of the heat and look forward to supporting Ryan’s work when possible.

teilten dies erneut

Als Antwort auf Allen

man, that issue is one hell of a dumpster fire!

teilten dies erneut

Als Antwort auf Macumba Macaca

It is indeed, but that’s what happens when passionate people collide in a new-ish environment. We’re all trying to find a way to get what we want, and hopefully fair compromises can be had for any of these challenges.

Wishing you a beautiful day!

teilten dies erneut

Als Antwort auf Proxima Centauri

Maybe...
What irritates me is that I left social media for quite a period of time b/c I was fed up with the nonsense going on in corp. owned social media platforms. So I found out about fediverse and now threads is here and bluesky.
That's fine...I just don't want to see any of it or interact with those instances and I have blocked them...I don't want that toxic element in my TL.

teilten dies erneut

Als Antwort auf Ryan Barrett

I'll just respond to say, thanks for letting me know. I hope things go well, and I like the option to connect withore people.
@activitypubblueskybridge @fedidevs @fediversenews

teilten dies erneut

Als Antwort auf Ryan Barrett

I trust that you will change OptOut to OptIn before your bridge goes online.

Just to make sure, I hereby prohibit the bridging of any information from this instance to BlueSky.

Furthermore, what are your plans for posts with more than 300 characters? I hope that you are not planning to forward incomplete posts to Bluesky, possibly destroying their meaning.

#nobridge

teilten dies erneut

Als Antwort auf zeitverschreib [mastodon]

@zeitverschreib [mastodon] @Ryan Barrett (a) the hashtag goes in your bio (b) that's not going to change, they're being nice, the norm is that bridges don't ask and the only way to have a say at all is to just block the bridge... which you can always do.

If you feel like your content needs to be opt-in to distribute, you should set all your posts private (bridge will only see them if you accept a follow request from a Bluesky user on the bridge), or you should move to a whitelist server (where your posts will only federate to explicitly approved servers)

teilten dies erneut

Als Antwort auf Ryan Barrett

I have no interest of connecting into Bluesky, and I'm offended by your assumption that me, and most people, would be interested (opt-out instead of opt-in).

I call for #fediblock of bsky.brid.gy, and I'm blocking you. Thank you for listening.

teilten dies erneut

Als Antwort auf Joana de Castro Arnaud

@Joana de Castro Arnaud @Ryan Barrett it basically is opt in because someone on one side or the other will have to request the content, either one of your users requests a bluesky account or a bluesky user requests your account.

And the assumption is perfectly reasonable given that it's essentially just another instance, as if Bluesky spun up an activitypub endpoint themselves. The opt-out is at least a nice gesture (though unnecessary because blocking a server is an opt out regardless).

teilten dies erneut

Als Antwort auf Ryan Barrett

A few more questions, if you don't mind:

1. Where does the bridge pass messages on the Bluesky side? Directly to other PDS? Through the Relay? Does it function as a PDS?

2. What ATproto services is it using to pull posts back to the fediverse side? An App View? A feed generator? A labeller?

3. Is the choice of those services set by the PDS, or will they be customizable from the fediverse side on a per-account basis?

teilten dies erneut

Als Antwort auf Ryan Barrett

Hey @seahorse , are we safe from people like this and their piss poor ideas?
#nobridge #idontconsent #fuckinvasivetechbros
Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf seahorse

@seahorse @Formally Known As Bending Unit @Ryan Barrett pro-active statement that doesn't even knowledge of your network: bridges like this are passive, they appear and operate just the same as regular AP instances, only difference is that they're translating the requests on the other end to Bluesky and vice versa.

It's not live yet because it won't function until Bluesky federates, once they do it'll appear as a completely separate Bluesky instance in their network.

Bridges already exist for other networks as well, the only reason this is new is because Bluesky hasn't federated at all before.

As far as how to deal with it, if you don't want to see Bluesky accounts you can block the domain from your user account, or if an admin feels it's unacceptable they can block the domain server-wide. Both just like you can with a regular AP instance.

teilten dies erneut

Als Antwort auf Shiri Bailem

My admin took care of it.

I do not consider a bridge to bluesky or anything owned by (edit: sorry, affiliated with) a scumbag like dorsey to be "passive." I consider it to be the first step to #enshittification.

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf Formally Known As Bending Unit

@Formally Known As Bending Unit @Ryan Barrett @seahorse passive is a technical, not emotional term. Alternatively an "active" bridge would be akin to a webcrawler, actively pulling in posts whether or not they're requested.

That is also a wild misuse of enshittification. Enshittification is when a platform or product offers an explicit feature and upon achieving market dominance removes that feature.

This is simply someone using the existing features and design of ActivityPub in a way you dislike. This is not being provided by any of the platforms involved and is not something added or changed about the ActivityPub protocol.

This is as much enshittification as complaining about platforms other than Mastodon using ActivityPub.

Dieser Beitrag wurde bearbeitet. (2 Monate her)

teilten dies erneut

Als Antwort auf Shiri Bailem

you wasted your time defining passive and active, I could not care any less.

The definition I understand for enshittification is: "the pattern of decreasing quality of online platforms that act as two-sided markets."

Using a little knowledge and just a little bit of basic reasoning, I expect bluesky to only decrease the quality (as in, enshittify) of the mastodon experience.

More words more words more words

teilten dies erneut

Als Antwort auf Formally Known As Bending Unit

@Formally Known As Bending Unit @Ryan Barrett I'm just calling out people for being assholes because OP is getting shit on for spending the extra effort to offer a respectful feature...

Thread is full of assholes who think it's impossible and unreasonable to just block an instance and that somehow it's a deep violation of the principles of the fediverse for it to federate, let alone federate by default.

"How dare bridges, a thing that's been around for every single federated platform throughout history, offer an opt-out function, a feature that few if any other bridges offer as the norm is for them to just connect and not care"

And again on the topic of enshittification... you share the whole definition but clearly only read half of it because you don't understand what a two-sided market is... and how this is not a two sided market...

To clarify: a two-sided market is a business with two different sides to it, in most cases with enshittification we're talking about users and advertisers, but it can also be something like a credit card company (cardholders and merchants). Enshittification does not happen between platforms, it happens within a platform that's acting as a two-sided market.

ActivityPub is not a market at all, the vast majority of AP instances are not two-sided markets (I haven't seen any as of yet, but I'm sure there's an ad driven one out there somewhere), the bridge is not a two-sided market, the only two-sided market in this conversation is Bluesky itself.

teilten dies erneut

Als Antwort auf Shiri Bailem

Oi, how about unwelcome assholes that feel the need to unwantedly splain things?

Hold this mute, since you don't take hints

teilten dies erneut

Als Antwort auf Ryan Barrett

The big fediverse house, it has a big door, why people have to enter from window ?
@ghazi
@nizarus

teilten dies erneut

Als Antwort auf tness16

@tness16 @Nizar Kerkeni 🇹🇳 نزار القرقني @Ghazi @Ryan Barrett this isn't a window, it's an adjoining door. It's letting us and them talk without having to first exit the house, walk around the building and re-enter a completely different house.

And to be clear, the fediverse is both, this bridge is the fediverse in action. What you mean is ActivityPub.

teilten dies erneut

Als Antwort auf Shiri Bailem

Shiri that’s the most apt analogy I’ve found so far! May I appropriate that? I find myself sometimes trying to explain fediverse concepts to outsiders.

I usually resort to the villages-of-many-small-unique-buildngs vs. one-single-monolithic-high-rise allegory.

teilten dies erneut

Als Antwort auf tness16

I'm a little bit torn regarding this issue. While it is good to be able to interact with new people who prefer Bluesky for whatever reason, some people don't want their posts shared outside of the fediverse.
Whatever we post here is publicly accessible to anyone anyways, so I don't think this is a completely bad idea.

teilten dies erneut

Als Antwort auf tness16

Assuming the big door in this context is to join an ActivityPub server, I know several people who came here when Twitter blew up and weren't warmly welcomed. Lots of people telling them they were doing it wrong, etc. So, they left and went to places like Threads or BlueSky. This is giving them a chance to be on their instance of choice (BlueSky) and still follow their friends who did stay on ActivityPub.

teilten dies erneut

Als Antwort auf Jamie Booth

I am not against the people of Threads or BlueSky my opinion is the management of relationships between these two very different worlds, a world of enormous capital based on profit thanks to advertisements and a free and voluntary world which seeks tranquility
1/2

teilten dies erneut

Als Antwort auf tness16

with this bridge the infiltrations of artificial intelligence will go unnoticed and will spread like a cancer. There are a lot of questions for example spammers who will enter through this bridge who can stop them? The list of questions is long.
2/2

teilten dies erneut

Als Antwort auf tness16

I think it's ok to question the management and assess the risks (as long as you don't do it in a vacuum...AI is/will be an issue on ActivityPub as well). But, I also would remind you that there are real people who just want to get along and interact with their friends who happen to be on ActivityPub. This bridge allows that.

teilten dies erneut

Als Antwort auf Jamie Booth

Let's assume that the intention is good, it's true, social relations are important, I agree. Will the bridge only allow humans to pass? or bots too?

teilten dies erneut

Als Antwort auf tness16

My guess is it won't have any way to know. But I don't know if BS has a bot tag like Mastodon.

I would also say not all bots are bad. You can have bots that report traffic or weather. Governments have bots for distributing information.

I feel like a lot of the responses to this have been reactions to the worst possible scenario. That rarely happens. Reality is somewhere in the middle.

teilten dies erneut

Als Antwort auf Jamie Booth

There is good and bad everywhere, I am like anyone who loves this fediverse world as it is with these current flaws, and the motivated people who each try to improve it on their own. I hope the bridge follows the same logic.

teilten dies erneut

Als Antwort auf Ryan Barrett

@Ryan Barrett @Ryan Barrett glad to see this already underway, sorry however to see the amount of hate you're getting from people who don't understand how the fediverse works... if they think this is bad, should I tell them about Mostr? lol

teilten dies erneut

Als Antwort auf Shiri Bailem

Hey Shari, most bridged services I've used are transparent about the bridge existing. I'm apart of a community that bridges IRC, Matrix, and Discord. This is instantly transpatent regardless of protocol or platform. This is usually how I've seen them work in social communities.

A lot of folks like this space because it's insular and allows them to attempt to control their reach, additionally the culture in many spaces here is heavily consent based.

teilten dies erneut

Als Antwort auf Bennett

Do you genuinely believe that the main reason folks do not like this is because they don't understand what a bridge is? Same question applies to Apub/Masto. I suspect it's because folks here want to be asked if XYZ is fine or not, not because of a technical misunderstanding. Generally moderators help ensure the culture of consent is followed.

I feel you misunderstand where the folks you're replying to are coming from.

Als Antwort auf Bennett

@Bennett @Ryan Barrett @Ryan Barrett oh no, I fully understand all those points. What people are upset about is that their illusions are being taken away.

For one, bridge transparency: IRC and Discord are non-federated, so they don't even have bridges in the same sense, their bridges are only what we would call puppet accounts. Matrix bridges really come in two forms, one is puppet accounts and the other are bridges in the same sense as above... a prime example is aria-net.org which is an XMPP/Matrix bridge. Like above, no consent, no nothing, it's there and just works. If I want to contact you on one platform from the other I just have to know how to reformat your name to use the bridge and voila, no "consent" needed and no "opt-in". (You'll note how you generally don't see an option somewhere in Matrix or XMPP to sign up for a bridge between the two services, because you only need to sign up for puppet accounts)

and second: people are freaking out because they had assumptions and illusions about what the fediverse is and this threatens those assumptions and illusions, despite being something that's been understood to be the accepted norm here loooooong before they ever even heard about it.

Bridges pre-date even ActivityPub, and the behavior of bridges is well established. Again, people freaking out about this are people who didn't realize that this is part and parcel of what it means to federate. And if you're goal is to control your data, then you need to be joining a whitelist server because otherwise this isn't the place for that.

Unbekannter Ursprungsbeitrag

Shiri Bailem
@Damon @Black Aziz Anansi :vm: I mean if they prefer opt-in they should look for or host a whitelist server... (many server platforms have a whitelist mode in which they only federate with explicitly whitelisted instances)

teilten dies erneut

Als Antwort auf Ryan Barrett

A question about your comment "Admins .... the domain to limit or block is bsky.brid.gy". Does this also work for individual users blocking the domain? If so, you might want to update your post to reflect that -- I've heard from several people that they don't think regular blocking will work with #BridgyFed
Als Antwort auf Jon

@Jon @Ryan Barrett @Ryan Barrett User level block controls vary based on platform (ie. Mastodon, Lemmy, Friendica, etc). Regardless they should work mostly the same as server level controls.

teilten dies erneut

Als Antwort auf Ryan Barrett

mother fucker what an awful and hateful idea to make opt out, you're a terrible person

teilten dies erneut

Als Antwort auf FS9-BS "Bad Survivor"

@FS9-BS "Bad Survivor" @Ryan Barrett what a hateful comment to make when they're doing more than any of the other bridges.

Let alone an ignorant comment to complain about how your publicly federated posts are passed around... sounds like you just need to join a whitelist server.

teilten dies erneut

Als Antwort auf Ryan Barrett

I know I'm feeding the dogpile, but you need to understand that a service like this must be opt-in. Most users on either platform will never know about this bridge, and are therefore unable to opt out. Bridge services must always be opt-in to ensure that users actually get a choice.

teilten dies erneut

Als Antwort auf Hazelnoot

@Hazelnoot @Ryan Barrett @Ryan Barrett what JP said, but also bridge services are open things. Opt-in really is more about your usage and server than the bridge.

For users who want a choice in how their posts are federated, I strongly recommend whitelist servers. Otherwise you've already opted in to the fediverse (and bridges are an important part of the fediverse) as a whole.

Als Antwort auf Shiri Bailem

Otherwise you've already opted in to the fediverse


That's exactly my point, though. I've opted into the fediverse, not BlueSky or Twitter or Nostr or anything else that's been bridged before.

Als Antwort auf Hazelnoot

@Hazelnoot @Ryan Barrett @Ryan Barrett Bluesky and Nostr are the fediverse (or rather, Bluesky will be once they choose to federate, which this bridge is just preparing for), it's not my fault you didn't know the difference.

One of the key elements of the fediverse is you don't get to control what platform others use to view and access your account. There's no "block firefish" or "block hubzilla" or "block mastodon". A bridge is just another extension of that and long before ActivityPub even existed bridges were already established as a major feature of federated networks (hell, I reference an XMMP-Matrix bridge in my bio, all of which predate Activity-Pub and that bridge can only be opted out of by blocking the server... like most bridges).

Basically, this is the way the system was always supposed to work, I'm sorry that you were mislead to think otherwise.

And I guarantee you W3C (the actual stewards of ActivityPub) were absolutely expecting bridges like this to show up immediately (bridges to diaspora* and OStatus would have been some of the first bridges on ActivityPub, again operating silently with no opt-in or opt-out mechanism).

teilten dies erneut

Als Antwort auf Shiri Bailem

respectfully, I still disagree. Those networks are entirely separate from the one that we're currently on (ActivityPub). The communities are different, the servers are different, the software is different, even the protocol is different. It's disingenuous to consider them all the same when there's literally no relation.

There's no "block firefish" or "block hubzilla" or "block mastodon".


Side note, but that actually does exist. I once encountered a Mastodon instance that has been patched to automatically suspend any instance running Pleroma. I also know someone who uses a script to detect and block Soapbox instances. Not saying I support that, of course, but it's definitely a thing that some people do here.

teilten dies erneut

Als Antwort auf Hazelnoot

@Hazelnoot @Ryan Barrett it's a false assumption to join a federated network and think you're joining an isolated space.

The people who are upset about this are honestly just people who have false assumptions about what a federated network is and what the fediverse is. If you joined explicitly only wanting to be accessible via ActivityPub native servers... then you were under a false assumption and it's not their fault you that your illusion is being broken.

They are all the same because they've always been the same. All federated networks bridge between eachother, just like above... only exception is this is the weird bridge that offers an opt-out other than blocking.

And as far as hacking a way to block by platform... those methods will also work for this too.

Als Antwort auf Ryan Barrett

I think a lot of people think that Mastodon is the fediverse, and then freak out when they find out that it is actually connected to all of these other things too. I am guessing no one told them what federation is and how it works.

teilten dies erneut

Als Antwort auf Scott M. Stolz

This was my feeling when the Threads freakout happened last summer and it has been confirmed since yesterday.

A lot of Mastodon users don't understand the first thing about the Fediverse and federation.

And it's concerning when some of those people are Mastodon admins.

#Mastodon#Fediverse#Federation#Consent#Privacy#BlueSky#Threads

teilten dies erneut

Als Antwort auf Ryan Barrett

@javido ¿ Nosotros aquí en tiflo como quedamos con esto?

teilten dies erneut

Als Antwort auf Nora🇲🇽

(Disculpe, estoy aprendiendo español!) ¿Quieres "bridge" a Bluesky con tecnologías de asistencia para invidentes?

(Excuse me, I’m learning Spanish!) you want to “bridge” with Bluesky with assistive technologies for the blind?

teilten dies erneut

Als Antwort auf Ryan Barrett

You have this totally the wrong way round and are not respecting user privacy. If you're making big changes like this the default should be opted out, not opted in with a choice to opt out.
Don't be a dick like Facebook et.al do the right thing from the start.

Also we Europeans have stronger data protection laws and I suspect you're breaking them.

#respectuserprivacy
#GDPR

teilten dies erneut

Als Antwort auf Greg Walker :manjaro:

@Greg Walker :manjaro: @Ryan Barrett they're already doing the right thing from the start and exceeding expectations, offering any such feature is totally abnormal for a bridge.

Maybe you should consider whether you're doing the right thing by coming into the fediverse with assumptions that bridges should be opt-in when in the community they've always been automatic, opting out purely by blocking.

And in regards to the GDPR (A) nobody outside of a GDPR country cares (B) GDPR applies as much to bridges as it does to other instances, if it's illegal for the bridge to operate then it's also going to be illegal for multiple core AP functions to operate as well.

teilten dies erneut

Als Antwort auf Ryan Barrett

I just came here to say that I support your work and I'm totally for building a bridge. The web should be free and so should the information in it.

teilten dies erneut

Als Antwort auf Ryan Barrett

You may want to check compliance with GDPR before doing this.
@aeris you may be interested in this.

teilten dies erneut

Als Antwort auf Robur

@Robur @aeris @Ryan Barrett you only need to check compliance if you're in a GDPR country (they are not), and GDPR's stance on this will be the exact same as on federation in general (as such if this is illegal than the entire fediverse is illegal to begin with)

teilten dies erneut

Als Antwort auf Ryan Barrett

I'm undecided about Bluesky, but I was undecided about Threads. My thing with Threads was, "I'm a single person instance (now a 2 person instance briefly a 3 person instance) so the damage done while I'm not around is minimal". Bluesky seems to be *trying* to be not a problem, but I'm not sure they will prove to be not a problem. Thanks for your work.

teilten dies erneut

Als Antwort auf Ryan Barrett

I’m looking forward to following #Bluesky accounts here. It seems like the other side has lots of knobs for twiddling opaque algorithms and all follows, but precious few for moderating what I see from the individual “knobs” I follow there.

teilten dies erneut

Als Antwort auf Ryan Barrett

This sounds great. Can't wait to follow #Bluesky accounts. Please go on with your original opt-out plan and don't listen to the sad haters on #Mastodon.

teilten dies erneut

Als Antwort auf F4GRX Sébastien

@F4GRX Sébastien @Ryan Barrett congratulations, you don't have to have anything to do with Bluesky. But bridges are a normal part of federation, if this feels threatening I strongly recommend you read up on how ActivityPub (the protocol used by Mastodon) works, how bridges work, and the history of bridges in the fediverse.

Odds are you'll never see any personal impact from this whatsoever unless you make friends with someone who's on Bluesky or share something that goes super viral (in which case you'll probably be thankful for this because you have zero control over screenshots, but through the bridge you'll still have access to blocking, deleting, and editing of posts)

teilten dies erneut

Als Antwort auf soc

@soc @Ryan Barrett I recommend then either blocking the bridge or selecting one of the options they provide to opt-out. Their # nobridge tag is thorough because it'll also opt you out of other bridges running their software, but if you don't like that you can just block their bridge's instance.

Be aware though that if you're on the fediverse and not on a whitelist instance, you will be bridged to all reasonably compatible federated networks.

teilten dies erneut

Diese Webseite verwendet Cookies zur Erkennung von wiederkehrenden Besuchern und eingeloggten Nutzern. Durch die weitere Benutzung der Webseite akzeptierst du die Verwendung der Cookies.