🌈 Social 📸 Photography 🌈

Kevin Karhan :verified:I'm not shure what I should think about <a href="https://www.raspberrypi.com/documentation/services/connect.html" rel="nofollow noopener" target="_blank">Raspberry Pi Connect</a>...<ul><li>Obviously it's an upgrade compared to <a href="https://mastodon.social/@RaspberryPi" class="u-url mention" rel="nofollow noopener" target="_blank">@RaspberryPi</a> / <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a>|s with their [deprecated!] <a href="https://github.com/greyhat-academy/lists.d/blob/cacf5b9fbd80affd34d760c50b0b7333def000bf/default.logins.list.tsv#L3" rel="nofollow noopener" target="_blank">default credential pair</a> exposed on the internet, but I also don't like <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> services like that.</li></ul>Not that I deny the benefits of it, but it's just not for me...<ul><li>It would be cool if it was like in a "managed" / "<a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a>" capable setup for like <a href="https://infosec.space/tags/Classroom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Classroom</a>|s with <a href="https://infosec.space/tags/Pi400" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi400</a> / <a href="https://infosec.space/tags/Pi500" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pi500</a> units where teachers want to have means to quickly remote into a machine if need be...</li></ul>

Faraiwe<a href="https://mastodon.social/@quillmatiq" class="u-url mention" rel="nofollow noopener" target="_blank">@quillmatiq</a> still NOT decentralized, still CORPORATE OWNED, still owned by vc crypto techbros.thIs TimE wILL Be difFerEnT, right?Hardest of passes, thanks, no.<a href="https://mstdn.social/tags/DTBO" class="mention hashtag" rel="nofollow noopener" target="_blank">#DTBO</a> <a href="https://mstdn.social/tags/techbro" class="mention hashtag" rel="nofollow noopener" target="_blank">#techbro</a> <a href="https://mstdn.social/tags/bluesky" class="mention hashtag" rel="nofollow noopener" target="_blank">#bluesky</a> <a href="https://mstdn.social/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> <a href="https://mstdn.social/tags/CorporateWallGarden" class="mention hashtag" rel="nofollow noopener" target="_blank">#CorporateWallGarden</a>

openSUSE LinuxFrom cost savings to <a href="https://fosstodon.org/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> management: how <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> succeeded where <a href="https://fosstodon.org/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> struggled in real-world deployments. Watch the <a href="https://fosstodon.org/tags/TheGreatMigration" class="mention hashtag" rel="nofollow noopener" target="_blank">#TheGreatMigration</a> Parts I & II on the practical path to migration. <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#oSC25</a> <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> <a href="https://youtu.be/2HHle_OmqRE?si=TXfylAA2TBU4sS22" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/2HHle_OmqRE?si=TXfylAA2TBU4sS22</a>

Kevin Karhan :verified:<a href="https://furry.engineer/@soatok" class="u-url mention" rel="nofollow noopener" target="_blank">@soatok</a> IMHO all <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> solutions are bad - including <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a>! <a href="https://infosec.space/@kkarhan/114935952643402592" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/114935952643402592</a><a href="https://infosec.space/tags/InconvenientTruth" class="mention hashtag" rel="nofollow noopener" target="_blank">#InconvenientTruth</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@photovince" class="u-url mention" rel="nofollow noopener" target="_blank">@photovince</a> anyone who doesn't trust a.<a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proprietary</a> <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> solution that demands <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> for no valid reason like <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> does!

Kevin Karhan :verified:<a href="https://infosec.exchange/@artfulmodder" class="u-url mention" rel="nofollow noopener" target="_blank">@artfulmodder</a> last time I checked <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> still demanded <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> in.the form of a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumber</a>, still peddled the <a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileCoin</a> <a href="https://infosec.space/tags/Shitcoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shitcoin</a> <a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scam</a> and didn't move out of the <a href="https://infosec.space/tags/Cyberfacist" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cyberfacist</a> <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#USA</a> despite <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a> being nothing new!<ul><li>Not to mention <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> is both able and willing to discriminate against users based off said PII. Just because they do it for "<a href="https://infosec.space/tags/Sanctions" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sanctions</a> <a href="https://infosec.space/tags/Compliance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Compliance</a>" diesn't mean they ain't gonna change that nor that <a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@Mer__edith</a> (or anyone else at Signal) could be bribed or threatened to do so.</li></ul>They are <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> and are thus a <a href="https://infosec.space/tags/SinglePointOfFailure" class="mention hashtag" rel="nofollow noopener" target="_blank">#SinglePointOfFailure</a> per design!<ul><li>Unlike <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> (which is <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME in a different UI) or <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a> (which you can use via <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> and connect to a Server that is an <a href="https://infosec.space/tags/OnionService" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionService</a>.</li></ul>IMHO "memory tagging" is the least of Signal's problems. To me they stench "<a href="https://infosec.space/tags/ControlledOpposition" class="mention hashtag" rel="nofollow noopener" target="_blank">#ControlledOpposition</a>" just as hard as <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANØM</a> and incompetence as hard as <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncroChat</a>!

contrapunctus ✊🏳️‍🌈🏳️‍⚧️<a class="hashtag" href="https://fe.disroot.org/tag/discord" rel="nofollow noopener" target="_blank">#Discord</a> users, <a class="hashtag" href="https://fe.disroot.org/tag/xmpp" rel="nofollow noopener" target="_blank">#XMPP</a> is <a class="hashtag" href="https://fe.disroot.org/tag/federated" rel="nofollow noopener" target="_blank">#federated</a> and immune to this kind of <a class="hashtag" href="https://fe.disroot.org/tag/enshittification" rel="nofollow noopener" target="_blank">#enshittification</a> ! 🙂Move yourself, move your friends, move your communities. Declare to all <a class="hashtag" href="https://fe.disroot.org/tag/centralized" rel="nofollow noopener" target="_blank">#centralized</a> and <a class="hashtag" href="https://fe.disroot.org/tag/proprietary" rel="nofollow noopener" target="_blank">#proprietary</a> networks ( <a class="hashtag" href="https://fe.disroot.org/tag/signal" rel="nofollow noopener" target="_blank">#Signal</a> <a class="hashtag" href="https://fe.disroot.org/tag/bluesky" rel="nofollow noopener" target="_blank">#BlueSky</a> …) - “Never again!”<a href="https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html" rel="nofollow noopener" target="_blank">The Quick and Easy Guide to Jabber/XMPP</a><a href="https://mastodon.social/@emaytch/114747736099579585" rel="nofollow noopener" target="_blank">https://mastodon.social/@emaytch/114747736099579585</a>

Kevin Karhan :verified:<a href="https://social.anoxinon.de/@mit_scharf" class="u-url mention" rel="nofollow noopener" target="_blank">@mit_scharf</a> the problem with "threat scenarios" is that they tend to change quickly, non-consensual and without warning.<ul><li>Demanding any <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> [even by virtue of being correlateable through circumstances] to be able to use a service is inherently bad, espechally since there is no "legitimate interest" for that.</li></ul>"<a href="https://infosec.space/tags/KYC" class="mention hashtag" rel="nofollow noopener" target="_blank">#KYC</a>" is the illicit activity! and <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> acts as a <a href="https://en.wikipedia.org/wiki/Opposition_(politics)#Controlled_opposition" rel="nofollow noopener" target="_blank">controlled opposition</a> by virtue of being a <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> "solution" that subjects itself to a juristiction that has 0 <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> laws and only <a href="https://infosec.space/tags/cyberfacism" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberfacism</a> (see <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a> ) to boot...<ul><li>I find it more fatiguing and also expensive to try to workaround shite than to migrate folks to secure standards because that's a one-time investment that I'm willing to take vs. having to jump through hoops and paywalls to acquire a working <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a> (or <a href="https://infosec.space/tags/eSIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#eSIM</a>) anonymously and maintaining it.</li></ul>It's just not in the cards TBH!

Kevin Karhan :verified:<a href="https://piaille.fr/@ciourte" class="u-url mention" rel="nofollow noopener" target="_blank">@ciourte</a> <a href="https://social.coop/@netopwibby" class="u-url mention" rel="nofollow noopener" target="_blank">@netopwibby</a> Needless to say I've only heard of some Spanish low-cost <a href="https://infosec.space/tags/MVNO" class="mention hashtag" rel="nofollow noopener" target="_blank">#MVNO</a> offering one device only in a <a href="https://infosec.space/tags/prepaid" class="mention hashtag" rel="nofollow noopener" target="_blank">#prepaid</a> <a href="https://infosec.space/tags/bundle" class="mention hashtag" rel="nofollow noopener" target="_blank">#bundle</a> when <a href="https://infosec.space/tags/FirefoxOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FirefoxOS</a> was unveiled at the <a href="https://infosec.space/tags/MWC" class="mention hashtag" rel="nofollow noopener" target="_blank">#MWC</a> in <a href="https://infosec.space/tags/Barcelona" class="mention hashtag" rel="nofollow noopener" target="_blank">#Barcelona</a> based off coverage in <a href="https://social.heise.de/@ct_Magazin" class="u-url mention" rel="nofollow noopener" target="_blank">@ct_Magazin</a> at the time.<ul><li>Cuz I remember <a href="https://infosec.space/tags/WebDevs" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevs</a> like <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener" target="_blank">@fuchsiii</a> really loving it because it was the then hot & fresh <a href="https://infosec.space/tags/HTML5" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML5</a> + <a href="https://infosec.space/tags/JS6" class="mention hashtag" rel="nofollow noopener" target="_blank">#JS6</a> + <a href="https://infosec.space/tags/CSS3" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS3</a> combo to make it super-easy to do <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apps</a>. All one needs to build an app was <a href="https://infosec.space/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firefox</a> as Browser and the ability to basically zip' it.</li></ul>Alas <a href="https://mastodon.cc/@Mozilla" class="u-url mention" rel="nofollow noopener" target="_blank">@Mozilla</a> deciding on purpose to literally splinter the market by letting <a href="https://infosec.space/tags/MNO" class="mention hashtag" rel="nofollow noopener" target="_blank">#MNO</a>|s and MVNOs run their <a href="https://infosec.space/tags/AppStore" class="mention hashtag" rel="nofollow noopener" target="_blank">#AppStore</a>|s instead of a <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> model, making the situation worse than in the "P.R." <a href="https://infosec.space/tags/China" class="mention hashtag" rel="nofollow noopener" target="_blank">#China</a> where there are several vendor-independent <a href="https://infosec.space/tags/AppStores" class="mention hashtag" rel="nofollow noopener" target="_blank">#AppStores</a> for <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a>. <ul><li>"Conspiracy Theorists" even suggested that this was deliberate self-sabotage to benefit <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> and <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a>, tho needless to say Firefox OS aimed at devices & specs that were too low for Android.</li></ul>Still, I'm <a href="https://infosec.space/tags/StillMad" class="mention hashtag" rel="nofollow noopener" target="_blank">#StillMad</a> at <a href="https://infosec.space/tags/Mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mozilla</a> for faceplanting Firefox OS cuz it had the easiest way to get started and a good architecture being every <a href="https://infosec.space/tags/App" class="mention hashtag" rel="nofollow noopener" target="_blank">#App</a> is just a <a href="https://infosec.space/tags/WebApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebApp</a> and all the system calls were standard <a href="https://infosec.space/tags/HTML5" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTML5</a> permissions and nothing fancy.<ul><li>Basically <a href="https://infosec.space/tags/PSvita" class="mention hashtag" rel="nofollow noopener" target="_blank">#PSvita</a> - <a href="https://www.youtube.com/watch?v=REaUzHef9h4" rel="nofollow noopener" target="_blank">Syndrome,</a> but worse as in <a href="https://infosec.space/tags/OpenMoko" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenMoko</a> <a href="https://infosec.space/tags/Freenunner" class="mention hashtag" rel="nofollow noopener" target="_blank">#Freenunner</a>: </li></ul><a href="https://www.youtube.com/watch?v=p76exsJn7SU" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=p76exsJn7SU</a>

contrapunctus ✊🏳️‍🌈🏳️‍⚧️<a href="https://aus.social/@dgar" class="u-url mention" rel="nofollow noopener" target="_blank">@dgar</a> Love the variety of synonyms for "died" 😆Lessons to be learned - • Boycott <a href="https://en.osm.town/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proprietary</a> software - use <a href="https://en.osm.town/tags/FreedomRespecting" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreedomRespecting</a> software (a.k.a. <a href="https://en.osm.town/tags/Libre" class="mention hashtag" rel="nofollow noopener" target="_blank">#Libre</a> / <a href="https://en.osm.town/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> / <a href="https://en.osm.town/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a>) which is free of corporate control, and • Boycott <a href="https://en.osm.town/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> services - use <a href="https://en.osm.town/tags/federated" class="mention hashtag" rel="nofollow noopener" target="_blank">#federated</a> services so you aren't locked into one service.<a href="https://en.osm.town/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a> is still around, and thriving. <a href="https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html" rel="nofollow noopener" translate="no" target="_blank">https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html</a>

Kevin Karhan :verified:<a href="https://darmstadt.social/@stormii" class="u-url mention" rel="nofollow noopener" target="_blank">@stormii</a> <a href="https://hear-me.social/@debby" class="u-url mention" rel="nofollow noopener" target="_blank">@debby</a> okay.Still a <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> service that <a href="http://dreadytofatroptsdj6io7l3xptbet6onoyno2yv7jicoxknyazubrad.onion/post/2077a6d441154a89bbb4" rel="nofollow noopener" target="_blank">snitches on users</a> if it ain't yet another <a href="https://infosec.space/tags/Honeypot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Honeypot</a> like <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANØM</a>...

Kevin Karhan :verified:<a href="https://hear-me.social/@debby" class="u-url mention" rel="nofollow noopener" target="_blank">@debby</a> <a href="https://infosec.space/tags/Mumble" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mumble</a>, <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IRC</a>, <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a> (+OMEMO = <a href="https://fosstodon.org/@gajim" class="u-url mention" rel="nofollow noopener" target="_blank">@gajim</a> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#monoclesChat</a>) & <a href="https://infosec.space/tags/Linphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linphone</a> (<a href="https://infosec.space/tags/SIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIP</a> / <a href="https://infosec.space/tags/VoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoIP</a>) are the better options. <a href="https://infosec.space/tags/NextcloudTalk" class="mention hashtag" rel="nofollow noopener" target="_blank">#NextcloudTalk</a> also exist and <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> as well as <a href="https://mstdn.social/@Stuxhost" class="u-url mention" rel="nofollow noopener" target="_blank">@Stuxhost</a> offer that.<ul><li><a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> and <a href="https://infosec.space/tags/Session" class="mention hashtag" rel="nofollow noopener" target="_blank">#Session</a> are <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> solutions!</li><li>And <a href="https://infosec.space/tags/Matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Matrix</a> is just a shittier <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a>. Give <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> / <a href="https://infosec.space/tags/DeltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeltaChat</a> a try instead.</li></ul>OfC <a href="https://infosec.space/tags/JitsiMeet" class="mention hashtag" rel="nofollow noopener" target="_blank">#JitsiMeet</a> and <a href="https://infosec.space/tags/WebCall" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebCall</a> are also great!<a href="https://webcall.timur.mobi" rel="nofollow noopener" translate="no" target="_blank">https://webcall.timur.mobi</a>

Kevin Karhan :verified:<a href="https://tweesecake.social/@adisonverlice" class="u-url mention" rel="nofollow noopener" target="_blank">@adisonverlice</a> I think that's dangerous disinfo as <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> actively works against attempts to fingerprint and track <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> users.<ul><li>I do consider Tor more private than any <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a> simply becaise they can neither ban users nor identify them.</li></ul>In fact, Tor has been designed with the explicit goal to circumvent <a href="https://infosec.space/tags/Firewalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewalls</a> and <a href="https://infosec.space/tags/InternetCensorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#InternetCensorship</a> methods like <a href="https://infosec.space/tags/DeepApcketInspection" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeepApcketInspection</a>.<ul><li>Which is why <a href="https://infosec.space/tags/OnionShare" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionShare</a> by <a href="https://infosec.exchange/@micahflee" class="u-url mention" rel="nofollow noopener" target="_blank">@micahflee</a> works so great!</li></ul>As a matter of principle I'd never vouch for any <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> and/or <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> solution of any kind, including <a href="https://infosec.space/tags/Session" class="mention hashtag" rel="nofollow noopener" target="_blank">#Session</a>.<ul><li>Tor is sufficiently decentralized in that it is not only completely <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> but has proven to not have SPOFs in the form of maintainers and is able to yeet proplematic folks (unlike <a href="https://infosec.space/tags/WikiLeaks" class="mention hashtag" rel="nofollow noopener" target="_blank">#WikiLeaks</a>!)…</li></ul>

Shanie MyrsTearFor <a href="https://mastodon.tails.ch/tags/Discord" class="mention hashtag" rel="nofollow noopener" target="_blank">#Discord</a>, the end-times are sooner than we think.With the pickup of Ex-Activision Exec Humam Sakhnini, you know, the Call of M̶o̶n̶e̶y̶ Duty publisher, as CEO of Discord, we can effectively say "goodbye" to what Discord is, and "hello" to the complete <a href="https://mastodon.tails.ch/tags/enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#enshittification</a> of a service marching headfirst into <a href="https://mastodon.tails.ch/tags/IPO" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPO</a>.Sorry ya'll, but we're due to move off another <a href="https://mastodon.tails.ch/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> place we love if we care about the services we get. And it sucks, because Discord has a good UX.<a href="https://discord.com/blog/passing-the-torch" rel="nofollow noopener" translate="no" target="_blank">https://discord.com/blog/passing-the-torch</a>

Kevin Karhan :verified:<a href="https://tweesecake.social/@adisonverlice" class="u-url mention" rel="nofollow noopener" target="_blank">@adisonverlice</a> it's not just re: <a href="https://infosec.space/tags/Governments" class="mention hashtag" rel="nofollow noopener" target="_blank">#Governments</a> (tho <a href="https://infosec.space/tags/Project2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#Project2025</a> explicitly endorses unsactioned comms to twart attempts at <a href="https://infosec.space/tags/FIOA" class="mention hashtag" rel="nofollow noopener" target="_blank">#FIOA</a> or any <a href="https://infosec.space/tags/accountability" class="mention hashtag" rel="nofollow noopener" target="_blank">#accountability</a> for that matter), but individuals or any organization:<ul><li>If a system is <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> as in <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> and/or <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a>, it's inherently vulnerable.</li></ul>And if <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncroChat</a> got pwned, who's gonna guarantee <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> won't if it's actually secure or isn't an <a href="https://infosec.space/tags/InsideJob" class="mention hashtag" rel="nofollow noopener" target="_blank">#InsideJob</a> like <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANØM</a>.After all, both <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a>'s Organization and key people like <a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@Mer__edith</a> are known to the authorities by more than just their legal name.<ul><li>What's gonna prevent <a href="https://infosec.space/tags/Trump" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trump</a> from doing a "bag&drag" on her or getting his goons to put a gun on,the developers' heads and force them to,<a href="https://infosec.space/tags/d0x" class="mention hashtag" rel="nofollow noopener" target="_blank">#d0x</a> all users and <a href="https://infosec.space/tags/backdoor" class="mention hashtag" rel="nofollow noopener" target="_blank">#backdoor</a> everything (if they didn't already got forced to have some "<a href="https://infosec.space/tags/LafwulInterception" class="mention hashtag" rel="nofollow noopener" target="_blank">#LafwulInterception</a>" gear in a closet like <a href="https://infosec.space/tags/Room641A" class="mention hashtag" rel="nofollow noopener" target="_blank">#Room641A</a>... </li></ul>After all, Signal <a href="https://web.archive.org/web/20220112020000/https://twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank">can't pull the 5th</a> and refuse to comply!

Kevin Karhan :verified:<a href="https://infosec.exchange/@bob_zim" class="u-url mention" rel="nofollow noopener" target="_blank">@bob_zim</a> yeah. Seen it. in the writeup by <a href="https://infosec.exchange/@micahflee" class="u-url mention" rel="nofollow noopener" target="_blank">@micahflee</a> ...I just hope to find any that ain't <a href="https://infosec.space/tags/NetLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetLock</a>'d / <a href="https://infosec.space/tags/SimLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#SimLock</a>'d to <a href="https://infosec.space/tags/Verizon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Verizon</a> and that these support more than <a href="https://infosec.space/tags/US" class="mention hashtag" rel="nofollow noopener" target="_blank">#US</a>-<a href="https://infosec.space/tags/LTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#LTE</a> bands... <ul><li>Not shure if it needs a valid <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a> or just an <a href="https://infosec.space/tags/ICCID" class="mention hashtag" rel="nofollow noopener" target="_blank">#ICCID</a> + <a href="https://infosec.space/tags/Ki" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ki</a> on a <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a> to get going (cuz in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> it's hard [imported <a href="https://infosec.space/tags/SIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIM</a>] to illegal [domestic SIMs] to get an anonymous SIM since 07/2017.</li></ul>I just wish <a href="https://mastodon.social/@eff" class="u-url mention" rel="nofollow noopener" target="_blank">@eff</a> wouldn't expect everyone to use <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> services like <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> in the age of <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a>, cuz neither I nor anyone I'd trust would submit <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> to them like a <a href="https://infosec.space/tags/PhoneNumer" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumer</a> <a href="https://infosec.space/@kkarhan/114234551915193036" rel="nofollow noopener" target="_blank">as a matter of principle!</a>

Jon JuarezDecentralization against AI:Big Tech's sole interest is to control the narratives through biases, algorithms, <a href="https://mas.to/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>. In the past, they bought newspapers and journalists; now they buy platforms and bots. But without users, they have no value. Underfeeding <a href="https://mas.to/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> networks is the way against AI⚡️ 1/5 ⬇️

Kevin Karhan :verified:<a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> no it's not.<ul><li>Otherwise <a href="https://infosec.space/tags/OrganizedCrime" class="mention hashtag" rel="nofollow noopener" target="_blank">#OrganizedCrime</a> would choose <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> so hard, you'd be shutdown within weeks by the <a href="https://infosec.space/tags/FBI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FBI</a> and <a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@Mer__edith</a> would be forced to "pull a <a href="https://infosec.space/tags/LavaBit" class="mention hashtag" rel="nofollow noopener" target="_blank">#LavaBit</a>" and face jailtime for obstruction of justice or snitch on users! </li></ul>Being a <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> solution subject to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a> makes you inherently vulnerable by your own choice and thus trivial to shutdown compared to real <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2EE</a> with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfCustody</a> of all the keys and true <a href="https://infosec.space/tags/decentralization" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralization</a> as well as <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> (i.e. <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME [see <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> / <a href="https://infosec.space/tags/deltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#deltaChat</a> et. al.] and <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a> [see <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#monoclesChat</a> et. al.]!)<ul><li>Plus neither of those <a href="https://www.youtube.com/watch?v=0DSGq9FQKU4" rel="nofollow noopener" target="_blank">shill</a> <a href="https://infosec.space/tags/Shitcoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shitcoin</a>-<a href="https://infosec.space/tags/Scams" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scams</a> <a href="https://www.youtube.com/watch?v=tJoO2uWrX1M" rel="nofollow noopener" target="_blank">like</a> <a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileCoin</a>! </li></ul>And don't even get me started on you collecting <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> (espechally <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumbers</a>) for no valid reason, (thus violating <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a> & <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener" target="_blank">#BDSG</a>)...<ul><li>Not to mention relying ob <a href="https://infosec.space/tags/charity" class="mention hashtag" rel="nofollow noopener" target="_blank">#charity</a> and being a <a href="https://infosec.space/tags/VCmoneyBurningParty" class="mention hashtag" rel="nofollow noopener" target="_blank">#VCmoneyBurningParty</a> isn't sustainable to begin with!</li></ul>But yeah, I'll be patient to shout "<a href="https://infosec.space/tags/ToldYaSo" class="mention hashtag" rel="nofollow noopener" target="_blank">#ToldYaSo</a>" to your annoying cult of fanboys!

Kevin Karhan :verified:<a href="https://mastodon.social/@dzwiedziu" class="u-url mention" rel="nofollow noopener" target="_blank">@dzwiedziu</a> <a href="https://mastodon.social/@fj" class="u-url mention" rel="nofollow noopener" target="_blank">@fj</a> <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> not really, as the <a href="https://infosec.space/tags/Metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#Metadata</a> <a href="https://infosec.space/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUD</a> cited by <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> is mitigateable with proper measures.<ul><li>You can't even run Signal over <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> and even if that point is moot when you're forced to quasi-<a href="https://infosec.space/tags/KYC" class="mention hashtag" rel="nofollow noopener" target="_blank">#KYC</a> by virtue of a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumber</a> aka. <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> they have neither legitimate interest nor technical reason to demand in the first place!</li></ul>Every claim that things like <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a>, <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a>, <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpSec</a> & <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ComSec</a> can be solved with "Just use Signal!" is "<a href="https://infosec.space/tags/TechPopulism" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechPopulism</a>" at best if not being a "<a href="https://infosec.space/tags/UsefulIdiot" class="mention hashtag" rel="nofollow noopener" target="_blank">#UsefulIdiot</a>"!<ul><li>All <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProbider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProbider</a> systems are inherently insecure!</li></ul><a href="https://infosec.space/tags/EOD" class="mention hashtag" rel="nofollow noopener" target="_blank">#EOD</a> <a href="https://infosec.space/tags/thxbye" class="mention hashtag" rel="nofollow noopener" target="_blank">#thxbye</a> <a href="https://infosec.space/tags/next" class="mention hashtag" rel="nofollow noopener" target="_blank">#next</a>

Kevin Karhan :verified:<a href="https://social.tchncs.de/@pixelcode" class="u-url mention" rel="nofollow noopener" target="_blank">@pixelcode</a> <a href="https://fedi.feministwiki.org/users/taylan" class="u-url mention" rel="nofollow noopener" target="_blank">@taylan</a> that is simply not true.<a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> is <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> and there's no way one can verify the code released for the servers is what they actually run.Unlike <a href="https://social.tchncs.de/@pixelcode/114229194820119509" rel="nofollow noopener" target="_blank">your replies</a> my criticisms ain't founded based off "<a href="https://infosec.space/tags/TrustMeBro" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrustMeBro</a>!" but systemic issues I highlight which <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> refuses to address or take seriously!

Recent searches

Search options

Administered by:

Server stats:

#centralized