If you are interested in how the Fediverse really works and some of the key people making it happen, sit down with a coffee and check out one (or all!) of the presentations from #fedicon.
Mine was about my journey finding the Fediverse and eventually teaming up with folks to create socialbc.ca and what I learned along the way.
And yes, I am pretty sure we are in a Stanley Kubrick movie.
#fediverse #mastodon #socialbc #democracy #webstandards #activitypub #community
https://spectra.video/w/p9nScG9XFX81iE89ufmWUM
Good news everyone!
We are extremely thankful and excited to be supported once again by @nlnet to work on our roadmap ( https://dokie.li/docs#roadmap ) as part of NGI Zero Commons Fund.
Read the announcement:
https://nlnet.nl/news/2025/20250804-announcement-grants-CommonsFund.html
The project:
https://nlnet.nl/project/Dokieli-Collaborative/
This time we will focus on these tasks:
* End-to-end encryption
* Collaborative editing
* Code modularization
* Internationalization
* Browser extension improvements
And here I am with a spicy take on the <hgroup> HTML element of all things.
Is the <hgroup> element redundant and should we handle headings and subheadings differently instead of re-introducing the element?
https://aldavigdis.dev/2025/07/25/taming-html-headings-subheadings-and-overlines/
Just published: “Designing with Abstractions: CSS and the Case of Masonry Layouts”
This (academic) article explores CSS as both a technical system and a design object. It examines how this is shaped through negotiation between conceptual models, implementation constraints, and interface considerations, focusing on the Masonry layout debates.
Appreciation to those participating in CSS WG debates and making this work visible.
When applying a thick border around an element in multiple colors, the corners meet at a 45-degree angle forming a diamond. That is established and seems reasonable.
But, when you set a thick edge on one side, the thin 1px border gets squeezed into a slope, and won't reach the edge! And the sidebar forms a *trapezoid*!
This is most noticable on modern high-DPI screens. It is rather unsatisfying, and hard to unsee...
Wenn „Developer“ den Plain-Text-Teil einer E-Mail „vergessen“ und stattdessen den Rest für Dokumentation missbrauchen, sehen Menschen wie ich, die keine HTML-Mails lesen wollen, und Menschen, die darauf angewiesen sind, oft gar nichts mehr.
Ich merke das auch im Alltag: Vor 20 Jahren war es selbstverständlich, einen Plain-Text-Teil bereitzustellen. Heute denken viele nur noch: „Hat doch eh jeder HTML-Mails.“
Meanwhile the discussion on defining "view"rumbles on: 52 comments · 137 replies
I have largely stayed out of it as I have other more pressing shit to do.
Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. #compsci #webdev #webstandards #opensource
The Web's superpower is its openness. Native JS templating makes JS more ergonomic. Direct WASM→DOM makes the web more OPEN. Which better serves the platform's future? The web shouldn't privilege one language. True platform evolution means equal access to core capabilities for all languages. That's how we get the next generation of web innovation. #compsci #webdev #webstandards #opensource
Why add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. #compsci #webdev #wasm #webstandards
File encryption with a browser.
I've been exploring the #WebCryptoAPI and I'm impressed!
When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!
I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.
Live Demo: https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo
Demo Code: https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js
Hook Code: https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js
IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration purposes only.
* It has NOT been reviewed or audited. Do NOT use for sensitive data.
* The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.
* This is NOT meant to replace robust solutions like #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.
Congrats to editors Matt Garrish and @tzviya for the two newly published @w3c #WebStandards "Digital Publishing WAI-ARIA Module 1.1 (DPUB-ARIA)" and "Digital Publishing Accessibility API Mappings 1.1 (DPUB-AAM)". #timetoadopt
https://www.w3.org/TR/dpub-aria-1.1/
https://www.w3.org/TR/dpub-aam-1.1/
#dokieli ( https://dokie.li/ ) is a web-based #decentralized article #publishing and #annotation #application and browser extension, built as an #opensource ( https://git.dokie.li/ ) project using #webstandards.
dokieli enables individuals and communities to publish, share, and annotate articles using their preferred identities and storage, and you are always free to switch to another application and take your content with you.
W3C Accessibility Specialist Daniel Montalvo will be at the Inclusive Africa Conference 3–5 June 2025.
Daniel’s sessions are available free for remote participants:
- 12.10pm (EAT), 3 June: Global Implementation of Accessibility
- 2.40pm (EAT), 3 June: Roundtable on Developing Africa’s Digital Accessibility Standard
Registration: https://kutanaevents.com/events/inclusive_africa_conference
How strict should the application of "2.5.3: Label in Name" be for languages other than English?
It's been three months since I became one of the first-ever W3C TAG Associates! I'm grateful for the opportunity to help shape impactful web standards and work with our great community. I'm still learning, but I'm proud to have supported the W3C TAG in conducting several design reviews already. Learn more about the role: https://w3ctag.org/associates/ #webstandards #W3CTAG
Exciting news! Are you in the EU
and seeking funding for your @w3c #WebStandards work? Don’t miss this opportunity — #w3cTPAC in
is coming up fast!
Apply now for the StandICT.eu 9th Open Call: https://standict.eu/standicteu-2026-9th-open-call
Deadline is 27 June 2025
The “W” in WCAG stands for “woke”
Off to State of the Browser #SOTB tomorrow the #WebStandards conference organized by @dletorey and @webstandards team. Excited to learn from @sarajw and @matuzo amongst others.
If you are attending come say