Recent searches
Search options
★ New blog post: The Bluesky hater's guide to using Bluesky (aka, how to use Bluesky without *actually* using Bluesky)
A real quick post inspired by a thing I wrote on Cohost.
https://beeps.website/blog/2024-09-18-the-bluesky-haters-guide-to-using-bluesky/
@batbeeps Sorry to ask this so long after the article has been written
This method has some serious caveats that I can't see myself looking past.
The fact that you have to use a second account on a mastodon client just. It kinda defeats the purpose of not making a bluesky account In the first place. If I'm going to have a second account that requires monitoring as well why not just make a bluesky account?
Why can't this cross posting tech also crosspost a bluesky feed to a bot or something that I could follow on fedi with this account?
NFC#844 @batbeeps@chitter.xyz@Lilium_Mortem The intent there is that if you’re already using a Mastodon client that supports multiple accounts, you don’t need to use an entirely new and separate client to use Bluesky.
There are tools that let you directly follow individual Bluesky accounts on the fediverse, but they—correctly—require individual consent. Every Bluesky user you might want to follow would have to separately sign up for a bridging service before you could follow them.
Cross posting a person’s posts to a different platform without their consent is almost certainly a violation of some terms of service somewhere (if not just ethically dubious).
Having it be a separate account/feed avoids that problem because to Bluesky it’s a Bluesky account following Bluesky’s users. All the bridging is happening between Bluesky and the client you’re using.