Recent searches

No recent searches

Search options

Not available on mastodon.zunda.ninja.
mastodon.zunda.ninja is one of the many independent Mastodon servers you can use to participate in the fediverse.
Zundon is a single user instance as home of @zundan as well as a test bed for changes of the code.

Administered by:

Server stats:

1
active users

mastodon.zunda.ninja: AboutPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.5.0-alpha.1+afcae57e-ruby-3.4.5

#webapps

0 posts0 participants0 posts today
Frontend Dogma<p>How to Protect Your Web Applications From XSS, by <span class="h-card" translate="no"><a href="https://mastodon.social/@torgo" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>torgo</span></a></span> (<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>):</p><p><a href="https://www.w3.org/blog/2025/how-to-protect-your-web-applications-from-xss/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/blog/2025/how-to-protec</span><span class="invisible">t-your-web-applications-from-xss/</span></a></p><p><a href="https://mas.to/tags/howtos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>howtos</span></a> <a href="https://mas.to/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapps</span></a> <a href="https://mas.to/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mas.to/tags/xss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xss</span></a></p>
W3C Developers<p>The newly published <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/CandidateRecommendation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CandidateRecommendation</span></a> "Device Posture API" allows <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a> to request and be notified of changes of the posture of a device <a href="https://w3c.social/tags/timetoimplement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>timetoimplement</span></a><br><a href="https://www.w3.org/TR/device-posture/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/TR/device-posture/</span><span class="invisible"></span></a></p><p>Device posture refers to its physical position, detected via sensors. With foldable devices, understanding posture is key for responsive design, especially when the device isn’t fully flat.</p><p>Read the explainer: <a href="https://github.com/w3c/device-posture/blob/gh-pages/README.md" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/w3c/device-posture/</span><span class="invisible">blob/gh-pages/README.md</span></a><br>Feedback welcome: <a href="https://github.com/w3c/device-posture/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/w3c/device-posture/</span><span class="invisible"></span></a></p>
W3C Developers<p>🗓️ Wed. 25 Sept.: 8:30am - 5:00pm PDT </p><p>The <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> Breakouts schedule is now available! <br>▶️ <a href="https://www.w3.org/2024/09/TPAC/breakouts.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/2024/09/TPAC/breakouts.</span><span class="invisible">html</span></a></p><p><a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>w3cTPAC</span></a> participants organize discussions among the full W3C <a href="https://w3c.social/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> about new or existing topics. This year, a total of 89 proposals were allocated across 10 categories including topics like <a href="https://w3c.social/tags/identity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>identity</span></a>, <a href="https://w3c.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a>, permissions, <a href="https://w3c.social/tags/WebComponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebComponents</span></a>, <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a>, and more.</p>
W3C Developers<p>Newly created <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/WorkingGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WorkingGroup</span></a>: "Linked Web Storage"! </p><p>The group's mission is to create <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a> with loosely coupled data storage, <a href="https://w3c.social/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>authentication</span></a>, and access control by standardizing a <a href="https://w3c.social/tags/protocol" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>protocol</span></a> between apps and identity/storage servers.<br>▶️ <a href="https://www.w3.org/groups/wg/lws/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/groups/wg/lws/</span><span class="invisible"></span></a></p><p>The group will deliver the Linked Web Storage Protocol specification, based among other input on the the <a href="https://w3c.social/tags/Solid" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Solid</span></a> Protocol developed by the Solid <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CommunityGroup</span></a></p>
W3C Developers<p>Large Language Models (LLMs) are being distributed across many devices and platforms. Having these models available on-device can help reduce the need for sending private data to cloud-hosted systems.</p><p>At the <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> member meeting last month in <a href="https://w3c.social/tags/Hiroshima" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hiroshima</span></a> 🇯🇵, Chunhui Mo (Huawei) explored what it would take to expose these LLMs to <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a> through a Web <a href="https://w3c.social/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>API</span></a> and the advantages it could bring in terms of <a href="https://w3c.social/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a>, <a href="https://w3c.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> and <a href="https://w3c.social/tags/performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>performance</span></a>. </p><p>🎬 Watch the video: <a href="https://youtu.be/7S60LNBAFj0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/7S60LNBAFj0</span><span class="invisible"></span></a></p>
W3C Developers<p>The <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> breakouts day 2024 recap is out!<br>▶️ <a href="https://www.w3.org/blog/2024/breakouts-day-2024-recap/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/blog/2024/breakouts-day</span><span class="invisible">-2024-recap/</span></a></p><p>Participants organized 19 sessions, covering: <br>- detailed technical discussions (FedCM, <a href="https://w3c.social/tags/RDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RDF</span></a>)<br>- strategic discussions (<a href="https://w3c.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a>, <a href="https://w3c.social/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Privacy</span></a>, funding the ecosystem)<br>- ideas for more efficient work (incubation, managing registries)<br>- new/proposed groups (<a href="https://w3c.social/tags/identity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>identity</span></a>, real estate)<br>- Web for <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developers</span></a> (<span class="h-card" translate="no"><a href="https://mozilla.social/@MDN" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>MDN</span></a></span>, <span class="h-card" translate="no"><a href="https://front-end.social/@openwebdocs" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>openwebdocs</span></a></span>, installing <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a>) </p><p>Check session slides, minutes, notes and links, and potential follow-up discussions.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://blob.cat/users/hexaheximal" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>hexaheximal@blob.cat</span></a></span> <span class="h-card" translate="no"><a href="https://wetdry.world/@esm" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>esm</span></a></span> <span class="h-card" translate="no"><a href="https://wetdry.world/@hexaheximal" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>hexaheximal@wetdry.world</span></a></span> ...and even if we think local <a href="https://mstdn.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a> are a legitimate way to handle sensitive comms - they ain't but let's just assume they are for the sake of argument - WHY would you do anything beyond a .desktop file that includes startup parameters for <a href="https://mstdn.social/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a> (or even <a href="https://mstdn.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> if you're that kind of Cyber-Masochist!) that specify the browser, and the file to load.</p><p>Because any good <a href="https://mstdn.social/tags/WebApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApp</span></a> should be reduceable as <a href="https://mstdn.social/tags/HTML5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTML5</span></a> + <a href="https://mstdn.social/tags/JS6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JS6</span></a> + <a href="https://mstdn.social/tags/CSS3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSS3</span></a> and measured in kB or maybe a few MB.</p>
elementary<p>We’re shipping the very latest <span class="h-card" translate="no"><a href="https://floss.social/@gnome" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gnome</span></a></span> Web 43 which includes support for creating <a href="https://mastodon.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a> which show in the applications menu. They can have their own settings including privacy controls and can even run in the background</p>
Alexander Martin<p>I have an idea to replace both <a href="https://fosstodon.org/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApps</span></a> and <a href="https://fosstodon.org/tags/electron" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Electron</span></a> with something that makes more sense.</p><p>Basically, we build a stand-alone WebAssembly runtime with some UI framework (Qt?) and portable OS interfaces. With that done, it's just a matter of porting the runtime to as many platforms as possible and now you can do an actually good version of Write-Once-Run-Anywhere using a variety of pre-existing tools and languages.</p>
TrendingLive feeds
About