Writing Exchange

1 post1 participant0 posts today

Inautilo<a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> <a href="https://mastodon.social/tags/Introductions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Introductions</a> MCP · The standard for a shared language between AI and apps <a href="https://ilo.im/1630fl" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ilo.im/1630fl</a>_____ <a href="https://mastodon.social/tags/MCP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MCP</a> <a href="https://mastodon.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> <a href="https://mastodon.social/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://mastodon.social/tags/Applications" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Applications</a> <a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebDev</a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Frontend</a> <a href="https://mastodon.social/tags/Backend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backend</a>

Kevin Karhan :verified:<a href="https://infosec.exchange/@nikolaidis" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nikolaidis</a> using <a href="https://infosec.space/tags/WhatsApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WhatsApp</a> or any other shitty <a href="https://infosec.space/tags/messenger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#messenger</a> that isn't an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> is always a big red flag for me!

☮ ♥ ♬ 🧑‍💻What is the AT Protocol? Wikipedia: “The <a href="https://ioc.exchange/tags/ATProtocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ATProtocol</a> (Authenticated Transfer Protocol, pronounced "@ protocol" and commonly shortened to ATProto) is a protocol and <a href="https://ioc.exchange/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> for <a href="https://ioc.exchange/tags/distributed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distributed</a> <a href="https://ioc.exchange/tags/socialNetworking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#socialNetworking</a> services. It is under development by <a href="https://ioc.exchange/tags/BlueskySocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlueskySocial</a> <a href="https://ioc.exchange/tags/PBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PBC</a>, a public benefit corporation originally created as an independent research group within <a href="https://ioc.exchange/tags/Twitter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Twitter</a> to investigate the possibility of <a href="https://ioc.exchange/tags/decentralizing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralizing</a> the service.”<<a href="https://en.m.wikipedia.org/wiki/AT_Protocol" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.m.wikipedia.org/wiki/AT_Protocol</a>>

Amgine<a href="https://smores.town/@touk" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@touk</a> This reminds me of a personal rage: why do <a href="https://mamot.fr/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://mamot.fr/tags/audio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#audio</a> <a href="https://mamot.fr/tags/streaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#streaming</a> platforms not default to the <a href="https://mamot.fr/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> file formats? <a href="https://mamot.fr/tags/petpeeve" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#petpeeve</a> <a href="https://mamot.fr/tags/audiophile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#audiophile</a>

💧🌏 Greg CocksGSPy - A New Toolbox And Data Standard For Geophysical Datasets -- <a href="https://doi.org/10.3389/feart.2022.907614" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://doi.org/10.3389/feart.2022.907614</a> <-- shared paper -- <a href="https://doi.org/10.5066/P9XNQVGQ" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://doi.org/10.5066/P9XNQVGQ</a> | <a href="https://code.usgs.gov/g3sc/gspy" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://code.usgs.gov/g3sc/gspy</a> <-- shared code repository -- [an older paper, but code is in active and ongoing development/evolution] <a href="https://techhub.social/tags/GIS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GIS</a> <a href="https://techhub.social/tags/spatial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#spatial</a> <a href="https://techhub.social/tags/mapping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mapping</a> <a href="https://techhub.social/tags/geophysics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geophysics</a> <a href="https://techhub.social/tags/geophysical" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#geophysical</a> <a href="https://techhub.social/tags/NetCDF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetCDF</a> <a href="https://techhub.social/tags/datatypes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datatypes</a> <a href="https://techhub.social/tags/code" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#code</a> <a href="https://techhub.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://techhub.social/tags/library" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#library</a> <a href="https://techhub.social/tags/dataformats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dataformats</a> <a href="https://techhub.social/tags/standardisation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#standardisation</a> <a href="https://techhub.social/tags/standardization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#standardization</a> <a href="https://techhub.social/tags/openstandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openstandard</a> <a href="https://techhub.social/tags/portable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#portable</a> <a href="https://techhub.social/tags/metadata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#metadata</a> <a href="https://techhub.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://techhub.social/tags/package" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#package</a> <a href="https://techhub.social/tags/GSPy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GSPy</a> <a href="https://techhub.social/tags/methods" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#methods</a> <a href="https://techhub.social/tags/workflows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#workflows</a> <a href="https://techhub.social/tags/xarray" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xarray</a> <a href="https://techhub.social/tags/CRS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CRS</a> <a href="https://techhub.social/tags/opendata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opendata</a> <a href="https://techhub.social/tags/architecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#architecture</a> <a href="https://techhub.social/tags/toolbox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolbox</a>

small circle 🕊 in calmness"Show don't tell" of federate <a href="https://social.coop/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> code & apps doesn't work well in environment where we need "Show don't tell" of <a href="https://social.coop/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> specs to make progress. Especially if the specs are so vague that each code implementation thrown in the cauldron of <a href="https://social.coop/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> <a href="https://social.coop/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> installed base is known to only add <a href="https://social.coop/tags/ProtocolDecay" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProtocolDecay</a> and <a href="https://social.coop/tags/TechDebt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechDebt</a>.In <a href="https://social.coop/tags/Commons" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Commons</a> <a href="https://social.coop/tags/CommonSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonSense</a> makes <a href="https://social.coop/tags/CommonsSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsSense</a>: Don't introduce the opposite of <a href="https://social.coop/tags/interoperabily" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#interoperabily</a> when in pursuit of seamless interop.We need both forms of showing.

MISPThe MISP-standard.org is proud to announce the release of a new standard: Threat Actor Naming (RFC). This standard addresses one of the most critical challenges in cybersecurity information sharing—the consistent and reliable identification of threat actors.<a href="https://misp-community.org/tags/standard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#standard</a> <a href="https://misp-community.org/tags/openstandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openstandard</a> <a href="https://misp-community.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://misp-community.org/tags/misp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#misp</a> <a href="https://misp-community.org/tags/threatintelligence" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#threatintelligence</a> <a href="https://misp-community.org/tags/threatintel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#threatintel</a> 🔗 <a href="https://www.misp-standard.org/blog/Naming-Threat-Actor/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.misp-standard.org/blog/Naming-Threat-Actor/</a>

Erik Jonkeractually an interesting idea and proposal, MCP, model context protocol. <a href="https://www.anthropic.com/news/model-context-protocol" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.anthropic.com/news/model-context-protocol</a> <a href="https://mastodon.social/tags/openstandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openstandard</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://mastodon.social/tags/mcp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mcp</a> <a href="https://mastodon.social/tags/ai" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ai</a> <a href="https://mastodon.social/tags/anthropic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#anthropic</a>

Paolo Melchiorre<a href="https://social.opensource.org/@osi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@osi</a> <a href="https://fedi.simonwillison.net/@simon" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@simon</a> <a href="https://kfogel.org/users/kfogel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kfogel</a> 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?<a href="https://fosstodon.org/tags/OSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSI</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/OpenFormat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFormat</a> <a href="https://fosstodon.org/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> <a href="https://fosstodon.org/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HTML</a> <a href="https://fosstodon.org/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Accessibility</a> <a href="https://fosstodon.org/tags/A11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#A11y</a> <a href="https://fosstodon.org/tags/TexLatex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TexLatex</a> <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a>

jbz"All RISC-V does is specify what software should expect of a RISC-V processor – it is up to processor designers to decide how exactly they implement that specification. RISC-V is open and royalty free to use, but the chips themselves can be either open source designs or closed and proprietary. The RISC-V world fears it will be broadly hit with sanctions if it can't get officials to see that distinction" <a href="https://www.theregister.com/2024/05/29/riscv_messsaging_struggle/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.theregister.com/2024/05/29/riscv_messsaging_struggle/</a><a href="https://indieweb.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RISCV</a> <a href="https://indieweb.social/tags/Sanctions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sanctions</a> <a href="https://indieweb.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> <a href="https://indieweb.social/tags/Opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Opensource</a> <a href="https://indieweb.social/tags/China" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#China</a> <a href="https://indieweb.social/tags/Geopolitics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geopolitics</a>

Jan Wildeboer 😷:krulorange: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">#OpenStandard</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.

petersuberUpdate. On the obstacles to this kind of bridge-building. <a href="https://flipboard.video/w/2Jj46hJaUQQG5TuiBYi9TR" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://flipboard.video/w/2Jj46hJaUQQG5TuiBYi9TR</a>"Ryan’s work to connect <a href="https://fediscience.org/tags/Bluesky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bluesky</a>, which uses the <a href="https://fediscience.org/tags/ATProtocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ATProtocol</a>, to <a href="https://fediscience.org/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> & other platforms using the <a href="https://fediscience.org/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</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">#fediverse</a>’s promise of <a href="https://fediscience.org/tags/interoperability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#interoperability</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">#OpenStandard</a> really means."

Norobiik @Norobiik@noc.social<a href="https://noc.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RISCV</a> is an <a href="https://noc.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> instruction set architecture(<a href="https://noc.social/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ISA</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">#Arm</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">#CPU</a> core with <a href="https://noc.social/tags/GPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPU</a> capabilities.Groundbreaking RISC-V chip combines CPU, GPU, and <a href="https://noc.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> capabilities into one core <a href="https://www.xda-developers.com/risc-v-cpu-gpu-ai-one-core/" rel="nofollow noopener noreferrer" target="_blank">https://www.xda-developers.com/risc-v-cpu-gpu-ai-one-core/</a>

Jan Wildeboer 😷:krulorange:It's only an <a href="https://social.wildeboer.net/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</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">#OpenSource</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.

Foundation for Public CodeYour codebase can now claim a badge of commitment! We've launched a new badge to show a codebase's commitment to meeting the Standard for Public Code. Digg - The Authority for Digital Governance - is hosting two awesome codebase communities that are already using it. Read more about it on our blog: <a href="https://blog.publiccode.net/news/2023/09/12/standard-for-pubic-code-commitment-badge.html" rel="nofollow noopener noreferrer" target="_blank">https://blog.publiccode.net/news/2023/09/12/standard-for-pubic-code-commitment-badge.html</a> <a href="https://floss.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://floss.social/tags/openstandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openstandard</a>

narF 😵✌️This system should be an open standard, so that all existing contact book apps could implement it. Kinda like an updated version of CardDAV (<a href="https://en.wikipedia.org/wiki/CardDAV" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/CardDAV</a>).And ideally, all of that would be end-to-end encrypted, so that only your friends get to see your personal data. The host where you store your profile and your friends hosts should not be able to read your contact info!<a href="https://mstdn.ca/tags/CardDAV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CardDAV</a> <a href="https://mstdn.ca/tags/openStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openStandard</a> <a href="https://mstdn.ca/tags/FederatedIdentity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FederatedIdentity</a> <a href="https://mstdn.ca/tags/FederatedContactApp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FederatedContactApp</a> <a href="https://mstdn.ca/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> <a href="https://mstdn.ca/tags/E2EEncryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EEncryption</a> <a href="https://mstdn.ca/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://mstdn.ca/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a>

Jan Wildeboer 😷:krulorange: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">#OpenStandard</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

Jan Wildeboer 😷:krulorange:<a href="https://masto.ai/@danjac" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@danjac</a> <a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@smallcircles</a> <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@w3c</a> <a href="https://venera.social/profile/fedidevs" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fedidevs</a> <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Codeberg</a> <a href="https://mastodon.social/@dansup" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dansup</a> <a href="https://social.network.europa.eu/@EC_NGI" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@EC_NGI</a> <a href="https://social.network.europa.eu/@EC_DIGIT" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@EC_DIGIT</a> 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">#OpenStandard</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.

Brìghde<a href="https://mastodon.online/@thunderbird" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thunderbird</a> To me, open conveys that better than free. <a href="https://mastodon.scot/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> or as already suggested by someone <a href="https://mastodon.scot/tags/OpenInbox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenInbox</a>

LisPi<a href="https://social.engard.me/@michael" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@michael</a> <a href="https://mastodon.nzoss.nz/@lightweight" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lightweight</a> <a href="https://me.dm/@anildash" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@anildash</a> Yeah, this issue is one of the things <a href="https://mamot.fr/@pluralistic" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pluralistic</a> has written quite a bit about.In my country, refusing to work with any Microsoft-derived technology in IT will basically remove >70% of jobs, right from the get-go.We did get some good things out of M$'s laziness though, like the <a href="https://mastodon.top/tags/LSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LSP</a> & <a href="https://mastodon.top/tags/DAP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DAP</a> <a href="https://mastodon.top/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandard</a> <a href="https://mastodon.top/tags/protocols" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protocols</a>, which work just fine in <a href="https://mastodon.top/tags/Emacs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Emacs</a> (why VSC when you have Emacs?) and have greatly improved its ability to be used for <a href="https://mastodon.top/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> among other languages.

Recent searches

Search options

Administered by:

Server stats:

#openstandard