TechHub

InfoQDevelopers & contributors of the <a href="https://techhub.social/tags/ModelContextProtocol" class="mention hashtag" rel="tag">#ModelContextProtocol</a> gathered for the first developer summit!They charted the future of this rapidly adopted open standard, paving the way for seamless integration between LLM apps & external data sources and tools.Find out more: <a href="https://bit.ly/4m4JQ5O" target="_blank" rel="nofollow noopener" translate="no">https://bit.ly/4m4JQ5O</a> <a href="https://techhub.social/tags/InfoQ" class="mention hashtag" rel="tag">#InfoQ</a> <a href="https://techhub.social/tags/AI" class="mention hashtag" rel="tag">#AI</a> <a href="https://techhub.social/tags/LLMs" class="mention hashtag" rel="tag">#LLMs</a> <a href="https://techhub.social/tags/OpenStandard" class="mention hashtag" rel="tag">#OpenStandard</a>

Kevin Karhan :verified:<a href="https://mstdn.ca/@action_jay" class="u-url mention" rel="nofollow noopener" target="_blank">@action_jay</a> everything that isn't a fully <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>'d <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> with <a href="https://infosec.space/tags/MultiVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#MultiVendor</a> & <a href="https://infosec.space/tags/MultiProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#MultiProvider</a> support.That's why <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> (<a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME) & <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> / <a href="https://fosstodon.org/@gajim" class="u-url mention" rel="nofollow noopener" target="_blank">@gajim</a> (<a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a>) are superior to <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> , because that can be easily cracked down on due to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a>, whereas truly <a href="https://infosec.space/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralized</a> systems have <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> so they can't be taken down effectively.<ul><li>Bonus points if they support <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a>, cuz that makes it harder for "state-sponsored" (or rather state-endorsed/governmental attackers) to block or sabotage it (<a href="https://infosec.space/tags/OnionServices" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionServices</a> are harder to take down!)</li></ul>

Open Vulnerability Report🛡️ The OVR Foundation website is live! 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.🔧 Small updates will follow in the next few days. 🌍 Visit us: <a href="https://ovr-foundation.org" rel="nofollow noopener" translate="no" target="_blank">https://ovr-foundation.org</a> 🔗 <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://infosec.exchange/tags/OVR" class="mention hashtag" rel="nofollow noopener" target="_blank">#OVR</a> <a href="https://infosec.exchange/tags/Infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#Infosec</a> <a href="https://infosec.exchange/tags/Decentralization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Decentralization</a> <a href="https://infosec.exchange/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> <a href="https://infosec.exchange/tags/CVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE</a>

Grüne Kreisverband Stade<a href="https://gruene.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mastodon</a> im <a href="https://gruene.social/tags/Fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a> bietet dir einen Kurznachrichtendienst mit eingebauter Daten-Souveränität. „Deine <a href="https://gruene.social/tags/Nachrichten" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nachrichten</a> gehören dir und werden durch das Veröffentlichen nicht zum Eigentum eines Einzelnen, der damit reich wird.“Mastodon wurde in <a href="https://gruene.social/tags/Jena" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jena</a> in <a href="https://gruene.social/tags/Europa" class="mention hashtag" rel="nofollow noopener" target="_blank">#Europa</a> erfunden. Die Software und das Protokoll sind <a href="https://gruene.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> und <a href="https://gruene.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a>.<a href="https://gruene.social/@weddige" class="u-url mention" rel="nofollow noopener" target="_blank">@weddige</a> <a href="https://gruene.social/@kaibojens" class="u-url mention" rel="nofollow noopener" target="_blank">@kaibojens</a> <a href="https://mastodon.social/@Gargron" class="u-url mention" rel="nofollow noopener" target="_blank">@Gargron</a>

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

🧊 freezr 🥶Standard interchange image format for Open Source DTPHi people,with all the mayor GUI <a href="https://friendica.myportal.social/search?tag=DTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#DTP</a> software reaching their peak: <a href="https://friendica.myportal.social/search?tag=GIMP" class="mention hashtag" rel="nofollow noopener" target="_blank">#GIMP</a>, <a href="https://friendica.myportal.social/search?tag=Scribus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scribus</a> and <a href="https://friendica.myportal.social/search?tag=Inkscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#Inkscape</a>; and the well established <a href="https://friendica.myportal.social/search?tag=TeX" class="mention hashtag" rel="nofollow noopener" target="_blank">#TeX</a> software <a href="https://friendica.myportal.social/search?tag=ConTeXt" class="mention hashtag" rel="nofollow noopener" target="_blank">#ConTeXt</a> and <a href="https://friendica.myportal.social/search?tag=SpeedataPublisher" class="mention hashtag" rel="nofollow noopener" target="_blank">#SpeedataPublisher</a>, and <a href="https://friendica.myportal.social/search?tag=ImageMagick" class="mention hashtag" rel="nofollow noopener" target="_blank">#ImageMagick</a> we need a serious discussion about which image format we should adopt that works seamlessly across all these applications and it is generally accepted in the press workflow, whereas is embedded or not into a PDF file.It should be something that has good quality, supports <a href="https://friendica.myportal.social/search?tag=CMYK" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMYK</a> and Alpha channels and it is <a href="https://friendica.myportal.social/search?tag=opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> friendly and perhaps an <a href="https://friendica.myportal.social/search?tag=openstandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#openstandard</a>.I would dare to say that perhaps jpeg2000 matches most of them, it exists from a very long time and can be adopted as common ground, however it is need a combined effort, if what I am writing makes sense for you.ImageMagick supports it, Gimp 3 currently doesn't, <a href="https://friendica.myportal.social/search?tag=LuaTeX" class="mention hashtag" rel="nofollow noopener" target="_blank">#LuaTeX</a> and <a href="https://friendica.myportal.social/search?tag=LuaMetaTeX" class="mention hashtag" rel="nofollow noopener" target="_blank">#LuaMetaTeX</a> neither. I guess that Inkscape once it will be able to export in CMYK it will decide which format using to store images in CMYK with alpha into a PDF.It would be very beneficial if we can adopt a format that works everywhere and it is press friendly, thanks.

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

Hacker NewsOpen-UI: Maintain an open standard for UI and promote its adherence and adoption<a href="https://github.com/openui/open-ui" rel="nofollow noopener" translate="no" target="_blank">https://github.com/openui/open-ui</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/OpenUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenUI</a> <a href="https://mastodon.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> <a href="https://mastodon.social/tags/UIAdoption" class="mention hashtag" rel="nofollow noopener" target="_blank">#UIAdoption</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://mastodon.social/tags/TechCommunity" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechCommunity</a>

☮ ♥ ♬ 🧑‍💻What is the AT Protocol? Wikipedia: “The <a href="https://ioc.exchange/tags/ATProtocol" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#OpenStandard</a> for <a href="https://ioc.exchange/tags/distributed" class="mention hashtag" rel="nofollow noopener" target="_blank">#distributed</a> <a href="https://ioc.exchange/tags/socialNetworking" class="mention hashtag" rel="nofollow noopener" target="_blank">#socialNetworking</a> services. It is under development by <a href="https://ioc.exchange/tags/BlueskySocial" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlueskySocial</a> <a href="https://ioc.exchange/tags/PBC" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#Twitter</a> to investigate the possibility of <a href="https://ioc.exchange/tags/decentralizing" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralizing</a> the service.”<<a href="https://en.m.wikipedia.org/wiki/AT_Protocol" rel="nofollow noopener" translate="no" target="_blank">https://en.m.wikipedia.org/wiki/AT_Protocol</a>>

RomWent the VM route instead - spun a Windows VM and now am converting ebooks to ePub format. <a class="hashtag" href="https://bsky.app/search?q=%23FOSS" rel="nofollow noopener" target="_blank">#FOSS</a> <a class="hashtag" href="https://bsky.app/search?q=%23OpenStandard" rel="nofollow noopener" target="_blank">#OpenStandard</a> <a class="hashtag" href="https://bsky.app/search?q=%23xp" rel="nofollow noopener" target="_blank">#xp</a>

Amgine<a href="https://smores.town/@touk" class="u-url mention" rel="nofollow noopener" 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" target="_blank">#OpenSource</a> <a href="https://mamot.fr/tags/audio" class="mention hashtag" rel="nofollow noopener" target="_blank">#audio</a> <a href="https://mamot.fr/tags/streaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#streaming</a> platforms not default to the <a href="https://mamot.fr/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> file formats? <a href="https://mamot.fr/tags/petpeeve" class="mention hashtag" rel="nofollow noopener" target="_blank">#petpeeve</a> <a href="https://mamot.fr/tags/audiophile" class="mention hashtag" rel="nofollow noopener" 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" target="_blank" rel="nofollow noopener" translate="no">https://doi.org/10.3389/feart.2022.907614</a> <-- shared paper -- <a href="https://doi.org/10.5066/P9XNQVGQ" target="_blank" rel="nofollow noopener" translate="no">https://doi.org/10.5066/P9XNQVGQ</a> | <a href="https://code.usgs.gov/g3sc/gspy" target="_blank" rel="nofollow noopener" translate="no">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="tag">#GIS</a> <a href="https://techhub.social/tags/spatial" class="mention hashtag" rel="tag">#spatial</a> <a href="https://techhub.social/tags/mapping" class="mention hashtag" rel="tag">#mapping</a> <a href="https://techhub.social/tags/geophysics" class="mention hashtag" rel="tag">#geophysics</a> <a href="https://techhub.social/tags/geophysical" class="mention hashtag" rel="tag">#geophysical</a> <a href="https://techhub.social/tags/NetCDF" class="mention hashtag" rel="tag">#NetCDF</a> <a href="https://techhub.social/tags/datatypes" class="mention hashtag" rel="tag">#datatypes</a> <a href="https://techhub.social/tags/code" class="mention hashtag" rel="tag">#code</a> <a href="https://techhub.social/tags/opensource" class="mention hashtag" rel="tag">#opensource</a> <a href="https://techhub.social/tags/library" class="mention hashtag" rel="tag">#library</a> <a href="https://techhub.social/tags/dataformats" class="mention hashtag" rel="tag">#dataformats</a> <a href="https://techhub.social/tags/standardisation" class="mention hashtag" rel="tag">#standardisation</a> <a href="https://techhub.social/tags/standardization" class="mention hashtag" rel="tag">#standardization</a> <a href="https://techhub.social/tags/openstandard" class="mention hashtag" rel="tag">#openstandard</a> <a href="https://techhub.social/tags/portable" class="mention hashtag" rel="tag">#portable</a> <a href="https://techhub.social/tags/metadata" class="mention hashtag" rel="tag">#metadata</a> <a href="https://techhub.social/tags/Python" class="mention hashtag" rel="tag">#Python</a> <a href="https://techhub.social/tags/package" class="mention hashtag" rel="tag">#package</a> <a href="https://techhub.social/tags/GSPy" class="mention hashtag" rel="tag">#GSPy</a> <a href="https://techhub.social/tags/methods" class="mention hashtag" rel="tag">#methods</a> <a href="https://techhub.social/tags/workflows" class="mention hashtag" rel="tag">#workflows</a> <a href="https://techhub.social/tags/xarray" class="mention hashtag" rel="tag">#xarray</a> <a href="https://techhub.social/tags/CRS" class="mention hashtag" rel="tag">#CRS</a> <a href="https://techhub.social/tags/opendata" class="mention hashtag" rel="tag">#opendata</a> <a href="https://techhub.social/tags/architecture" class="mention hashtag" rel="tag">#architecture</a> <a href="https://techhub.social/tags/toolbox" class="mention hashtag" rel="tag">#toolbox</a>

Kevin Karhan :verified:<a href="https://mstdn.social/@stux" class="u-url mention" rel="nofollow noopener" target="_blank">@stux</a> yeah, cuz <a href="https://infosec.space/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener" target="_blank">#ActivityPub</a> as an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</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.<ul><li>Just like <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IRC</a>, <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a> & <a href="https://infosec.space/tags/eMail" class="mention hashtag" rel="nofollow noopener" target="_blank">#eMail</a> are...</li></ul>

just small circles 🕊"Show don't tell" of federate <a href="https://social.coop/tags/FOSS" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">#ActivityPub</a> <a href="https://social.coop/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a> installed base is known to only add <a href="https://social.coop/tags/ProtocolDecay" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProtocolDecay</a> and <a href="https://social.coop/tags/TechDebt" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechDebt</a>.In <a href="https://social.coop/tags/Commons" class="mention hashtag" rel="nofollow noopener" target="_blank">#Commons</a> <a href="https://social.coop/tags/CommonSense" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommonSense</a> makes <a href="https://social.coop/tags/CommonsSense" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommonsSense</a>: Don't introduce the opposite of <a href="https://social.coop/tags/interoperabily" class="mention hashtag" rel="nofollow noopener" target="_blank">#interoperabily</a> when in pursuit of seamless interop.We need both forms of showing.

Neustradamus :xmpp: :linux:Few days ago, it was the 26th Birthday of <a href="https://mastodon.social/tags/Jabber" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jabber</a>/#XMPP! It is the date of <a href="https://mastodon.social/tags/JeremieMiller" class="mention hashtag" rel="nofollow noopener" target="_blank">#JeremieMiller</a> announcement on <a href="https://mastodon.social/tags/Slashdot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Slashdot</a>! <a href="https://mastodon.social/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> <a href="https://mastodon.social/tags/InstantMessaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#InstantMessaging</a> <a href="https://mastodon.social/tags/RealTimeText" class="mention hashtag" rel="nofollow noopener" target="_blank">#RealTimeText</a> <a href="https://mastodon.social/tags/CommunicationProtocol" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunicationProtocol</a> <a href="https://mastodon.social/tags/IETF" class="mention hashtag" rel="nofollow noopener" target="_blank">#IETF</a> <a href="https://mastodon.social/tags/InternetEngineeringTaskForce" class="mention hashtag" rel="nofollow noopener" target="_blank">#InternetEngineeringTaskForce</a> <a href="https://slashdot.org/story/99/01/04/1621211/open-real-time-messaging-system" rel="nofollow noopener" translate="no" target="_blank">https://slashdot.org/story/99/01/04/1621211/open-real-time-messaging-system</a>

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" target="_blank">#standard</a> <a href="https://misp-community.org/tags/openstandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#openstandard</a> <a href="https://misp-community.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> <a href="https://misp-community.org/tags/misp" class="mention hashtag" rel="nofollow noopener" target="_blank">#misp</a> <a href="https://misp-community.org/tags/threatintelligence" class="mention hashtag" rel="nofollow noopener" target="_blank">#threatintelligence</a> <a href="https://misp-community.org/tags/threatintel" class="mention hashtag" rel="nofollow noopener" target="_blank">#threatintel</a> 🔗 <a href="https://www.misp-standard.org/blog/Naming-Threat-Actor/" rel="nofollow noopener" translate="no" target="_blank">https://www.misp-standard.org/blog/Naming-Threat-Actor/</a>

Kevin Karhan :verified:<a href="https://digipres.club/@foone" class="u-url mention" rel="nofollow noopener" target="_blank">@foone</a> needless to say I doubt anyone will actually ever implement a "<a href="https://infosec.space/tags/SecureUSB" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureUSB</a>" implementation even if it was an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> and doing so wouldn't even require <a href="https://infosec.space/tags/USB" class="mention hashtag" rel="nofollow noopener" target="_blank">#USB</a>-IF membership or anything.Ideally true <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> with proper keys would be implemented, but that would still have Trust Root Probems but worse than <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</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" 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" target="_blank">#openstandard</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.social/tags/mcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#mcp</a> <a href="https://mastodon.social/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://mastodon.social/tags/anthropic" class="mention hashtag" rel="nofollow noopener" target="_blank">#anthropic</a>

Kevin Karhan :verified:<a href="https://uwu.social/@koakuma" class="u-url mention" rel="nofollow noopener" target="_blank">@koakuma</a> <a href="https://woof.tech/@techokami" class="u-url mention" rel="nofollow noopener" target="_blank">@techokami</a> also <a href="https://infosec.space/tags/UltraSparcT2" class="mention hashtag" rel="nofollow noopener" target="_blank">#UltraSparcT2</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).<ul><li>Plus <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener" target="_blank">#RISCv</a> unlike <a href="https://infosec.space/tags/SPARCv9" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPARCv9</a> amd <a href="https://infosec.space/tags/OpenPOWER" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenPOWER</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" target="_blank">#RISC</a> & <a href="https://infosec.space/tags/CISC" class="mention hashtag" rel="nofollow noopener" target="_blank">#CISC</a> architectures and needed something <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> as they can't just violate NDAs nilly-willy for teaching.</li></ul>Pretty shure <a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener" target="_blank">@stman</a> could write an entire curriculum on why <a href="https://infosec.space/tags/SPARC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPARC</a>, <a href="https://infosec.space/tags/PowerPC" class="mention hashtag" rel="nofollow noopener" target="_blank">#PowerPC</a>, <a href="https://infosec.space/tags/s390x" class="mention hashtag" rel="nofollow noopener" target="_blank">#s390x</a> and even <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARM</a> / <a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARM64</a> should not be pursued and why <a href="https://infosec.space/tags/mc68k" class="mention hashtag" rel="nofollow noopener" target="_blank">#mc68k</a> died alongside the unfixable-by-design mess that is <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener" target="_blank">#ix86</a> & <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd64</a>.<ul><li>Plus RISCv's ISA has been an <a href="https://infosec.space/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> from the get go, whereas the efforts by <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oracle</a> nee <a href="https://infosec.space/tags/Sun" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sun</a> and <a href="https://infosec.space/tags/IBM" class="mention hashtag" rel="nofollow noopener" target="_blank">#IBM</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>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" target="_blank">#PiCluster</a> like those <a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener" target="_blank">@geerlingguy</a> had built multiple times are more practical.<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>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" target="_blank">#Pi5</a> they neither included a power button nor <a href="https://infosec.space/tags/RTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#RTC</a> onboard!<ul><li>OFC RISC-V is still 5-25+ years behind <a href="https://infosec.space/tags/ARMv9" class="mention hashtag" rel="nofollow noopener" target="_blank">#ARMv9</a> solely based off <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#patents</a>, <a href="https://infosec.space/tags/budget" class="mention hashtag" rel="nofollow noopener" target="_blank">#budget</a> and <a href="https://infosec.space/tags/PersonnelHours" class="mention hashtag" rel="nofollow noopener" target="_blank">#PersonnelHours</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>

Nico RikkenOn my way to <a href="https://mastodon.nl/tags/Shapeshifter" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shapeshifter</a> day: a community working session to improve this <a href="https://mastodon.nl/tags/OpenStandard" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandard</a> with corresponding <a href="https://mastodon.nl/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> libraries for <a href="https://mastodon.nl/tags/Energy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Energy</a> congestion markets. Looking forward to have fun with this great community. Of course I brought stickers! <a href="https://lfenergy.org/projects/shapeshifter/" rel="nofollow noopener" translate="no" target="_blank">https://lfenergy.org/projects/shapeshifter/</a> <a href="https://mastodon.nl/tags/LFEnergy" class="mention hashtag" rel="nofollow noopener" target="_blank">#LFEnergy</a>

Recent searches

Search options

Administered by:

Server stats:

#openstandard