shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

268
active users

#webstandards

0 posts0 participants0 posts today
Holger Hellinger<p>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.</p><p>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.“</p><p><a href="https://hellinger.wtf/tags/Barrieren" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Barrieren</span></a> <a href="https://hellinger.wtf/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
Steve Faulkner<p>Interview with Lola Odelola <span class="h-card" translate="no"><a href="https://mastodon.social/@lolaodelola" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lolaodelola</span></a></span> </p><p>"Lola Odelola is a force to be reckoned with. Which is why TetraLogical are delighted to sponsor her work on the W3C Technical Architecture Group (TAG)"</p><p><a href="https://mastodon.social/tags/ARIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARIA</span></a> <a href="https://mastodon.social/tags/AT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AT</span></a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p><p><a href="https://tetralogical.com/blog/2025/07/02/interview-with-lola-odelola/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tetralogical.com/blog/2025/07/</span><span class="invisible">02/interview-with-lola-odelola/</span></a></p>
vruz<p>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. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
vruz<p>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. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
vruz<p>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. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a></p>
xoron :verified:<p>File encryption with a browser.</p><p>I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCryptoAPI</span></a> and I'm impressed!</p><p>When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystemAPI</span></a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encrypt</span></a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>store</span></a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>localstorage</span></a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a>!</p><p>I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapps</span></a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> vulnerabilities since the code is served over the web, so I've <a href="https://infosec.exchange/tags/OpenSourced" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSourced</span></a> my demo! You can check it out, and it should even work if <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHubPages</span></a>.</p><p>Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dim.positive-intentions.com/?p</span><span class="invisible">ath=/story/usefs--encrypted-demo</span></a></p><p>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</span></a></p><p>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/dim/blob/staging/src/hooks/useFS.js</span></a></p><p>IMPORTANT NOTES (PLEASE READ!):<br> * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>demonstration</span></a> purposes only.<br> * It has NOT been reviewed or audited. Do NOT use for sensitive data.<br> * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.<br> * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VeraCrypt</span></a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proofofconcept</span></a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>browser</span></a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>APIs</span></a>.</p><p><a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Encryption</span></a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cryptography</span></a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Frontend</span></a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDevelopment</span></a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coding</span></a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Developer</span></a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tech</span></a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GitHub</span></a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MastodonDev</span></a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Programming</span></a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FileSystem</span></a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAPI</span></a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProofOfConcept</span></a></p>
🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸<p>URLs should be able to include HTTP verbs and headers. </p><p>They say "URLs define the "what" not the "how"" but protocol prefixes, file extensions, and query parameters are part of the how and yet they all exist in the URL. </p><p>Leaving HTTP verbs and headers out of URLs was an arbitrary decision.</p><p><a href="https://mastodon.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a> <a href="https://mastodon.social/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://mastodon.social/tags/hypermedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hypermedia</span></a> <a href="https://mastodon.social/tags/hateoas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hateoas</span></a> <a href="https://mastodon.social/tags/webStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webStandards</span></a> <a href="https://mastodon.social/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>html</span></a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a></p>
Web Accessibility Initiative<p>W3C Accessibility Specialist Daniel Montalvo will be at the Inclusive Africa Conference 3–5 June 2025. </p><p>Daniel’s sessions are available free for remote participants:<br> - 12.10pm (EAT), 3 June: Global Implementation of Accessibility<br> - 2.40pm (EAT), 3 June: Roundtable on Developing Africa’s Digital Accessibility Standard</p><p>Registration: <a href="https://kutanaevents.com/events/inclusive_africa_conference" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">kutanaevents.com/events/inclus</span><span class="invisible">ive_africa_conference</span></a></p><p><a href="https://w3c.social/tags/DigitalAccessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalAccessibility</span></a> <br><a href="https://w3c.social/tags/WAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WAI</span></a> <br><a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>
W3C Developers<p>🚀 Exciting news! Are you in the EU 🇪🇺 and seeking funding for your <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w3c</span></a></span> <a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> work? Don’t miss this opportunity — <a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>w3cTPAC</span></a> in 🇯🇵 is coming up fast!</p><p>📄 Apply now for the StandICT.eu 9th Open Call: <a href="https://standict.eu/standicteu-2026-9th-open-call" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">standict.eu/standicteu-2026-9t</span><span class="invisible">h-open-call</span></a></p><p>⏱️ Deadline is 27 June 2025</p>
Steve Faulkner<p>🖖 The “W” in WCAG stands for “woke”</p><p><a href="https://mastodon.social/tags/Woke" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Woke</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a> <a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WCAG</span></a></p>
DoctorG ♀️🏳️‍🌈<p><span class="h-card" translate="no"><a href="https://social.vivaldi.net/@brucelawson" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>brucelawson</span></a></span> Those framework dudes know anything about <a href="https://social.vivaldi.net/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accessibility</span></a> and <a href="https://social.vivaldi.net/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a>. <a href="https://social.vivaldi.net/tags/ablism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ablism</span></a></p>
Amelia Bellamy-Royds<p>A reminder that if you're interested in <a href="https://front-end.social/tags/SVG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SVG</span></a> and the <a href="https://front-end.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> process, and specifically about trying to get SVG standardization back into gear, there is an open meeting on the topic today. It's hosted by Eric Meyer ( <span class="h-card" translate="no"><a href="https://mastodon.social/@Meyerweb" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Meyerweb</span></a></span> ) of Igalia, as part of W3C Breakouts Day.</p><p>Starts in 5.5 hours. You'll need a w3.org account to sign up; meeting is via zoom with irc chat.</p><p><a href="https://www.w3.org/events/meetings/09b7b3fd-9e91-4696-a96d-ee8df6c404f3/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/events/meetings/09b7b3f</span><span class="invisible">d-9e91-4696-a96d-ee8df6c404f3/</span></a></p>
dusoft<p>Yep, <a href="https://fosstodon.org/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PHP</span></a> website, two scrollbars are definitely way to go!<br><a href="https://fosstodon.org/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UX</span></a> <a href="https://fosstodon.org/tags/UI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UI</span></a> <a href="https://fosstodon.org/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://fosstodon.org/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>html</span></a> <a href="https://fosstodon.org/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a> <a href="https://fosstodon.org/tags/css" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>css</span></a> <a href="https://fosstodon.org/tags/layout" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>layout</span></a></p>
Vivaldi<p>Hey web devs, ever used CSS Grid or the :has() selector? Ever wondered how they actually made it into browsers?</p><p>Stephanie Stimac (<span class="h-card" translate="no"><a href="https://toot.cafe/@seaotta" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>seaotta</span></a></span>) from Igalia (<span class="h-card" translate="no"><a href="https://floss.social/@igalia" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>igalia</span></a></span>) spills the beans on how new web features get funded, developed, and shipped. Turns out, it’s not as simple as you’d think.</p><p>Catch the convo on the latest For a Better Web Podcast.</p><p>📺 Watch: <a href="https://www.youtube.com/watch?v=loBPN54siCE" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=loBPN54siC</span><span class="invisible">E</span></a><br>🎧 Listen: <a href="https://open.spotify.com/episode/1tzEQYpQ00fGx6gLwvkhXK" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">open.spotify.com/episode/1tzEQ</span><span class="invisible">YpQ00fGx6gLwvkhXK</span></a> </p><p><a href="https://social.vivaldi.net/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://social.vivaldi.net/tags/Design" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Design</span></a> <a href="https://social.vivaldi.net/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://social.vivaldi.net/tags/Web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Web</span></a> <a href="https://social.vivaldi.net/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a></p>
Steve Faulkner<p>Scope of WCAG 2.2 / 2.1 errata changes</p><p>Some agree with changes other disagree</p><p>I want WCAG to be as unambiguous as possible, how about you?</p><p>Some people have based their KLOUT on being the interpreters of the WCAG scratchings...</p><p><a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WCAG</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a></p><p><a href="https://github.com/w3c/wcag/discussions/4188" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/w3c/wcag/discussion</span><span class="invisible">s/4188</span></a></p>
lola<p>🌐 I’ve spent years working on web standards to make the internet open and inclusive. I’m excited to continue participating in the W3C—shaping the future of the web through collaboration and advocacy. This work requires resources, and I need your support to continue!</p><p>💡 Sponsor my work to directly support efforts to ensure web standards work for everyone.</p><p><a href="https://opencollective.com/lolas-lab/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">opencollective.com/lolas-lab/</span><span class="invisible"></span></a></p><p>Let’s build a better web together. ❤️</p><p><a href="https://mastodon.social/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWeb</span></a> <a href="https://mastodon.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>W3C</span></a></p>
Jonathan Kamens 86 47<p>Poll: do you think servers generating link previews should obey robots.txt? I think they shouldn't, because that's a misinterpretation of the purpose of robots.txt. At least some of the folks who work on Mastodon seem to agree (<a href="https://github.com/mastodon/mastodon/issues/21738#issuecomment-1328292663" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/mastodon/mastodon/i</span><span class="invisible">ssues/21738#issuecomment-1328292663</span></a>): "No other social media software has used robots.txt to govern its crawling."<br><a href="https://federate.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a> <a href="https://federate.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a><br>🧵2/?</p>
jmcnaughton<p>I spent the day getting to know <a href="https://freshrss.org/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">freshrss.org/</span><span class="invisible"></span></a> </p><p>I've tried many feed readers over the years and never managed to form a habit with any of them. Maybe this is the one?</p><p>It's been great so far, and because it's a web application it can generate new feeds based on filters and tags and share the feeds as HTML or RSS! Pretty cool!</p><p>It's too bad not as many websites have RSS feeds anymore.</p><p><a href="https://freefree.ps/tags/rss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rss</span></a> <a href="https://freefree.ps/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeSoftware</span></a> <a href="https://freefree.ps/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://freefree.ps/tags/agpl3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>agpl3</span></a> <a href="https://freefree.ps/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHosting</span></a></p>
Luke Dorny<p>Raising awareness and encouraging the use of web standards in the 2000s created an energy that helped us bring the web to where it is today. <br>Grass roots movements work. <br><a href="https://typo.social/tags/BlueBeanieDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BlueBeanieDay</span></a> <a href="https://typo.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a> <a href="https://typo.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebDev</span></a> <a href="https://typo.social/tags/Blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Blog</span></a> <a href="https://typo.social/tags/Design" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Design</span></a> <a href="https://front-end.social/@zeldman/113571069200698011" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">front-end.social/@zeldman/1135</span><span class="invisible">71069200698011</span></a></p>
World Wide Web Consortium<p>☞ today November 30 is the 17th Blue Beanie Day, an annual international celebration and support of Web standards.</p><p>Thanks to all who help develop standards, promote the open web, and thanks to <span class="h-card" translate="no"><a href="https://front-end.social/@zeldman" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>zeldman</span></a></span> for starting it in 2007!</p><p>Listen to our Founder, Web inventor Sir Tim Berners-Lee, on what part of W3C he's most proud of:<br><a href="https://youtu.be/qdNQ3dyALAM" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/qdNQ3dyALAM</span><span class="invisible"></span></a></p><p>Watch "Web standards for the future" for the reasons for Web standards<br><a href="https://vimeo.com/110256895" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">vimeo.com/110256895</span><span class="invisible"></span></a></p><p><a href="https://w3c.social/tags/BlueBeanieDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BlueBeanieDay</span></a> <a href="https://w3c.social/tags/bbd17" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bbd17</span></a> <a href="https://w3c.social/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebStandards</span></a></p>