Quick bet: #BlueSky will grow dramatically over the next quarter.

And the #Fediverse will continue to grow at AT LEAST 800,000 to 1 million+ new users per month as well. No let up.

Dramatic new apps will launch supporting BlueSky AND cool new features launching in great apps for Mastodon.

A decentralized rising tide of awareness lifts all decentralized boats.

Meanwhile:
Twitter will lose Monthly Active users. So will mini-me closed source platforms (Spoutible, Tribal, etc)

Follow on bet for this next quarter:

At LEAST one, robust bridge will launch inter-connecting ActivityPub/Fediverse networks in a two-way connection with BlueSky ATProtocol networks.

Likely more than one.

@tchambers Bridges are the way.

@atomicpoet @tchambers

That's assuming BS is actually federating, which may not be the case (assuming @evalprime didn't mess with the code):

https://mastodon.social/@evalprime/110283861562722811

@oblomov @atomicpoet @tchambers

code for getProfile is here: https://github.com/bluesky-social/atproto/blob/main/packages/bsky/src/api/app/bsky/actor/getProfile.ts. line 8 means it requires auth.

it would maybe(?) be possible for a bridge without auth for viewing profiles/posts but you'd also need to change some frontend stuff.

atproto/getProfile.ts at main · bluesky-social/atproto

Social networking technology created by Bluesky. Contribute to bluesky-social/atproto development by creating an account on GitHub.

GitHub

@oblomov @atomicpoet @tchambers @evalprime wait but if it wouldn't federate, 400 is not the correct response. 400 usually means that something is wrong with the request, not that you don't have sufficient permissions or no access to something.

Or did I get something wrong here?

@farshidhakimy @oblomov @atomicpoet @tchambers

here bluesky is trying to get that did but it doesn't exist in the db. what it should do is look up the user in its pds but it doesn't

the response is some JSON, "Profile not found"

@oblomov @atomicpoet @tchambers @evalprime for example, it is possible that the ":" is not url-encoded and this is what causes this response.
(This could be completely wrong. I just think that this is not the correct status code for not allowing access to something)

@farshidhakimy @oblomov @atomicpoet @tchambers

it should still work regardless, dids work on bsky.elijahs.space just the same.

you can see on line 15 of https://github.com/bluesky-social/atproto/blob/main/packages/bsky/src/api/app/bsky/actor/getProfile.ts that that same string is returned because actorRes doesn't exist. it's looking at it in the db, not the internet. https://github.com/bluesky-social/atproto/blob/main/packages/bsky/src/services/actor/index.ts

atproto/getProfile.ts at main · bluesky-social/atproto

Social networking technology created by Bluesky. Contribute to bluesky-social/atproto development by creating an account on GitHub.

GitHub

@farshidhakimy @oblomov @atomicpoet @tchambers

so when I tried to get the profile on my instance it gave 400, but getting the same profile on bsky.social is a 401

@evalprime @oblomov @atomicpoet @tchambers sorry, I actually don't know much about the protocol blue sky uses.
This request should be possible with your credentials/no credentials for it to be able to federate?

@farshidhakimy @oblomov @atomicpoet @tchambers

yeah, app.bsky.actor.getProfile is how it should be able to get a profile. but it's limited to auth with a jwt token that you can only get on that pds (instance). in theory, without auth, the frontend could just pull from that pds' domain for the account, so I could see another pds' users. but there is auth, so essentially it's limited to just users on that pds, thus no federation

@evalprime @oblomov @atomicpoet @tchambers oh okay so no federation.
I hope this is just because they rushed it

@farshidhakimy @oblomov @atomicpoet @tchambers

same, but they claim it's federated and so do a whole bunch of news sources like The Verge and TIME

@evalprime @oblomov @atomicpoet @tchambers that's shady imho and lowers my trust towards them.
But I think that the journalists handled this bad as well. If you don't fact check before publishing I could just look in the press release myself and you have no reason to exist.
But this is nothing new in tech journalism 🤷.