Lorenzo Miniero<p>Aaaahhh is it the 10th of August already? 😱<br>See you later at 7pm Italy time for some live music, streamed via <a href="https://fosstodon.org/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a> because why not?</p><p><a href="https://music.lminiero.it/live/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">music.lminiero.it/live/</span><span class="invisible"></span></a></p>
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.
Administered by:
Server stats:
261active users
shakedown.social: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.3
#webrtc
2 posts · 2 participants · 0 posts today
Debacle<p><span class="h-card" translate="no"><a href="https://chaos.social/@ge0rg" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ge0rg</span></a></span> <span class="h-card" translate="no"><a href="https://retro.social/@ifixcoinops" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ifixcoinops</span></a></span> <span class="h-card" translate="no"><a href="https://timeloop.cafe/@alienghic" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>alienghic</span></a></span></p><p>XMPP is pronounced 'ʤæb.əʳ 🙂</p><p>To me,<br><a href="https://framapiaf.org/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a> is the universal communication protocol, used for <a href="https://framapiaf.org/tags/IoT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IoT</span></a>, <a href="https://framapiaf.org/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>, gaming, social, and <a href="https://framapiaf.org/tags/instantMessaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>instantMessaging</span></a>.<br><a href="https://framapiaf.org/tags/Jabber" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Jabber</span></a> is the latter in an open and federated network.<br><a href="https://framapiaf.org/tags/CiscoJabber" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CiscoJabber</span></a>™ is a product by Cisco.<br>Zimpy is many things, but don't look it up in <a href="https://framapiaf.org/tags/UrbanDictionary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UrbanDictionary</span></a>!</p><p>(Btw. I fiercely advocate naming <a href="https://framapiaf.org/tags/freeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freeSoftware</span></a> projects, children, cats, companies, everything, after <a href="https://framapiaf.org/tags/UUID" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UUID</span></a>s. No more unambiguousness, no more <a href="https://framapiaf.org/tags/trademark" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>trademark</span></a> issues.)</p>
xoron :verified:<p>An <a href="https://infosec.exchange/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>E2EE</span></a> messaging app unaffected by <a href="https://infosec.exchange/tags/ChatControl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ChatControl</span></a></p><p>* App: <a href="https://chat.positive-intentions.com/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">chat.positive-intentions.com/</span><span class="invisible"></span></a><br>* Code: <a href="https://github.com/positive-intentions/chat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/chat</span></a><br>* Reddit: <a href="https://www.reddit.com/r/positive_intentions" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">reddit.com/r/positive_intentio</span><span class="invisible">ns</span></a></p><p>How it works: <a href="https://positive-intentions.com/docs/projects/chat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/docs/p</span><span class="invisible">rojects/chat</span></a></p><p>TLDR: I'm working on a <a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> messaging <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapp</span></a>. Webapps are generally not considered secure because of the nature of serving statics over the internet. This is correct, but not a limitation of this project. (<a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosting</span></a> options: <a href="https://positive-intentions.com/blog/docker-ios-android-desktop" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/blog/d</span><span class="invisible">ocker-ios-android-desktop</span></a>).</p><p>As a webapp, I can provide the app with zero-installation and no-registration. The app is only using (local-only) browser storage (specifically <a href="https://infosec.exchange/tags/indexedDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>indexedDB</span></a>). So in a P2P interaction, the traditional concept of "the cloud" is just the physical devices connected over <a href="https://infosec.exchange/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>. This allows for things like P2P authentication: <a href="https://positive-intentions.com/blog/security-privacy-authentication" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/blog/s</span><span class="invisible">ecurity-privacy-authentication</span></a>.</p><p>Future:<br>I'm aiming to create the most secure messaging app out there... (more than <a href="https://infosec.exchange/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a>, <a href="https://infosec.exchange/tags/Simplex" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Simplex</span></a>, <a href="https://infosec.exchange/tags/threema" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>threema</span></a>, <a href="https://infosec.exchange/tags/session" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>session</span></a>, <a href="https://infosec.exchange/tags/deltachat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deltachat</span></a>, <a href="https://infosec.exchange/tags/bitchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bitchat</span></a>, etc). I know I have a long way to go to get there. The UI is fairly ugly for the average user, but I think the mechanics are working as expected. I think <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a> is underrated in what you can do with it. I'm actively investigating improving the <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> approach further to align to how the Signal protocol works (currently using a <a href="https://infosec.exchange/tags/DiffieHellman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DiffieHellman</span></a> key-exchange).</p><p>Support:<br>In the age of <a href="https://infosec.exchange/tags/ChatControl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ChatControl</span></a>, I would like to keep this project <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a>, but open-source funding is not working for me. I don't want your donations (but don't let that stop you) because it isn't sustainable for a long-term project. I have so far only experienced grant-funding rejections. I have no idea what I'm doing in trying to get funding for this project, so any support/advice is appreciated. In recognition of the project in its current state not being able to get funding... (sorry) I will have to go <a href="https://infosec.exchange/tags/closedsource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>closedsource</span></a> (which I'd like to avoid because it undermines several <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a> claims I'd like to make). I don't accept collaboration on the project because this would make tough decisions like going closed-source also immoral.</p><p><a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://infosec.exchange/tags/messaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>messaging</span></a> <a href="https://infosec.exchange/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>decentralized</span></a> <a href="https://infosec.exchange/tags/peer2peer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>peer2peer</span></a> <a href="https://infosec.exchange/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://infosec.exchange/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tech</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developer</span></a> <a href="https://infosec.exchange/tags/funding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>funding</span></a> <a href="https://infosec.exchange/tags/startup" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>startup</span></a></p>
Björn Schießle :europa:<p><span class="h-card" translate="no"><a href="https://front-end.social/@jensimmons" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jensimmons</span></a></span> I would wish, that Apple contributes their WebRTC implementation for WebKit upstream to the Open Source project so that Gnome Web and other Free Software web browser would finally support WebRTC.</p><p><a href="https://social.schiessle.eu/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> <a href="https://social.schiessle.eu/tags/Webkit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Webkit</span></a> <a href="https://social.schiessle.eu/tags/Webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Webrtc</span></a> <a href="https://social.schiessle.eu/tags/Gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gnome</span></a></p>
xoron :verified:<p><a href="https://glitr.io" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">glitr.io</span><span class="invisible"></span></a></p><p>im looking for feedback on my project.</p><p>IMPORTANT NOTES (PLEASE READ!):<br>* this is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>testing</span></a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>demonstration</span></a> purposes only.<br>* It has NOT been reviewed or audited. Do NOT use for sensitive data.<br>* All functionality demonstrated is experimental.<br>* This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/magicwormhole" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>magicwormhole</span></a> </p><p><a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>p2p</span></a> <a href="https://infosec.exchange/tags/e2ee" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>e2ee</span></a> <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encrypted</span></a> <a href="https://infosec.exchange/tags/pwa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pwa</span></a> <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a> <a href="https://infosec.exchange/tags/filetransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filetransfer</span></a> <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a> <a href="https://infosec.exchange/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>secure</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cybersecurity</span></a></p>
Marcel Waldvogel 🔜 WHY<p>Both <a href="https://waldvogel.family/tags/Yandex" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Yandex</span></a> and <a href="https://waldvogel.family/tags/Meta" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Meta</span></a> used obfuscation techniques to hide that the traffic occured and/or that the apps were listening to these requests:</p><p>➡️ Meta traffic was using <a href="https://waldvogel.family/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>, which does not show up in the browser's developer tools<br>➡️ Yandex traffic looked non-local<br>➡️ Yandex apps started listening only after several days</p><p>BTW: Apparently, Meta stopped doing this yesterday. But they probably still have the mapping DB.<br>All the details by the researchers here.<br><a href="https://localmess.github.io/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">localmess.github.io/</span><span class="invisible"></span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@ip6li" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ip6li</span></a></span> habe grade auch nen Interview abgelehnt, weil <a href="https://infosec.space/tags/MicrosoftTeams" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MicrosoftTeams</span></a> geb' ich mir nicht!</p><ul><li>Ist ja nicht so als hätte ich denen gleich mehrere Alternativen angeboten von <a href="https://infosec.space/tags/SIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIP</span></a> (<a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VoIP</span></a>) über <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a> (<a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCall</span></a>) und hätte im Bedarfsfalle sogar nen eigenen <a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JitsiMeet</span></a>-Server aufgesetzt...</li></ul>
xoron :verified:<p>Send files privately. No cloud. No trace.</p><p><a href="https://glitr.io" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">glitr.io</span><span class="invisible"></span></a></p><p>I’m working towards something for <a href="https://infosec.exchange/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>secure</span></a> / <a href="https://infosec.exchange/tags/private" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>private</span></a> / <a href="https://infosec.exchange/tags/simple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>simple</span></a> <a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> <a href="https://infosec.exchange/tags/filetransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>filetransfer</span></a>. It isnt as “simple” as it could be, im still working on it, but ive got it down to:</p><p>Zero-installation as a <a href="https://infosec.exchange/tags/PWA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PWA</span></a></p><p>Zero-registration by using local-only storage</p><p><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a>-authentication using <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCryptoAPI</span></a></p><p>Fast <a href="https://infosec.exchange/tags/datatransfer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>datatransfer</span></a> using <a href="https://infosec.exchange/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a></p><p>It’s far from finished, but i think ive got it “usable” enough to ask for feedback on it.</p><p>When comparing this project to things like <a href="https://infosec.exchange/tags/wormhole" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wormhole</span></a>, <a href="https://infosec.exchange/tags/onionshare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>onionshare</span></a>, <a href="https://infosec.exchange/tags/localsend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>localsend</span></a>, <a href="https://infosec.exchange/tags/syncthing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>syncthing</span></a>, <a href="https://infosec.exchange/tags/croc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>croc</span></a>, <a href="https://infosec.exchange/tags/sphynctershare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sphynctershare</span></a> and countless others. the key difference in my approach is that its a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapp</span></a> thats ready to go without any "real" setup process. you just need a browser.</p><p>I’m aware there are things like <a href="https://infosec.exchange/tags/SFTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SFTP</span></a> and several other established protocols and tools. I started doing this because I was learning about <a href="https://infosec.exchange/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a> and it seems suprisingly capable. This isnt ready to replace any existing apps or services.</p><p>(Note: I know you guys are typically interested in <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> code. this project is a spin-off from a bigger project: <a href="https://github.com/positive-intentions/chat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/positive-intentions</span><span class="invisible">/chat</span></a>)</p><p>Let me know what you think about the app, features and experience you would expect from a tool like this.</p><p>---</p><p>SUPER IMPORTANT NOTES TO PREVENT MISLEADING:</p><p>These projects are not ready to replace any existing apps or services.</p><p>These projects are not peer-reviewed or security audited.</p><p>The chat-app is <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> for transparency (as linked above)... but the file-app is not open souce at all (especially spicy when not reviewed or audited.).</p><p>All projects behind positive-intentions are provided for testing and demo purposes only.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://flipboard.com/@theverge" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>theverge</span></a></span> <span class="h-card" translate="no"><a href="https://flipboard.com/@theverge/tech-news-e3qmqbb8z" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tech-news-theverge</span></a></span> <a href="https://infosec.space/@kkarhan/114408031693623764" rel="nofollow noopener" target="_blank">yeah...</a></p><p>Meanwhile I recommend migrating to <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a> like <a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JitsiMeet</span></a>, <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCall</span></a> and espechally classic <a href="https://infosec.space/tags/SIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIP</span></a> / <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VoIP</span></a> like <a href="https://infosec.space/tags/Linphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linphone</span></a>! </p><ul><li><a href="https://infosec.space/tags/Skype" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Skype</span></a> fucked up big time, but TBH it was <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> doing <a href="https://infosec.space/tags/EmbraceExtendExtinguish" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EmbraceExtendExtinguish</span></a> instead that killed it!</li></ul>
IT News<p>Tiny, Hackable Telepresence Robot for under $100? Meet Goby - [Charmed Labs] are responsible for bringing numerous open-source hardware products... - <a href="https://hackaday.com/2025/04/17/tiny-hackable-telepresence-robot-for-under-100-meet-goby/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2025/04/17/tiny-h</span><span class="invisible">ackable-telepresence-robot-for-under-100-meet-goby/</span></a> <a href="https://schleuss.online/tags/telepresencerobot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>telepresencerobot</span></a> <a href="https://schleuss.online/tags/crowdfunding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>crowdfunding</span></a> <a href="https://schleuss.online/tags/telepresence" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>telepresence</span></a> <a href="https://schleuss.online/tags/tinypresence" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tinypresence</span></a> <a href="https://schleuss.online/tags/robotshacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>robotshacks</span></a> <a href="https://schleuss.online/tags/arduino" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arduino</span></a> <a href="https://schleuss.online/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a> <a href="https://schleuss.online/tags/esp32" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>esp32</span></a> <a href="https://schleuss.online/tags/goby" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>goby</span></a> <a href="https://schleuss.online/tags/fpv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fpv</span></a></p>
Kevin Karhan :verified:<p>Either am stupid or did <a href="https://infosec.space/tags/Linphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linphone</span></a> basically <em>memory-holed</em> <a href="https://infosec.space/tags/LinphoneWeb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinphoneWeb</span></a> and all <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SourceCode</span></a> for it?</p><ul><li>All I can find about it is <a href="https://www.linphone.org/en/news/linphone-web-1-0-available-today/" rel="nofollow noopener" target="_blank">this</a> <a href="https://infosec.space/tags/PressRelease" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PressRelease</span></a> and <a href="https://infosec.space/tags/Copypasta" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copypasta</span></a> of it. </li></ul><p>No <a href="https://infosec.space/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> or anything... </p><ul><li>Which is sad because it's basically a <a href="https://infosec.space/tags/SIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIP</span></a> client that works with <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a> in a <a href="https://infosec.space/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a>!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jwildeboer</span></a></span> Seriously, who uses <a href="https://infosec.space/tags/Skype" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Skype</span></a> in the age of <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>?</p><p><a href="https://www.youtube.com/watch?v=ZI0w_pwZY3E" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">youtube.com/watch?v=ZI0w_pwZY3E</span><span class="invisible"></span></a></p>
crows call me breadlady<p>who has a <a href="https://friend.camp/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a> experience report</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://433.world/@Yuvalne" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Yuvalne</span></a></span> consider <a href="https://infosec.space/tags/NextcloudTalk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NextcloudTalk</span></a> (included in <span class="h-card" translate="no"><a href="https://mastodon.xyz/@nextcloud" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nextcloud</span></a></span> / <a href="https://infosec.space/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nextcloud</span></a> as hosted <a href="https://docs.monocles.eu/services/cloud.service/#confer" rel="nofollow noopener" target="_blank">by</a> <span class="h-card" translate="no"><a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>monocles</span></a></span> and <span class="h-card" translate="no"><a href="https://mstdn.social/@Stuxhost" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Stuxhost</span></a></span> ) as well as <a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JitsiMeet</span></a> (which is even easier to <a href="https://infosec.space/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHost</span></a>.</p><ul><li>If you only need 1:1 <a href="https://infosec.space/tags/Videocalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Videocalling</span></a>, consider <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCall</span></a> <a href="https://timur.mobi/webcall/" rel="nofollow noopener" target="_blank">as a secure alternative</a>.</li></ul><p>All 3 use <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a> and don't require any shitty <a href="https://infosec.space/tags/Client" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Client</span></a> <a href="https://infosec.space/tags/Installation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Installation</span></a> whatsoever: They work from any modern <a href="https://infosec.space/tags/Browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Browser</span></a> like <a href="https://infosec.space/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a>!</p>
Bhante Subharo ☸️<p>After taking a closer look at <a href="https://c.im/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a> clients for the <a href="https://c.im/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> desktop, there's this frustrating "tie" for finding a favorite. </p><p><a href="https://c.im/tags/Dino" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Dino</span></a>, which is likeable for being able to do video and audio calls, only has limited support for multi-user chat (complete with fancy moderation tools). These audio and video calls it can do are AMD64-only at this time.</p><p><a href="https://c.im/tags/Gajim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gajim</span></a>, which is likeable for being able to do multi-user chat well (with great moderation tools), alas, can't do audio and video calls to the other XMPP clients (like, say, <a href="https://c.im/tags/Conversations" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Conversations</span></a>, as they use a newer <a href="https://c.im/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>-based method now).</p><p>So there's this strange situation where one is tempted to use both at the same time.</p><p>My takeaway is that <a href="https://c.im/tags/Conversations" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Conversations</span></a> for <a href="https://c.im/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> is the only xmpp client that I would possibly and carefully recommend to family and friends at this time, as it can cover all of the above. (<a href="https://c.im/tags/Monal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Monal</span></a> on <a href="https://c.im/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a>/#MacOS only has "partial" support for Multi-user chat, BTW.)</p><p>Yes I'm aware of the existence of Snikket, Quicksy, and Prav. No need to chime in on those.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.coop/@cwebber" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cwebber</span></a></span> yes, and we already have options for that:</p><ul><li><p><a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IRC</span></a> & <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMEMO</span></a>, <a href="https://infosec.space/tags/Zulip" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Zulip</span></a>, etc. for <a href="https://infosec.space/tags/Chat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chat</span></a>.</p></li><li><p><a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JitsiMeet</span></a>, <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCall</span></a> and other <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>-based comms.</p></li><li><p><a href="https://infosec.space/tags/Mumbke" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mumbke</span></a>, <a href="https://infosec.space/tags/SIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIP</span></a> and other <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VoIP</span></a> solutions.</p></li><li><p><a href="https://infosec.space/tags/OnionShare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OnionShare</span></a>, <a href="https://infosec.space/tags/Wormhole" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wormhole</span></a>, <a href="https://infosec.space/tags/oshi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oshi</span></a>, <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BitTorrent</span></a> & <a href="https://infosec.space/tags/IPFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPFS</span></a> for <a href="https://infosec.space/tags/Filesharing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Filesharing</span></a>.</p></li><li><p><a href="https://infosec.space/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Nextcloud</span></a> et. al. for collaboration.</p></li></ul><p>...</p>
xoron :verified:<p><span class="h-card" translate="no"><a href="https://infosec.space/@kkarhan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kkarhan</span></a></span> </p><p>thanks for the reply! far from being discouraged, i appriciate your engagement. i will try to be reasonably brief in my reponse to your points and give a general update on progress and objective.</p><p>> scout out existing solutions</p><p>i have seem similar <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapp</span></a> implementation, i think so far for "that kind" of chat app, the chat app is able to demonstrate similar basic functionality. for a wider adoption, the user interface needs to be more appealing, but i think its important to have a working proof-of-concept first. the project is specifically aiming to be a <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a> <a href="https://infosec.exchange/tags/localFirst" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>localFirst</span></a> <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapp</span></a>.</p><p>a couple notable similar implementation to mine are:<br>- <a href="https://github.com/cryptocat/cryptocat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/cryptocat/cryptocat</span><span class="invisible"></span></a><br>- <a href="https://github.com/jeremyckahn/chitchatter" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/jeremyckahn/chitcha</span><span class="invisible">tter</span></a><br>(im sure there are many more, but i think my approach is yet different and unique to the ones i've come across.)</p><p>> DO NOT DIY ENCRYPTION!</p><p>this is indeed a reccomended practice i have seen several times. here is a previsous reddit post on the matter: <a href="https://www.reddit.com/r/cryptography/comments/1cint8h/what_are_your_thoughts_on_subtlecrypto_vs_wasm" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">reddit.com/r/cryptography/comm</span><span class="invisible">ents/1cint8h/what_are_your_thoughts_on_subtlecrypto_vs_wasm</span></a> ... tldr; the underlying implementation provided by the browser is the best way to go. i have implemented the <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a> using the <a href="https://infosec.exchange/tags/webcrypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webcrypto</span></a> <a href="https://infosec.exchange/tags/api" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>api</span></a>. i aim to not use a library for this. </p><p>i generally try to word things in a way that users can provide feedback on features. the app is still in a very early stage, but has a reasonable amount of features. im generally open to requests and questions.</p><p>> minimum viable product</p><p>what you see as the chat app is also the <a href="https://infosec.exchange/tags/minimum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>minimum</span></a> <a href="https://infosec.exchange/tags/viable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>viable</span></a> <a href="https://infosec.exchange/tags/product" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>product</span></a>. i think its sufficiently demonstrates the basic functionality of a chat app. i think the next step is to make the app more stable and user friendly.</p><p>those other apps youve mentions ive come across before. what sets my approach apart is that mine it's purely a webapp. with what id like to describe as <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>p2p</span></a> <a href="https://infosec.exchange/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>authentication</span></a> over <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webrtc</span></a>, im able to remove reliance on a backend for <a href="https://infosec.exchange/tags/authenticate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>authenticate</span></a> <a href="https://infosec.exchange/tags/data" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>data</span></a> <a href="https://infosec.exchange/tags/connections" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>connections</span></a>. in some cases, bypass the internet (wifi/hotspot). while there are several ways to <a href="https://infosec.exchange/tags/selfhost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhost</span></a>, in this approach of a <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a> implementation, im able to store large amounts of data in the browser so things like images and <a href="https://infosec.exchange/tags/encryptionKeys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryptionKeys</span></a> can be <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a>" in the browser. while this form has nuanced limitations, it also has interesting implications to security and privacy.</p><p>there are many nice features from the different apps you mentioned and i think i have some unique features too. the bottle neck in this project is that i dont put in enough time to the app.</p><p>> feel free to slowly ibtegrate them.</p><p>this is basically already my approach to get the app to where it is now.</p><p>thanks for the luck, take care and i hope you stay tuned for updates.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@xoron" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>xoron</span></a></span> most of <a href="https://infosec.exchange/@xoron/113537250915068979" rel="nofollow noopener" target="_blank">those features</a> have already been implemented in <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>-based solutions <a href="https://timur.mobi/webcall/" rel="nofollow noopener" target="_blank">like</a> <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCall</span></a> <a href="https://jitsi.org/jitsi-meet/" rel="nofollow noopener" target="_blank">and</a> <a href="https://infosec.space/tags/JitsiMert" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JitsiMert</span></a>, abeit like with <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XMPP</span></a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OMEMO</span></a> none does all of those things together, and that is somewhat an acceptable tradeoff...</p>
Álvaro Costa<p>Did I create the ultimate tool to watch anime with friends?<br>:blobcatuwu:</p><p>xtream is a website where you can "upload" any video and watch among other people, without loss of quality.</p><p>Files are actually transferred privately via a P2P connection, without going through my server.</p><p>Each user can choose their preferred audio and subtitle language. Without installing programs or extensions.</p><p>🧵</p><p><a href="https://mastodon.chabal.es/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> <a href="https://mastodon.chabal.es/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://mastodon.chabal.es/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rust</span></a> <a href="https://mastodon.chabal.es/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://mastodon.chabal.es/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Mer__edith</span></a></span> that's a <a href="https://infosec.space/tags/Marketing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Marketing</span></a> <a href="https://infosec.space/tags/Lie" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lie</span></a> as <span class="h-card" translate="no"><a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>signalapp</span></a></span> / <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Signal</span></a> collects and demands <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PII</span></a> like <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PhoneNumbers</span></a> to this day, and unlike <a href="https://infosec.space/tags/WebRTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebRTC</span></a>-based options like <a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JitsiMeet</span></a> and <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebCall</span></a>, one cannot <a href="https://infosec.space/tags/SelfHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHost</span></a> Signal!</p><p>So please stop such bs claims, because they insult the intellect of everyone who's even halfassing <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ITsec</span></a>, <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a>, <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpSec</span></a> & <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComSec</span></a>...</p><p><a href="https://infosec.space/@kkarhan/113467293263701678" translate="no" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">infosec.space/@kkarhan/1134672</span><span class="invisible">93263701678</span></a></p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload