Web standards are stable. Frameworks, especially frameworks centered in transpiled code, absolutely are not. Maintenance cost is much higher for worse performance and accessibility. Just facts.

Yeah, it’s built on a modern incarnation of b2g that supports PWA:s etc, created by @fabrice.capyloon.org and friends

The dream:

To one day have a Fairphone, Mudita Kompakt or similar with an OS like capyloon.org

No more native black boxes sold through walled gardens.

Instead an open future enabled by web technology.

Trump would be furious. But maybe the rest of us can prioritize our happiness over his?

And: Saving the environment quite a bit as well 👏

Which specs are these?

In general I would love for specs / data formats to embrace more of an extendable “Web Linking” approach datatracker.ietf.org/doc/html/rfc... (cred to @mnot.net)

But on a related topic, if the ATProto would start supporting WebFinger based discovery rather than just its own limited .well-known path, then some of the stuff would be gotten for free

(And this is very much a non-IndieWeb answer as WebFinger is not in line with the general approach of IndieWeb)

IndieWeb isn’t just about microformats – the majority of it is the wiki and movement that documents prior art, experiences, attempts etc

And my point wasn’t that ATProto should become the IndieWeb or adopt the IndieWeb, it’s that it should not repeat reinventing yet another needless new thing

But preferably not mimic Mastodon in disregarding prior art and creating for themselves while naming it so that it’s perceived as something bigger. See eg my comment in their PR: github.com/mastodon/mas...

ATProto and the IndieWeb have a lot in common structurally

Both, and preferably a feed that contains both and another feed that contains just long form (different readers are suited for different content)

@pepelsbey.dev @lukewarlow.dev Perhaps there needs to be some more blogging / tutorials / references on how to constructively engage with this?

Such a one could also mention the possibility to sponsor @openwebdocs.org as a way to bring more hands on deck in improving the documentation

It’s real sad that the UNIFIL will be withdrawn rather than doubled down upon

Instead the UN Security Council has decided that also the UNIFIL – which has been in place for decades – should be disbanded at the end of next year.

Why bring less global accountability to the region? Isn’t there an urgent need to bring in more? To protect and safeguard?

Being used to eg list the top dependents of standard, neostandard etc in github.com/neostandard/... and being run through scheduled workflows like: github.com/neostandard/...

I use @ecosystems.mastodon.social.ap.brid.gy for github.com/voxpelli/lis...

This is why filing simple issues shouldn’t be as frowned upon as it currently is in large parts of the OSS community :/ (Not sure how it’s like in MDN)

Have you tried contributing a fix? It’s on GitHub and everyone can edit, I even made this screen recording a while back to help out showing how to those who may not be very used GitHub: bsky.app/profile/voxp...

You’re absolutely correct

Have you looked into whether you can use “git subtree” instead? Especially with the “--squash” flag it can be real powerful and doesn’t add any external repository dependencies apart from when pulling or pushing changes of course manpages.debian.org/testing/git-...