Goofed Home

@serapath This sounds great, even if a bit above my head! I'm not too sure how helpful I can be here, but perhaps you might have luck reaching out to Darius again?

He's pretty active on his Mastodon server, should be fairly easy to get in touch and get some useful pointers from him directly.

@_elena @lumiworx I for one am not one of those people. For me it's ActivityPub only.

@_elena @Gargron @lumiworx

I am also, but maybe in a different way.

As someone who helped create ActivityPub and works every day to promote its use, I absolutely believe that everyone should make and use ActivityPub-native software. At SWF, we only do ActivityPub projects.

But if someone chooses to build on ATProto, and to make their software and accounts bridgeable so we can stay connected, that's infinitely better than being cut off entirely.

@_elena @Gargron @lumiworx

I mentioned elsewhere that I think supporting the openness of the Atmosphere is important for whatever comes next there. Whether BlueSky thrive or don't survive, the more the ATproto stack is standardized and independent, the better it is for the Fediverse.

@slothrop@chaos.social @_elena@mastodon.social @lumiworx@mastodon.social Excellent way to put it for sure.

Centralization is easy. You control it all. It's not good for people that want innovation and choice.

Decentralization brings freedom, innovation, choice, but offers a lot of technical roadblocks.

I just want choice. I can choose what's best for my family. I don't need Tim Apple, or whoever to tell me what's good for us, while trapping us into a fish bowl and making us work for our food.

@mapto @funkylab

In the beginning we can't rely on companies, or recruiters to post jobs on a fediverse system. Most of them don't even know of it at all. So we'll use job scrapers. You will be able to set up a scraper for jobs you might be interested in, and other do similar. Then you see your, and their results, and vice versa.

The architecture does allow for recruiters, or companies to feed in their own job descriptions directly, but we can't start with only that.

1/2

@mapto @funkylab

I don'^t think, it would be reasonable to make that a paid feature, because I'm working on an open protocol. But actually I did think in a similar direction:

1. Have them pay for company-accounts on my installation of the system. They are free to set up their own instance, and others can also set up one, and sell accounts.
2. Help providers of their software to integrate with our architecture. If they use ProFed code directly, they have to accept the AGPL.

2/2

@mapto @funkylab

The talk about events on my website seems to be confusing. I have to change that. Those events are internal. I use an event sourced architecture, where in a simple installation all producers, and consumer of the event run in the same process. But it can be split e.g. to different Kubernetes pods for bigger installations as well.

I don't have any particularly specific plans on professional insights. My current idea is to rely on groups for that. Do you have any better ideas?

@mapto @funkylab

Thank you very much for your feedback. I'll answer them in each post to keep the context.

Those two are in the list already. I've extended Person with a CV, that is not the same, but adjacent to the h-resume microformat.

For jobs I plan to start with a scraper, that feeds a federated search engine, whose result is not immediate, but a feed. That way, I can avoid some of the complexities of federated search. But it is still not trivial.

@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.

@steve @trwnh @hongminhee @jasnell

@solarbranka yes, great idea!

@evan @hamishcampbell @_elena

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.

@julian@activitypub.space When I asked @reiver@mastodon.social last time, he said he’d make sure FediCon 2026 doesn’t overlap with COSCUP 2026, but I’m not sure how it’ll turn out.