Tech leaders ready launch of Canadian social-media platform Gander to buck U.S. dominance
#madeincanada #canada #socialmedia #datasovereignty #atprotocol #startup #startups #decentralized

"Yeah, if I had a bet on one, actually, you know what I’d bet on is the #MatrixProtocol, the dark horse in the corner." @photomatt from @automattic and @wordpress in @voxmedia. #ActivityPub #ATProtocol

https://www.theverge.com/decoder-podcast-with-nilay-patel/693052/automattic-ceo-matt-mullenweg-wordpress-drama-wp-engine-open-source

Just dropped a new article on the VEX.blue BETA site: Connect your Bluesky account to the Fediverse

Want your Bsky posts to show up on Mastodon? Or your Mastodon account to be visible on Bsky?

This guide walks you through using bsky.brid.gy and ap.brid.gy so your posts & profile can talk to others across platforms.

Reply via your timeline
https://new.vex.blue/articles/2024/09/06/bsky-fedi

I hope someone can answer this question. @snarfed.org@fed.brid.gy maybe?

I find #Bounce pretty exciting but I'm unsure of something.

If I move an ActivityPub account from one platform/server to a new one, I can't use the old account anymore.

Is it the same with Bounce? If I move my social graph from Bluesky to ActivityPub, does my Bluesky account "shuts down" or can I still use it afterward?

I know, Bounce is not out yet, so maybe I'm getting ahead of myself, but I was wondering.

#BridgyFed #Fediverse #ActivityPub #ATProtocol

Just learnt of Bounce. May be a good tool to be aware of for those using #bluesky or the #ATProtocol

https://blog.anew.social/bounce-a-cross-protocol-migration-tool/

It's so disappointing that #Bluesky decided to make a brand new protocol instead of going with the established standard - #ActivityPub. I hope they at least make #ATProtocol interoperable with the #fediverse in the future.

@mmasnick.bsky.social The only X that went anywhere was MIT's Athena project (started in 1986) and even that is dying.

Elon Musk's legacy I think is permanent now… unless #Twitter pull a rabbit out of a hat (e.g. #ActivityPub or #ATProtocol integration), it'll fade into irrelevance very soon.

The problem with #Bluesky is they came to be during a time when decentralization was en vogue, so they decided to just be that.

But, it's marketing.

Ten, fifteen years ago Bluesky would've branded itself as "modular" or having a robust API like App dot Net.

They want to be the internet's common infrastructure. Of course they do. What for-profit company wouldn't want that?

I maintain that #ATProtocol is interesting. But it's not a noble pursuit.

Anyway, I deleted my BS account.

At SXSW's Fediverse House, it didn't matter which platform or protocol you preferred — everyone was focused on the singular goal of building a better internet. We've uploaded videos and highlights of key conversations from the event and rounded them up in one post. Here you go:

https://about.flipboard.com/fediverse/fediverse-house-2025-roundup/

If you use Bluesky, you may be interested in today’s news that now you can publish Surf feeds to Bluesky.

We’d love for you to test with us if you want! Here's more details:

https://bsky.app/profile/surf.social/post/3lnnpyqge5c2p

In this episode of the DotSocial podcast, recorded at the #FediverseHouse at SXSW, Bluesky CTO @pfrazee.com strapped on his butterfly wings to explain to @mike how the company is rethinking the internet’s architecture to create a more flexible, user-centric web.

https://about.flipboard.com/fediverse/dot-social-paul-frazee-bluesky/

If you're at #IJF25 next week, I'd love to say hi!

Particularly excited to chat about:

- Building a high-functioning technology culture
- #opensource for newsrooms
- Maintaining source anonymity
- The #fediverse / #atprotocol
- Collab with open source projects

But also, I'd love to hang out!

One of a number of take-aways from #ATmosphereConf —

The Bluesky team had a whole session (IndieSky) set up so that others could set up their own parallel Bluesky infrastructure.

The Bluesky team even wanted to make it less expensive for people to do it.

BUT — most the people in the room didn't seem interested in that per se.

Most the people in the room wanted their own ATProto infrastructure for their own applications / platforms built on ATProto.

I was looking into how a Bluesky PDS works from a programming point-of-view.

I came across this document the first time I looked around. (And then someone shared it with me again.)

https://github.com/bluesky-social/atproto/discussions/2350

It gives you an overview, but not a list of API (NSID) end-points to implement.

The only resource I could find for that is this:

https://github.com/blacksky-algorithms/rsky/tree/main/rsky-pds%2Fsrc%2Fapis

(You can infer it from the directory names and file names.)

One of a number of take-aways from #ATmosphereConf —

I felt like Paul Frazee (from Bluesky Org) was encouraging people deploy their own relays.

And, to think of the Bluesky Firehose Relay of everything — as a temporary thing to use, when first developing your app or platform. And then later, to deploy your own relay.

One of a number of take-aways from #ATmosphereConf —

Although there is only one Bluesky Firehose Relay of everything —

There are definitely other relays on the Bluesky ATmosphere.

I talked to more than one person who has their own relay on the Bluesky ATmosphere.

...

Although none of these alt-relays seemed to be meant to be broadly used by others. But, instead meant to be used for the platform they created using ATProto.