Should @pixelfed explore adding native support for Bluesky/AtProto?
Feedback wanted!
Should @pixelfed explore adding native support for Bluesky/AtProto?
Feedback wanted!
@dansup @pixelfed Is it where we are all going? If so, yes, or Federate with Open Vibe and take their lead?
@dansup @pixelfed some things I would like to be addressed before this:
—auto night/day mode
—interaction counters auto-refresh on realtime
—bring back carousel option for timeline pictures
—zoom on pictures
—fix notifications (99% of time are not working, at least for me)
—notification badge on notification icon when new notifications are pending
—double tap option to like a photo
:-)
@dansup @pixelfed YES! there should be an option, but I'm tired of people being pissy about this! Threads and Tumblr are far worse. Fediverse won't grow, if they keep up with this damn elitist attitude!
@dansup @pixelfed Having a bridge between two protocols sounds good, we need less wall gardens for a true decentralized internet.
@dansup @pixelfed for photos sure. The fear is that the pressure will be to nudge ever closer to instagram+threads intermingling. Personally I kind of like having multiple separate social feeds.
@dansup @pixelfed Seriously f*ch all these VC-funded social media plays. That’s exactly what we are all escaping, isn’t it? No to Bluesky. No to Threads. Just NO.
If every app bends over backwards to support Bluesky, what’s their incentive to federate? Which they probably will never do anyway.
I read that implementing AtProto would be super expensive and currently Bluesky holds the monopoly on being an app on AtProto.
@dansup @pixelfed I don't know.
If someone asked that question about Mastodon, or even better - ActivityPub in general - I would definitely say yes.
Probably, even Mastodon should not do it by itself, it should be integrated somewhere on the level of the protocol, and not the platform itself.
@dansup no, do 1 thing and do 1 thing good 😅 also bridges exist for those who really want to, right @pixelfed
@dansup @pixelfed I think it's a bad idea, you could implement the bridge negatively to make is easier for Pixelfed users to discover it and opt in but I am against native Bluesky support in general. Their protocol gives them full control rather than allowing for actually decentralization and we shouldn't embrace that!
@dansup I've seen conceptual talk of combined ActivityPub servers and AT PDSes. For decentralization, that certainly makes more sense than routing everything through a single bridge. The idea seems worth exploring.
It does have lots of caveats though: posts published to Bluesky cannot be edited and are always fully public, the data model (e.g. 300 chars max) is strict, and there may still be restrictions on the number of accounts per PDS. So check your assumptions carefully.
@dansup @pixelfed No, Pixelfed should stay with Frdiverse. AtProto is the delusion of decentralized network; it’s just outsourced data center.
@dansup @pixelfed would make things unnecessarily complex, as bsky wont show apub posts anyway
@dansup @pixelfed No, BlueSky is a fucking plague, keep them as far away from us as is reasonably possible.
@dansup Yes!
@dansup Would also suggest getting Pixelfed/Loops accounts on Bluesky/Threads. Bluesky seemed to get loads of signups by having an account on Threads showing people what's available on Bluesky.
@dansup @pixelfed One vote for yes from me! Or if not, at least getting integration with @bsky.brid.gy to work in Pixelfed like it does with Mastodon.
@dansup @pixelfed Yes, I'm working on getting all of these feeds on one app as it is.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.