Shakedown Social

NagaramI don't hate the idea behind <a href="https://hachyderm.io/tags/clippy" class="mention hashtag" rel="nofollow noopener" target="_blank">#clippy</a> or <a href="https://hachyderm.io/tags/LouisRossmann" class="mention hashtag" rel="nofollow noopener" target="_blank">#LouisRossmann</a> and his latest activism.However, I really don't think its going to do anything. Were all here because we don't trust big tech corpos to give a shit about us.So to me the obvious correct answer is to go as scorched earth with it as possible. Remove myself from as many <a href="https://hachyderm.io/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> sites as possible. And hope we all can go back to enjoying a free and open or <a href="https://hachyderm.io/tags/decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#decentralized</a> internet.Louis has a motivation though. He has a community and an income stream from YouTube and thus needs it to change or at least be more predictable for him. Most of us aren't really doing this for money over here.I don't expect a PFP change to mean anything if you're still using the service."I hate this restaurant and I wear my 'I hate Arby's' T-shirt every day when I go back to Arby's for lunch. Just so I can remember why I hate it..."

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. 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, declare - “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!

Ben Royce 🇺🇦Everyone share everywhere:<a href="https://youtu.be/YRJHIJy5Nno" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/YRJHIJy5Nno</a><a href="https://mastodon.social/@_elena" class="u-url mention" rel="nofollow noopener" target="_blank">@_elena</a> 's primer on the <a href="https://mastodon.social/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a> <a href="https://mastodon.social/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a>In an ideal world everyone would leave the lying, spying, manipulating <a href="https://mastodon.social/tags/bigot" class="mention hashtag" rel="nofollow noopener" target="_blank">#bigot</a>'s playground that is <a href="https://mastodon.social/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> <a href="https://mastodon.social/tags/corporate" class="mention hashtag" rel="nofollow noopener" target="_blank">#corporate</a> <a href="https://mastodon.social/tags/socialMedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#socialMedia</a> so let us get the word out and make it happen!

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://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>

Ben Royce 🇺🇦<a href="https://app.wafrn.net/fediverse/blog/lukadjo" class="u-url mention" rel="nofollow noopener" target="_blank">@lukadjo</a> <a href="https://toot.wales/@ApAlun" class="u-url mention" rel="nofollow noopener" target="_blank">@ApAlun</a> <a href="https://infosec.exchange/@Crispius" class="u-url mention" rel="nofollow noopener" target="_blank">@Crispius</a> <a href="https://mastodon.social/@fedilore" class="u-url mention" rel="nofollow noopener" target="_blank">@fedilore</a> <a href="https://mastodon.sdf.org/@freeagent" class="u-url mention" rel="nofollow noopener" target="_blank">@freeagent</a> <a href="https://social.tchncs.de/@vfrmedia" class="u-url mention" rel="nofollow noopener" target="_blank">@vfrmedia</a> just an idea(not an original one):the problem with <a href="https://mastodon.social/tags/algorithms" class="mention hashtag" rel="nofollow noopener" target="_blank">#algorithms</a> on <a href="https://mastodon.social/tags/centralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#centralized</a> <a href="https://mastodon.social/tags/socialMedia" class="mention hashtag" rel="nofollow noopener" target="_blank">#socialMedia</a> is that they can be manipulatedon the <a href="https://mastodon.social/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#fediverse</a> why not have a menu of <a href="https://mastodon.social/tags/openSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSource</a> algorithms that anyone can write (audited so they are genuinely manipulation-free)?people can freely choose one, and they can sink into their <a href="https://mastodon.social/tags/algorithm" class="mention hashtag" rel="nofollow noopener" target="_blank">#algorithm</a> stuporif that's what they wantis there harm in that?i'm not saying they *have* to do that

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://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!

Kevin Karhan :verified:<a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> It's not <a href="https://infosec.space/tags/disinfo" class="mention hashtag" rel="nofollow noopener" target="_blank">#disinfo</a> when one points out that you demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener" target="_blank">#PII</a> aka. <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhoneNumbers</a> from Users and that is literally a architectural vulnerability, alongside your <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/Infrastructure" class="mention hashtag" rel="nofollow noopener" target="_blank">#Infrastructure</a>.<ul><li><a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> being 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> <a href="https://infosec.space/tags/Solution" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solution</a> is literally the reason why I consider it <a href="https://infosec.space/tags/insecure" class="mention hashtag" rel="nofollow noopener" target="_blank">#insecure</a>.</li></ul>Not to mention the lack of <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> support with an <a href="https://infosec.space/tags/OnionService" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnionService</a> or the willingness to fulfill <a href="https://infosec.space/tags/cyberfacist" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberfacist</a> "Embargoes" or shilling 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> named <a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#MobileCoin</a>!<ul><li><a href="https://infosec.space/tags/KYC" class="mention hashtag" rel="nofollow noopener" target="_blank">#KYC</a> is the illicit activity!!!</li></ul>And don't get me started on the <a href="https://infosec.space/tags/cyberfacism" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberfacism</a> that is <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a>.<ul><li>If you were secure, criminals would've used your platform so hard, it would've been shutdown like <a href="https://infosec.space/tags/EncroChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncroChat</a> and <a href="https://infosec.space/tags/SkyECC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SkyECC</a>.</li></ul>I may nit have allvthe.evidence yet, but <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a> stenches like <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener" target="_blank">#ANØM</a>: <a href="https://infosec.space/tags/Honeypot" class="mention hashtag" rel="nofollow noopener" target="_blank">#Honeypot</a>-esque!

Kevin Karhan :verified:<a href="https://social.vivaldi.net/@ueeu" class="u-url mention" rel="nofollow noopener" target="_blank">@ueeu</a> I think crucial parts is looking at it's components, dependencies, size and for apps permissions.<ul><li>Also make shure it uses <a href="https://infosec.space/tags/OpenStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenStandards</a>, because <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> can be just a "smoke grenade" when it's 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.</li></ul><a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReproduceableBuilds</a> for example are important, so the actually released source code is what people actually get served as basis.<ul><li>Both of the latter points are something that <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> does perfectly and that <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> completely fails at!</li></ul>Plus in terms of <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>, choose *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 <a href="https://infosec.space/tags/Keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#Keys</a>!

Recent searches

Search options

Administered by:

Server stats:

#centralized