Open Source Adventurer
Support me at https://patak.cat/sponsors
Project Steward @npmx.dev
Core @vite.dev @vitest.dev https://elk.zone
Director @stewardshiplab.org
Advisor @e18e.dev
patak
that’s pretty nifty
We're looking for ideas on how verification should work for open source communities 👋
one of the things i sneaked in while working on mu.social is a first version of a custom embed for events that allows you to directly rsvp
by this, I mean:
I've been using a cms for a long time to store things like:
⚪ #ama questions people ask
⚪ talks I'm planning to give (or have given!)
⚪ my current location (which I track and expose publicly 👀)
...and so on
👉 but atproto means your pds = your data
so … why not use it as a cms?
I'm finally verified! And with extra lore, as the verifier is @npmx.dev! Thanks for the trust towards npmx, Eurosky. Y'all aren't playing around this week: a new did:plc directory mirror, a relay, and an app, running on European infra. Cheers to mu.social future 🩷
We've started by verifying npmx maintainers. Log in to mu.social to see the verified badges! We'd like to discuss the best strategy for our communities with OSS maintainers. Should all large enough OSS projects be verifiers? Or would it be better for a few orgs/foundations to take on the task?
don't forget that there are droves of folks that care and are building towards a better future for everyone, but our comms tools are constantly bombarding us with the worse of humanity instead of celebrating them
When you're up against network effects, there comes a time when it isn't worth staying and trying to get others to move. It's better to leave. And focus on building, on new network effects.
