Open Vulnerability Report<p>🛡️ The OVR Foundation website is live!<br>We were founded after the U.S. government’s 2025 threat to cut funding for the CVE program — a crucial piece of the cybersecurity landscape. Now, we’re working to create a decentralized, resilient standard for global vulnerability coordination.</p><p>🔧 Small updates will follow in the next few days.<br>🌍 Visit us: <a href="https://ovr-foundation.org" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ovr-foundation.org</span><span class="invisible"></span></a><br>🔗 <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CyberSecurity</span></a> <a href="https://infosec.exchange/tags/OVR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OVR</span></a> <a href="https://infosec.exchange/tags/Infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Infosec</span></a> <a href="https://infosec.exchange/tags/Decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Decentralization</span></a> <a href="https://infosec.exchange/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> <a href="https://infosec.exchange/tags/CVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CVE</span></a></p>
Recent searches
No recent searches
Search options
Only available when logged in.
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:
257active users
shakedown.social: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.7
#openstandard
0 posts · 0 participants · 0 posts today
Grüne Kreisverband Stade<p><a href="https://gruene.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mastodon</span></a> im <a href="https://gruene.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fediverse</span></a> bietet dir einen Kurznachrichtendienst mit eingebauter Daten-Souveränität. </p><p>„Deine <a href="https://gruene.social/tags/Nachrichten" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Nachrichten</span></a> gehören dir und werden durch das Veröffentlichen nicht zum Eigentum eines Einzelnen, der damit reich wird.“</p><p>Mastodon wurde in <a href="https://gruene.social/tags/Jena" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Jena</span></a> in <a href="https://gruene.social/tags/Europa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Europa</span></a> erfunden. Die Software und das Protokoll sind <a href="https://gruene.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> und <a href="https://gruene.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a>.</p><p><span class="h-card" translate="no"><a href="https://gruene.social/@weddige" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>weddige</span></a></span> <span class="h-card" translate="no"><a href="https://gruene.social/@kaibojens" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>kaibojens</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@Gargron" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Gargron</span></a></span></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@nikolaidis" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nikolaidis</span></a></span> using <a href="https://infosec.space/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WhatsApp</span></a> or any other shitty <a href="https://infosec.space/tags/messenger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>messenger</span></a> that isn't an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> is always a <em>big red flag</em> for me!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.social/@stux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stux</span></a></span> yeah, cuz <a href="https://infosec.space/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ActivityPub</span></a> as an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> can be reimplemented and self-hosted an infinite amount if times, so even if all the current existing options got bullied ibto closure, it'll remain useable.</p><ul><li>Just like <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IRC</span></a>, <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XMPP</span></a> & <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>eMail</span></a> are...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://digipres.club/@foone" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>foone</span></a></span> needless to say I doubt anyone will actually ever implement a <em>"<a href="https://infosec.space/tags/SecureUSB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SecureUSB</span></a>"</em> implementation even if it was an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> and doing so wouldn't even require <a href="https://infosec.space/tags/USB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>USB</span></a>-IF membership or anything.</p><p>Ideally true <em><a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SelfCustody</span></a> with proper keys</em> would be implemented, but that would still have <em>Trust Root Probems</em> but worse than <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CensorBoot</span></a>...</p>
Erik Jonker<p>actually an interesting idea and proposal, MCP, model context protocol.<br><a href="https://www.anthropic.com/news/model-context-protocol" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">anthropic.com/news/model-conte</span><span class="invisible">xt-protocol</span></a><br><a href="https://mastodon.social/tags/openstandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openstandard</span></a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.social/tags/mcp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mcp</span></a> <a href="https://mastodon.social/tags/ai" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ai</span></a> <a href="https://mastodon.social/tags/anthropic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>anthropic</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://uwu.social/@koakuma" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>koakuma</span></a></span> <span class="h-card" translate="no"><a href="https://woof.tech/@techokami" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>techokami</span></a></span> also <a href="https://infosec.space/tags/UltraSparcT2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UltraSparcT2</span></a> as cool as it was at release (including dual 10Gbit-NICs and hardware RNG on die) has a lot of things noone would want to deal with in 2024 (i.e. DDR2-FBDIMMs).</p><ul><li>Plus <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCv</span></a> unlike <a href="https://infosec.space/tags/SPARCv9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPARCv9</span></a> amd <a href="https://infosec.space/tags/OpenPOWER" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenPOWER</span></a> was designed on a clean slate in academia by people who had dealt with <a href="https://infosec.space/tags/RISC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISC</span></a> & <a href="https://infosec.space/tags/CISC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CISC</span></a> architectures and needed something <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> as they can't just violate NDAs nilly-willy for teaching.</li></ul><p>Pretty shure <span class="h-card" translate="no"><a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stman</span></a></span> could write an entire curriculum on why <a href="https://infosec.space/tags/SPARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPARC</span></a>, <a href="https://infosec.space/tags/PowerPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PowerPC</span></a>, <a href="https://infosec.space/tags/s390x" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>s390x</span></a> and even <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARM</span></a> / <a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARM64</span></a> should not be pursued and why <a href="https://infosec.space/tags/mc68k" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mc68k</span></a> died alongside the unfixable-by-design mess that is <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ix86</span></a> & <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>amd64</span></a>.</p><ul><li>Plus RISCv's ISA has been an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> from the get go, whereas the efforts by <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Oracle</span></a> nee <a href="https://infosec.space/tags/Sun" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Sun</span></a> and <a href="https://infosec.space/tags/IBM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IBM</span></a> were mostly done in reaction to it and to keep the few invested licensees and co-designers onboard and not drop the platform entirely...</li></ul><p>Look, I'd love to get my hands on some Sun SPARC Hardware but aside from making my room hot and noisy there isn't much to justify blowing likely over half a Euro per hour (electricity price: € 0,40/kWh) just to have it up and running, as compared to a <a href="https://infosec.space/tags/PiCluster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PiCluster</span></a> like those <span class="h-card" translate="no"><a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>geerlingguy</span></a></span> had built multiple times are more practical.</p><ul><li>For comparison: It's like driving a 2011 Ford CVPI-71 with a 11,9l SONNY'S SAR-729 engine for commuting from Leverkusen to Köln when there's ample of affordable, reliable and fast public transport that gets me faster from Opladen to Deutz than it takes to drive up the 15th deck of a parking garage just to find a spot to park that 5,7m long street yacht where one can climb out of it from the doors and not the trunk!</li></ul><p>And that's just bottom-billing, low-cost ARM SoC tech designed for a price tag (to the point that until the <a href="https://infosec.space/tags/Pi5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pi5</span></a> they neither included a power button nor <a href="https://infosec.space/tags/RTC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RTC</span></a> onboard!</p><ul><li>OFC RISC-V is still 5-25+ years behind <a href="https://infosec.space/tags/ARMv9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARMv9</span></a> solely based off <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>patents</span></a>, <a href="https://infosec.space/tags/budget" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>budget</span></a> and <a href="https://infosec.space/tags/PersonnelHours" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PersonnelHours</span></a> invested in it, so it's barely getting on-par with 10-20yr old ARM devices in terms.of power and support.</li></ul>
Paolo Melchiorre<p><span class="h-card" translate="no"><a href="https://social.opensource.org/@osi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>osi</span></a></span> <span class="h-card" translate="no"><a href="https://fedi.simonwillison.net/@simon" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>simon</span></a></span> <span class="h-card" translate="no"><a href="https://kfogel.org/users/kfogel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>kfogel</span></a></span> The Open Source Initiative should publish documents in Open Formats. I recommend you to adopt Open Standards for documents from now on (e.g. HTML) and they are certainly more accessible to everyone (e.g. blind people). Is there a public repository with the source in Latex for this document?</p><p><a href="https://fosstodon.org/tags/OSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OSI</span></a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://fosstodon.org/tags/OpenFormat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenFormat</span></a> <a href="https://fosstodon.org/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> <a href="https://fosstodon.org/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTML</span></a> <a href="https://fosstodon.org/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Accessibility</span></a> <a href="https://fosstodon.org/tags/A11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>A11y</span></a> <a href="https://fosstodon.org/tags/TexLatex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TexLatex</span></a> <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FOSS</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://digipres.club/@foone" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>foone</span></a></span> +9001%</p><p>Also it should be a point-symmetric, simple COTS connector...</p><ul><li>Like the 7,9×5,5mm <em>"<a href="https://infosec.space/tags/ThinkPad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThinkPad</span></a></em>" barrel jack that just shoves 20V DC into the device!</li></ul><p>That being said, USB-C <a href="https://infosec.space/tags/PiwerDelivery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PiwerDelivery</span></a> / <a href="https://infosec.space/tags/USBpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>USBpd</span></a> is way more complex, it at least offers a more universal alternative by using an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> that can shove up to 240W (48V DC @ 5A) into a device...</p>
Jan Wildeboer 😷:krulorange:<p>But it can be done. Communities can buy back or create themselves the power lines needed for domestic use. They can build communal power storage units that decouple (hyper)local grids from the Big Grid. It needs an <a href="https://social.wildeboer.net/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> to control input and output to that local grid. Which is being worked on. Clean electricity can power private homes very soon. For free.</p>
petersuber<p>Update. On the obstacles to this kind of bridge-building.<br><a href="https://flipboard.video/w/2Jj46hJaUQQG5TuiBYi9TR" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">flipboard.video/w/2Jj46hJaUQQG</span><span class="invisible">5TuiBYi9TR</span></a></p><p>"Ryan’s work to connect <a href="https://fediscience.org/tags/Bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bluesky</span></a>, which uses the <a href="https://fediscience.org/tags/ATProtocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ATProtocol</span></a>, to <a href="https://fediscience.org/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mastodon</span></a> & other platforms using the <a href="https://fediscience.org/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ActivityPub</span></a> protocol ignited a firestorm. [He] wanted to advance the <a href="https://fediscience.org/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fediverse</span></a>’s promise of <a href="https://fediscience.org/tags/interoperability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>interoperability</span></a> but…inadvertently stirred up culture clashes between platforms & fervent discussions around consent, maintaining safety, fears of commercialism, & what being an <a href="https://fediscience.org/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> really means."</p>
Norobiik @Norobiik@noc.social<p><a href="https://noc.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> is an <a href="https://noc.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> instruction set architecture(<a href="https://noc.social/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISA</span></a>) that is most frequently positioned as a competitor to <a href="https://noc.social/tags/Arm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Arm</span></a>. It's low power, it's aimed at smaller devices, and it's completely open for anyone to use and implement.Now, X-Silicon has announced that it has created a new "C-GPU," which is a <a href="https://noc.social/tags/CPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPU</span></a> core with <a href="https://noc.social/tags/GPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GPU</span></a> capabilities.</p><p>Groundbreaking RISC-V chip combines CPU, GPU, and <a href="https://noc.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> capabilities into one core<br><a href="https://www.xda-developers.com/risc-v-cpu-gpu-ai-one-core/" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">xda-developers.com/risc-v-cpu-</span><span class="invisible">gpu-ai-one-core/</span></a></p>
Jan Wildeboer 😷:krulorange:<p>It's only an <a href="https://social.wildeboer.net/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> if you can choose between at least two <a href="https://social.wildeboer.net/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> implementations of which one is not produced by a member of the SSO (Standard Setting Organisation). And yes, it is OK if more implementations exist that can even be proprietary, as long as interoperability is a given.</p>
Jan Wildeboer 😷:krulorange:<p>A kinda weird question. If you were to write an <a href="https://social.wildeboer.net/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a>, just the standard document itself: Under what license would you put it to make sure it is irrevocably available for free to anyone but also making sure it cannot be altered by downstream recipients? 1/n</p>
Jan Wildeboer 😷:krulorange:<p><span class="h-card"><a href="https://masto.ai/@danjac" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>danjac</span></a></span> <span class="h-card"><a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>smallcircles</span></a></span> <span class="h-card"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> <span class="h-card"><a href="https://venera.social/profile/fedidevs" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>fedidevs</span></a></span> <span class="h-card"><a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Codeberg</span></a></span> <span class="h-card"><a href="https://mastodon.social/@dansup" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>dansup</span></a></span> <span class="h-card"><a href="https://social.network.europa.eu/@EC_NGI" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>EC_NGI</span></a></span> <span class="h-card"><a href="https://social.network.europa.eu/@EC_DIGIT" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>EC_DIGIT</span></a></span> It's what I've been saying since many years without being heard :( Every <a href="https://social.wildeboer.net/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandard</span></a> MUST consist of the Standard, an Open Source reference implementation and an open source validator to test interoperability against. All three MUST be maintained by the Standard Setting Organisation. Without this it isn't an Open Standard.</p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload