MastodonTech.de

xoron :verified:Selhosted P2P E2EE File Transfer & Messaging PWA<a href="https://positive-intentions.com" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com</a> * <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> * <a href="https://infosec.exchange/tags/CrossPlatform" class="mention hashtag" rel="nofollow noopener" target="_blank">#CrossPlatform</a> * <a href="https://infosec.exchange/tags/PWA" class="mention hashtag" rel="nofollow noopener" target="_blank">#PWA</a> * <a href="https://infosec.exchange/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a>, <a href="https://infosec.exchange/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a>, <a href="https://infosec.exchange/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Desktop</a> (self compile) * App store, Play store (coming soon) * Desktop * <a href="https://infosec.exchange/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>, <a href="https://infosec.exchange/tags/MacOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacOS</a>, <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> (self compile) * run `index.html` on any modern <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> * <a href="https://infosec.exchange/tags/Decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#Decentralized</a> * <a href="https://infosec.exchange/tags/Secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#Secure</a> * <a href="https://infosec.exchange/tags/NoCookies" class="mention hashtag" rel="nofollow noopener" target="_blank">#NoCookies</a> * <a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#P2P</a> <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypted</a> * No registration * No installing * <a href="https://infosec.exchange/tags/Messaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#Messaging</a> * Group Messaging (coming soon) * Text Messaging * <a href="https://infosec.exchange/tags/Multimedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Multimedia</a> Messaging * <a href="https://infosec.exchange/tags/Screensharing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Screensharing</a> (on desktop browsers) * Offline Messaging (in <a href="https://infosec.exchange/tags/research" class="mention hashtag" rel="nofollow noopener" target="_blank">#research</a> phase) * <a href="https://infosec.exchange/tags/FileTransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileTransfer</a> * <a href="https://infosec.exchange/tags/VideoCalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#VideoCalls</a> * <a href="https://infosec.exchange/tags/DataOwnership" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataOwnership</a> * <a href="https://infosec.exchange/tags/SelfHosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosted</a> * GitHub pages Hosting * <a href="https://infosec.exchange/tags/LocalOnly" class="mention hashtag" rel="nofollow noopener" target="_blank">#LocalOnly</a> storageCheck them out!(Degoogled links to the apps) - P2P Chat: <a href="https://chat.positive-intentions.com" rel="nofollow noopener" translate="no" target="_blank">https://chat.positive-intentions.com</a> - P2P File: <a href="https://file.positive-intentions.com" rel="nofollow noopener" translate="no" target="_blank">https://file.positive-intentions.com</a> - Encrypted drive storage: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank">https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo</a>- GitHub: <a href="https://github.com/positive-intentions" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions</a>IMPORTANT NOTES (PLEASE READ!): * These are NOT products. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#demonstration</a> purposes only. * They have NOT been reviewed or audited. Do NOT use for sensitive data. * All functionality demonstrated is experimental. * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#VeraCrypt</a>, <a href="https://infosec.exchange/tags/Simplexchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#Simplexchat</a>, <a href="https://infosec.exchange/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a>, <a href="https://infosec.exchange/tags/Whatsapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#Whatsapp</a>, <a href="https://infosec.exchange/tags/wetransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#wetransfer</a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a>.(Boosts appreciated)

xoron :verified:File encryption with a browser.I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebCryptoAPI</a> and I'm impressed!When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystemAPI</a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypt</a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener" target="_blank">#store</a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#localstorage</a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a>!I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapps</a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> vulnerabilities since the code is served over the web, so I've <a href="https://infosec.exchange/tags/OpenSourced" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSourced</a> my demo! You can check it out, and it should even work if <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubPages</a>.Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank">https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo</a>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</a>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js</a>IMPORTANT NOTES (PLEASE READ!): * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#demonstration</a> purposes only. * It has NOT been reviewed or audited. Do NOT use for sensitive data. * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security. * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#VeraCrypt</a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a>.<a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cryptography</a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Developer</a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastodonDev</a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebAPI</a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a>

xoron :verified:React-like functional webcomponents, but with vanilla HTML, JS and CSSIntroducing Dim – a new <a href="https://infosec.exchange/tags/Framework" class="mention hashtag" rel="nofollow noopener" target="_blank">#Framework</a> that brings <a href="https://infosec.exchange/tags/ReactJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReactJS</a>-like functional <a href="https://infosec.exchange/tags/JSX" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSX</a>-syntax with <a href="https://infosec.exchange/tags/VanillaJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VanillaJS</a>. Check it out here: 🔗 Project: <a href="https://github.com/positive-intentions/dim" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim</a> 🔗 Website: <a href="https://dim.positive-intentions.com" rel="nofollow noopener" translate="no" target="_blank">https://dim.positive-intentions.com</a>My journey with <a href="https://infosec.exchange/tags/WebComponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebComponents</a> started with Lit, and while I appreciated its native browser support (less <a href="https://infosec.exchange/tags/Tooling" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tooling</a>!), coming from <a href="https://infosec.exchange/tags/ReactJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReactJS</a>, the class components felt like a step backward. The <a href="https://infosec.exchange/tags/FunctionalProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#FunctionalProgramming</a> approach in React significantly improved my <a href="https://infosec.exchange/tags/DeveloperExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeveloperExperience</a> and debugging flow.So, I set out to build a thin, functional wrapper around <a href="https://infosec.exchange/tags/Lit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lit</a>, and Dim is the result! It's a <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> right now, with "main" <a href="https://infosec.exchange/tags/Hooks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hooks</a> similar to React, plus some custom ones like useStore for <a href="https://infosec.exchange/tags/EncryptionAtRest" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncryptionAtRest</a>. (Note: <a href="https://infosec.exchange/tags/StateManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#StateManagement</a> for encryption-at-rest is still unstable and currently uses a hardcoded password while I explore <a href="https://infosec.exchange/tags/Passwordless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Passwordless</a> options like <a href="https://infosec.exchange/tags/WebAuthn" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebAuthn</a>/#Passkeys).You can dive deeper into the <a href="https://infosec.exchange/tags/Documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Documentation</a> and see how it works here: 📚 Dim Docs: <a href="https://positive-intentions.com/docs/category/dim" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/docs/category/dim</a>This <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> project is still in its early stages and very <a href="https://infosec.exchange/tags/Unstable" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unstable</a>, so expect <a href="https://infosec.exchange/tags/BreakingChanges" class="mention hashtag" rel="nofollow noopener" target="_blank">#BreakingChanges</a>. I've already received valuable <a href="https://infosec.exchange/tags/Feedback" class="mention hashtag" rel="nofollow noopener" target="_blank">#Feedback</a> on some functions regarding <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a>, and I'm actively investigating those. I'm genuinely open to all feedback as I continue to develop it!<a href="https://infosec.exchange/tags/FrontendDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#FrontendDev</a> <a href="https://infosec.exchange/tags/JSFramework" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSFramework</a> <a href="https://infosec.exchange/tags/Innovation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Innovation</a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://infosec.exchange/tags/Programmer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programmer</a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@mrgrumpymonkey" class="u-url mention" rel="nofollow noopener" target="_blank">@mrgrumpymonkey</a> it is.One can repartition Windows installations on the fly whilst running (and even then there are tools like <a href="https://infosec.space/tags/Wubi" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wubi</a> that made it easy to setup <a href="https://infosec.space/tags/dualboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#dualboot</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> & <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>.<ul><li>ISOLINUX does allow for "load image into RAM and boot" setups. I literally use that on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> because no system that can boot it will have > 16 MB RAM anyway ( 8 MB is the hard limit for bare linux kernel) so merely making Windows' bootloader to chainload <a href="https://infosec.space/tags/isolinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#isolinux</a> to load that image in RAM and yeet it isn't out of the question.</li></ul>I just have neither a <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> machine nor time and spoons to make such a tool, much less to basically create even said <a href="https://infosec.space/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> "<a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a>"…<ul><li>But thanks to <a href="https://infosec.space/tags/GoldenKeyBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoldenKeyBoot</a>, <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> is unfixably insecure!</li></ul>

Matasoft🧪 Not sure if AI-powered spreadsheets are right for you? Start with a proof of concept! Download (Un)Perplexed Spready, request a free evaluation period, and test it on your actual data challenges. See the transformation firsthand before committing! 🔍 <a href="https://mstdn.business/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> <a href="https://mstdn.business/tags/TryBeforeBuy" class="mention hashtag" rel="nofollow noopener" target="_blank">#TryBeforeBuy</a> <a href="https://matasoft.hr/qtrendcontrol/index.php/un-perplexed-spready/un-perplexed-spready-download" rel="nofollow noopener" translate="no" target="_blank">https://matasoft.hr/qtrendcontrol/index.php/un-perplexed-spready/un-perplexed-spready-download</a>

Hacker NewsA proof of concept tool to verify estimates<a href="https://terrytao.wordpress.com/2025/05/01/a-proof-of-concept-tool-to-verify-estimates/" rel="nofollow noopener" translate="no" target="_blank">https://terrytao.wordpress.com/2025/05/01/a-proof-of-concept-tool-to-verify-estimates/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/proofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofOfConcept</a> <a href="https://mastodon.social/tags/toolVerification" class="mention hashtag" rel="nofollow noopener" target="_blank">#toolVerification</a> <a href="https://mastodon.social/tags/estimates" class="mention hashtag" rel="nofollow noopener" target="_blank">#estimates</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/techInnovation" class="mention hashtag" rel="nofollow noopener" target="_blank">#techInnovation</a>

Su_G<a href="https://sauropods.win/@futurebird" class="u-url mention" rel="nofollow noopener" target="_blank">@futurebird</a> You've convinced me! Bringing back extinct lichen is a great way to do proof of concept for bringing back extinct organisms, 🙂 <a href="https://aus.social/tags/proofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofOfConcept</a> <a href="https://aus.social/tags/lichen" class="mention hashtag" rel="nofollow noopener" target="_blank">#lichen</a> <a href="https://aus.social/tags/Extinct" class="mention hashtag" rel="nofollow noopener" target="_blank">#Extinct</a>

OlafDas Schicksal der <a href="https://mastodontech.de/tags/Nische" class="mention hashtag" rel="tag">#Nische</a>: Außerhalb der Blase kommt man "zu spät" und "zu kurz" vor. Der Hashtag <a href="https://mastodontech.de/tags/raum2" class="mention hashtag" rel="tag">#raum2</a> bietet in diesem Fall mehr Bildmaterial ohne Mehraufwand für den <a href="https://mastodontech.de/tags/lokalreporter" class="mention hashtag" rel="tag">#lokalreporter</a>. <a href="https://mastodontech.de/tags/proofofconcept" class="mention hashtag" rel="tag">#proofofconcept</a> From: <a href="https://zeitung.social/@ejz" class="u-url mention">@ejz</a> <a href="https://zeitung.social/@ejz/114189317736814950" target="_blank" rel="nofollow noopener" translate="no">https://zeitung.social/@ejz/114189317736814950</a>

Kevin Veen-Birkenbach💡 Today, I built a Proof of Concept: a dynamic cryptocurrency miner! The idea was to use idle hardware resources to mine crypto. 🖥️💰BUT... after some testing, I realized it's not worth it in Germany due to high energy costs ⚡ and low crypto prices 📉.Check it out here (but I don’t recommend using it 😉): <a href="https://github.com/kevinveenbirkenbach/dynamic-miner" rel="nofollow noopener" translate="no" target="_blank">https://github.com/kevinveenbirkenbach/dynamic-miner</a><a href="https://microblog.veen.world/tags/CryptoMining" class="mention hashtag" rel="nofollow noopener" target="_blank">#CryptoMining</a> <a href="https://microblog.veen.world/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> <a href="https://microblog.veen.world/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://microblog.veen.world/tags/TechExperiments" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechExperiments</a> <a href="https://microblog.veen.world/tags/DynamicMiner" class="mention hashtag" rel="nofollow noopener" target="_blank">#DynamicMiner</a> <a href="https://microblog.veen.world/tags/EnergyCosts" class="mention hashtag" rel="nofollow noopener" target="_blank">#EnergyCosts</a> <a href="https://microblog.veen.world/tags/CryptoPrices" class="mention hashtag" rel="nofollow noopener" target="_blank">#CryptoPrices</a> <a href="https://microblog.veen.world/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> <a href="https://microblog.veen.world/tags/ETC" class="mention hashtag" rel="nofollow noopener" target="_blank">#ETC</a> <a href="https://microblog.veen.world/tags/BTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#BTC</a> <a href="https://microblog.veen.world/tags/Bitcoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bitcoin</a> <a href="https://microblog.veen.world/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://microblog.veen.world/tags/Currency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Currency</a> <a href="https://microblog.veen.world/tags/Crypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#Crypto</a>

xoron :verified:id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.<a href="https://github.com/positive-intentions/chat" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/chat</a><a href="https://positive-intentions.com/blog/introducing-decentralized-chat" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/blog/introducing-decentralized-chat</a>im not an expert on <a href="https://infosec.exchange/tags/cyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberSecurity</a>. im sure there are many gaps in my knowlege in this domain.using <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>, i initially created a fairly basic <a href="https://infosec.exchange/tags/chatApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#chatApp</a> using using <a href="https://infosec.exchange/tags/peerjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#peerjs</a> to create <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypted</a> <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#webrtc</a> <a href="https://infosec.exchange/tags/connections" class="mention hashtag" rel="nofollow noopener" target="_blank">#connections</a>. this was then easily enhanced by exchanging additional <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a> <a href="https://infosec.exchange/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#keys</a> from <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> functions built into browsers (<a href="https://infosec.exchange/tags/webcrypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcrypto</a> api) to add a redundent layer of encryption. a <a href="https://infosec.exchange/tags/diffieHelman" class="mention hashtag" rel="nofollow noopener" target="_blank">#diffieHelman</a> key <a href="https://infosec.exchange/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#exchange</a> is done over <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#webrtc</a> (which can be considered <a href="https://infosec.exchange/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#secure</a> when exchanged over public channels) to create <a href="https://infosec.exchange/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> <a href="https://infosec.exchange/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a>.- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have <a href="https://infosec.exchange/tags/openedSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#openedSource</a> my <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> module. its basically a thin wrapper around vanilla cryptography functions of a <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> (webcrypto api).- another concern for my kind of app (<a href="https://infosec.exchange/tags/PWA" class="mention hashtag" rel="nofollow noopener" target="_blank">#PWA</a>) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a>. selhosting this app has some unique features. unlike many other <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://infosec.exchange/tags/projects" class="mention hashtag" rel="nofollow noopener" target="_blank">#projects</a>, this app can be hosted on <a href="https://infosec.exchange/tags/githubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#githubPages</a> (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.- to prevent things like browser extensions, the app uses strict <a href="https://infosec.exchange/tags/CSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSP</a> headers to prevent <a href="https://infosec.exchange/tags/unauthorised" class="mention hashtag" rel="nofollow noopener" target="_blank">#unauthorised</a> code from running. <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> users should take note of this when setting up their own instance.- i received feedback the <a href="https://infosec.exchange/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a>/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the <a href="https://infosec.exchange/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#complexity</a> by working with <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#webrtc</a>. while it has its many flaws, i think risks can be reasonable mitigated if the <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> functions are implemented correctly. (all data out is <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypted</a> and all data in is <a href="https://infosec.exchange/tags/decrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#decrypted</a> on-the-fly)- the key detail that makes this approach unique, is because as a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapp</a>, unlike other solutions, users have a choice of using any <a href="https://infosec.exchange/tags/device" class="mention hashtag" rel="nofollow noopener" target="_blank">#device</a>/#os/#browser. while a webapp can have nuanced <a href="https://infosec.exchange/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerabilities</a>, i think by <a href="https://infosec.exchange/tags/openSourcing" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSourcing</a> and providing instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> and instructions to <a href="https://infosec.exchange/tags/build" class="mention hashtag" rel="nofollow noopener" target="_blank">#build</a> for various <a href="https://infosec.exchange/tags/platforms" class="mention hashtag" rel="nofollow noopener" target="_blank">#platforms</a>, it can provide a reasonable level of <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>.i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> and the peerjs-server to be <a href="https://infosec.exchange/tags/hosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#hosted</a> <a href="https://infosec.exchange/tags/independently" class="mention hashtag" rel="nofollow noopener" target="_blank">#independently</a>, im on track for creating a <a href="https://infosec.exchange/tags/chatSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#chatSystem</a> with the "fewest moving parts". i hope you will agree this is true <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> and i hope i can use this as a step towards true <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> and <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>. <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> might be further improved by using a trusted <a href="https://infosec.exchange/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a>.while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find <a href="https://infosec.exchange/tags/bestPractices" class="mention hashtag" rel="nofollow noopener" target="_blank">#bestPractices</a> for the functionalities i want to achieve. in particular <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> practices to use when using <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> technology.(note: this app is an <a href="https://infosec.exchange/tags/unstable" class="mention hashtag" rel="nofollow noopener" target="_blank">#unstable</a>, <a href="https://infosec.exchange/tags/experiment" class="mention hashtag" rel="nofollow noopener" target="_blank">#experiment</a>, <a href="https://infosec.exchange/tags/proofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofOfConcept</a> and not ready to replace any other app or service. It's far from finished and provided for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demo" class="mention hashtag" rel="nofollow noopener" target="_blank">#demo</a> purposes only. This post is to get <a href="https://infosec.exchange/tags/feedback" class="mention hashtag" rel="nofollow noopener" target="_blank">#feedback</a> on the progress to determine if i'm going in the right direction for a secure chat app)

Matteo Bilotta :fediverso:Il progetto -mentre scrivo- è in stato embrionale; con scarso qualcosa di visibile a schermo.MA... Mi sono già occupato di una prima fase di analisi, ho esplorato qualche approccio implementativo e ho realizzato un paio di <a href="https://mastodon.uno/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> differenti. Molte delle scelte progettuali e tecnologiche -quindi- sono state fatte.Userò i prossimi giorni per portare in pari il resoconto con lo stato attuale del progetto, pubblicando una serie di post dietro l'altro.Allacciare le cinture! Si parte! 🚂

Tino Eberl<a href="https://mastodon.online/tags/KINews" class="mention hashtag" rel="nofollow noopener" target="_blank">#KINews</a><a href="https://mastodon.online/tags/Gartner" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gartner</a> prognostiziert, dass 30 % der generativen <a href="https://mastodon.online/tags/KIProjekte" class="mention hashtag" rel="nofollow noopener" target="_blank">#KIProjekte</a> nach dem <a href="https://mastodon.online/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a> (PoC) abgebrochen werden. Aber das ist nicht unbedingt schlecht: Ein <a href="https://mastodon.online/tags/PoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#PoC</a> ermöglicht es Unternehmen, <a href="https://mastodon.online/tags/Risiken" class="mention hashtag" rel="nofollow noopener" target="_blank">#Risiken</a> und <a href="https://mastodon.online/tags/Machbarkeit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Machbarkeit</a> frühzeitig zu bewerten, <a href="https://mastodon.online/tags/Kosten" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kosten</a> zu sparen und wertvolle Erfahrungen zu sammeln. So lassen sich ineffiziente Projekte stoppen, bevor sie teurer werden. Fazit: Ausprobieren lohnt sich und Abbrechen ist manchmal der bessere Weg. <a href="https://mastodon.online/tags/KI" class="mention hashtag" rel="nofollow noopener" target="_blank">#KI</a> <a href="https://mastodon.online/tags/Projektmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#Projektmanagement</a><a href="https://tino-eberl.de/ki-news/gartner-30-der-ki-projekte-werden-nach-poc-abgebrochen-ja-gut-so/" rel="nofollow noopener" translate="no" target="_blank">https://tino-eberl.de/ki-news/gartner-30-der-ki-projekte-werden-nach-poc-abgebrochen-ja-gut-so/</a>

scops<a href="https://social.panic.com/@panic" class="u-url mention" rel="nofollow noopener" target="_blank">@panic</a> <a href="https://social.tchncs.de/tags/Audion" class="mention hashtag" rel="nofollow noopener" target="_blank">#Audion</a> (Viewer) as <a href="https://social.tchncs.de/tags/AppleMusic" class="mention hashtag" rel="nofollow noopener" target="_blank">#AppleMusic</a> controller is just awesome!There is a github repo with some basic changes need to do to make it work: <a href="https://github.com/zydeco/audion/tree/applescript" rel="nofollow noopener" translate="no" target="_blank">https://github.com/zydeco/audion/tree/applescript</a>I build my self a version based on the lastest sources (<a href="https://gitlab.com/panicinc/audion" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/panicinc/audion</a>).Sadly there are a few bugs. For example: - The scrolling song title breaks out - The interface settings dialog doesn’t work - it’s just a placeholder<a href="https://social.tchncs.de/tags/mp3player" class="mention hashtag" rel="nofollow noopener" target="_blank">#mp3player</a> <a href="https://social.tchncs.de/tags/musicplayer" class="mention hashtag" rel="nofollow noopener" target="_blank">#musicplayer</a> <a href="https://social.tchncs.de/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> <a href="https://social.tchncs.de/tags/retro" class="mention hashtag" rel="nofollow noopener" target="_blank">#retro</a> <a href="https://social.tchncs.de/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Kevin Karhan :verified:<a href="https://tilde.zone/@lunch" class="u-url mention" rel="nofollow noopener" target="_blank">@lunch</a> So you just admitted that you vomitted <a href="https://infosec.space/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUD</a> into my mentions without evidence?If you're so smart, then why don't you sell your <a href="https://infosec.space/tags/exploit" class="mention hashtag" rel="nofollow noopener" target="_blank">#exploit</a> / <a href="https://infosec.space/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> / <a href="https://infosec.space/tags/Whitepaper" class="mention hashtag" rel="nofollow noopener" target="_blank">#Whitepaper</a> to the highest bidder?<ul><li>I'm shure <a href="https://infosec.space/tags/Zerodium" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zerodium</a> and all the LEAs would try to outbid each other...</li></ul>Alas, your messages are just hot air, and not substantiated by anything...At best your info is <a href="https://www.youtube.com/watch?v=-3BF_mE2e6M" rel="nofollow noopener" target="_blank">2+ years outdated</a>...

OlafKann <a href="https://fediworld.de/tags/Sharkey" rel="nofollow noopener" target="_blank">#Sharkey</a> auch <a href="https://fediworld.de/tags/Video" rel="nofollow noopener" target="_blank">#Video</a>? <a href="https://fediworld.de/tags/proofofconcept" rel="nofollow noopener" target="_blank">#proofofconcept</a> In dem Zusammenhang etwas Background: Ich habe mit dem Besitzer des Autos eine Stunde vor dem Teil gestanden - das hat seit 1957 80346 km auf der Uhr ("erste Umdrehung!"), braucht 10 ltr/100km und hat 45 PS. Damals war das der "Mercedes des kleinen Mannes". (Mädels fuhren brav damals auf dem Beifahrersitz) Der Artikel erscheint morgen in der Zeitung und unsere fu**ing Website ist nicht in der Lage, hochformatige Videos einzubinden. "Aber das ist doch sowieso für Instagram...!" - Ja, klar! Aber die Menschen, die sich an solche Autos eher erinnern nicht! Und die Verweildauer auf einem Reel ist ... fünf Sekunden? #zielgruppe #medien #mediengestaltung

Crypto NewsStarknet Foundation launches $5 million grants program - The funding aims to help developers with final-stage blockchain projects... - <a href="https://cointelegraph.com/news/starknet-foundation-5m-grant-program" rel="nofollow noopener" translate="no" target="_blank">https://cointelegraph.com/news/starknet-foundation-5m-grant-program</a> #$5millionseedgrantsprogram <a href="https://schleuss.online/tags/decentralizedapplications" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralizedapplications</a> <a href="https://schleuss.online/tags/blockchaininnovation" class="mention hashtag" rel="nofollow noopener" target="_blank">#blockchaininnovation</a> <a href="https://schleuss.online/tags/starknetfoundation" class="mention hashtag" rel="nofollow noopener" target="_blank">#starknetfoundation</a> <a href="https://schleuss.online/tags/starknetdevelopers" class="mention hashtag" rel="nofollow noopener" target="_blank">#starknetdevelopers</a> <a href="https://schleuss.online/tags/emergingprojects" class="mention hashtag" rel="nofollow noopener" target="_blank">#emergingprojects</a> <a href="https://schleuss.online/tags/blockchaingaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#blockchaingaming</a> <a href="https://schleuss.online/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> <a href="https://schleuss.online/tags/usdc" class="mention hashtag" rel="nofollow noopener" target="_blank">#usdc</a> <a href="https://schleuss.online/tags/mvp" class="mention hashtag" rel="nofollow noopener" target="_blank">#mvp</a> <a href="https://schleuss.online/tags/nft" class="mention hashtag" rel="nofollow noopener" target="_blank">#nft</a>

Matt WillemsenScientists say they can cut HIV out of cells <a href="https://www.bbc.com/news/health-68609297" rel="nofollow noopener" translate="no" target="_blank">https://www.bbc.com/news/health-68609297</a> <a href="https://mastodon.social/tags/health" class="mention hashtag" rel="nofollow noopener" target="_blank">#health</a> <a href="https://mastodon.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a> <a href="https://mastodon.social/tags/CRISPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#CRISPR</a> <a href="https://mastodon.social/tags/gene" class="mention hashtag" rel="nofollow noopener" target="_blank">#gene</a>—editing <a href="https://mastodon.social/tags/HIV" class="mention hashtag" rel="nofollow noopener" target="_blank">#HIV</a> <a href="https://mastodon.social/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a>

Stefan BohacekA little proof of concept showing the GrapesJS page builder integrated with Glitch via a browser extension.<a href="https://stefanbohacek.online/tags/demo" class="mention hashtag" rel="nofollow noopener" target="_blank">#demo</a> <a href="https://stefanbohacek.online/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> <a href="https://stefanbohacek.online/tags/glitch" class="mention hashtag" rel="nofollow noopener" target="_blank">#glitch</a> <a href="https://stefanbohacek.online/tags/MadeWithGlitch" class="mention hashtag" rel="nofollow noopener" target="_blank">#MadeWithGlitch</a>

Simon Walters<a href="https://fosstodon.org/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> Following a chat with <a href="https://fosstodon.org/@moenig" class="u-url mention" rel="nofollow noopener" target="_blank">@moenig</a> at <a href="https://fosstodon.org/tags/FOSDEM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSDEM</a> Sending out a <a href="https://fosstodon.org/tags/NodeRED" class="mention hashtag" rel="nofollow noopener" target="_blank">#NodeRED</a> message to <a href="https://fosstodon.org/@SnapCloud" class="u-url mention" rel="nofollow noopener" target="_blank">@SnapCloud</a> via <a href="https://fosstodon.org/tags/MQTT" class="mention hashtag" rel="nofollow noopener" target="_blank">#MQTT</a> - modifiying it and then returning it back to NodeRED

Tarnkappe.info📬 LeftoverLocals: Apple, AMD und Qualcomm GPUs von Sicherheitslücke betroffen <a href="https://social.tchncs.de/tags/ITSicherheit" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITSicherheit</a> <a href="https://social.tchncs.de/tags/AMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#AMD</a> <a href="https://social.tchncs.de/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> <a href="https://social.tchncs.de/tags/CPUs" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPUs</a> <a href="https://social.tchncs.de/tags/HeidyKhlaaf" class="mention hashtag" rel="nofollow noopener" target="_blank">#HeidyKhlaaf</a> <a href="https://social.tchncs.de/tags/LeftoverLocals" class="mention hashtag" rel="nofollow noopener" target="_blank">#LeftoverLocals</a> <a href="https://social.tchncs.de/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a> <a href="https://social.tchncs.de/tags/Qualcomm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Qualcomm</a> <a href="https://social.tchncs.de/tags/Sicherheitsl%C3%BCcke" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheitslücke</a> <a href="https://social.tchncs.de/tags/TrailofBits" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrailofBits</a> <a href="https://sc.tarnkappe.info/af0398" rel="nofollow noopener" translate="no" target="_blank">https://sc.tarnkappe.info/af0398</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#Proofofconcept