@julian I already have access to the package.
@julian anyways, moved and shipped!
@steve @trwnh @hongminhee ha! That was the notice that got me to become a maintainer. But I don't have the admin rights to change it!
@jasnell can you give admin rights on the activitystrea.ms repo so I can change the message and also push automatically?
@evan James archived the repo today, assumably in response to this question. I'm going to keep working from my personal fork, and I'll use that to push to npm. I think I can update the info in package.json on the topic, too. A change that's been waiting too long.
@solarbranka yes, great idea!
Since they have $100M in the bank, 3 is probably a way off. AFACT, they are currently doing both 1 and 2 in parallel; if you look at their protocol engineers, I do believe they are really all in on 1, but much of the rest of the company is taking every opportunity to act in a decentralized manner and going in the opposite direction.
@ricci @hamishcampbell @_elena well, they had $100M when they raised money last year.
Crypto funds love to rollover crypto assets. So maybe some of it was in crypto, like Bitcoin, which has since dropped 25% against USD.
And they've been operating a tech startup with 20-30 staff and dozens of contractors, plus hosting costs which are somewhere in the $20-50M/year range, I'd bet.
If I had to guess on runway for BlueSky today, I'd say 12-24 months.
@solarbranka that's surprising; I don't think that should be possible. I'll test it more thoroughly and let you know.
@mastodonmigration @hamishcampbell @_elena I won't argue with this. Having two incompatible stacks hurts the entire ecosystem. When developers and decisionmakers see that, it makes them want to sit back and wait to see what comes out on top.
I think our best mitigation for that right now is reassurance that investing time, energy and money into ActivityPub will not be a waste.
💯 Slow and steady wins the race. It is just frustrating that people are so easily distracted by bright shiny objects.
@hamishcampbell @_elena the good part is that this is what we should do in the best case scenario, too. So, all worthwhile.
@hamishcampbell @_elena one other thing: bridging is really important for us all right now. It's how we can tell developers to implement ActivityPub and still get access to the BlueSky audience. I hope everyone works to support BridgyFed.
So, I think there are two important things people in the Fediverse movement can do to help with these possible outcomes.
The first is to keep building on ActivityPub. I love our protocol and our ecosystem, and I think it's a wonderful network. But it's also a necessary hedge against clawback or collapse.
@tom @julian @astro There are some small differences in following between a relay and a regular actor. But it's essentially correct.
https://codeberg.org/fediverse/fep/src/branch/main/fep/ae0c/fep-ae0c.md
This all brings in a firehose, which can be a lot of data to handle, especially if you're only interested in a few topics.
Fedibuzz has solved this really nicely, by having one relay per hashtag. So an admin can add a few hashtag relays for topics of interest to their users.