bildung.social

3 Beiträge3 Beteiligte0 Beiträge heute

Kevin Karhan :verified:<a href="https://techhub.social/@ozone89" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ozone89</a> <a href="https://digipres.club/@foone" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@foone</a> oftentimes companies just come up with <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> connectors to shaft their clients, like <a href="https://infosec.space/tags/PoweredUSB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PoweredUSB</a> doing 12V & 24V...<a href="https://en.wikipedia.org/wiki/PoweredUSB" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/PoweredUSB</a>

WuzzyJust to be clear: If <a href="https://cyberplace.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> decides it’s okay to no longer send non-Gmail users the ACTUAL <a href="https://cyberplace.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a>, but only a LINK to some bullshit <a href="https://cyberplace.social/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> service that you must click to “unlock” the TRUE contents, then Gmail ceases to be an email provider but is merely a spam service which bullies unsuspecting users into using their proprietary crap.While this seems to be limited to (fake) E2E for now, I’m afraid it could get worse if people do not resist.I know why I don’t use <a href="https://cyberplace.social/tags/Gmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gmail</a>.

jablkoziemne<a href="https://tilvids.com/accounts/thelinuxexperiment" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thelinuxexperiment</a> 19:00 about that developers or publishers could just <a href="https://101010.pl/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> ancient games for the community, they dont usually tend to do that because of other <a href="https://101010.pl/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> libraries, and stuff that they used to make the <a href="https://101010.pl/tags/game" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#game</a> Sure, they could just run through the source code - if it even still exists - and remove not theirs stuff, but that would require knowledge of all not theirs proprietary elements, or ability to start their old developement environments or other game engines, that are the only sensible way of accessing scripts/logic stored in obscure binary formats.But yes, they should at least try to check if the source code is still on theirs discs, ask their lawyers if they can do that, and what has to be stripped, and maybe hire one intern to do all that work, to get hang of using computer, and tools they have used.

contrapunctus ✊🏳️‍🌈🏳️‍⚧️<a href="https://fosstodon.org/@simendsjo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@simendsjo</a> <a href="https://functional.cafe/@jackdaniel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jackdaniel</a> <a href="https://en.osm.town/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a> has all those features, and there's a fairly big <a href="https://en.osm.town/tags/Lisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lisp</a> / <a href="https://en.osm.town/tags/Scheme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scheme</a> / <a href="https://en.osm.town/tags/CommonLisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonLisp</a> channel there - <a href="https://xmpp.link/#lisp@conference.a3.pm?join" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xmpp.link/#lisp@conference.a3.pm?join</a>It might not have everything that <a href="https://en.osm.town/tags/Discord" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Discord</a> does, but it's vastly better than <a href="https://en.osm.town/tags/IRC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IRC</a>. And there's a cost to using <a href="https://en.osm.town/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> and <a href="https://en.osm.town/tags/centralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#centralized</a> services, which people constantly forget about in chasing convenience and shiny features.Here's a guide to help you get started. <a href="https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html</a>

Kevin Karhan :verified:<a href="https://social.tchncs.de/@pixelcode" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pixelcode</a> neither are there reproduceable builds nor is <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a>'s <a href="https://infosec.space/tags/backend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backend</a> opensoirce'd nor is it possible to <a href="https://infosec.space/tags/SelfHost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHost</a>.<ul><li>Thus it is <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaaS</a>!</li></ul>

contrapunctus ✊🏳️‍🌈🏳️‍⚧️Remember - the rest of the <a href="https://en.osm.town/tags/OpenStreetMap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStreetMap</a> <a href="https://en.osm.town/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> ecosystem is still on <a href="https://en.osm.town/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a>. The OSM website, the iD editor, <a href="https://bird.makeup/users/osmandapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@osmandapp</a>, <a href="https://en.osm.town/@vespucci_editor" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vespucci_editor</a>, <a href="https://en.osm.town/@everydoor" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@everydoor</a>, @osmapp...despite offers to help with the move.I know the devs to be otherwise very friendly and supportive people, but on this issue we are at an impasse.Why do they wait to be abused by <a href="https://en.osm.town/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> platforms when they could avoid the whole problem from the start?

contrapunctus ✊🏳️‍🌈🏳️‍⚧️On the train ride back from Patna (<a href="https://en.osm.town/tags/BiharFOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BiharFOSS</a>), <a href="https://toot.io/@ravi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ravi</a> and I sardonically thanked Trump for the state of things in the US, which may have been why <a href="https://en.osm.town/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> disabled the <a href="https://en.osm.town/tags/OrganicMaps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OrganicMaps</a> repo and forced them to move to <a href="https://en.osm.town/tags/FreedomRespecting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreedomRespecting</a> <a href="https://en.osm.town/tags/Forgejo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forgejo</a>."This will hopefully teach people why it's important to boycott <a href="https://en.osm.town/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> platforms. But why do people always wait around for such things to pass? <a href="https://en.osm.town/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> activists had been warning them for like 10 years!" (Also...Sourceforge???)<a href="https://en.osm.town/tags/OpenStreetMap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStreetMap</a>

Kevin Karhan :verified:<a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@signalapp</a> It's not <a href="https://infosec.space/tags/disinfo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#disinfo</a> when one points out that you demand <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PII</a> aka. <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#proprietary</a> & <a href="https://infosec.space/tags/Centralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Centralized</a> <a href="https://infosec.space/tags/Infrastructure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Infrastructure</a>.<ul><li><a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a> being a <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a> <a href="https://infosec.space/tags/Solution" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a> support with an <a href="https://infosec.space/tags/OnionService" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OnionService</a> or the willingness to fulfill <a href="https://infosec.space/tags/cyberfacist" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cyberfacist</a> "Embargoes" or shilling a <a href="https://infosec.space/tags/Shitcoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Shitcoin</a> <a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scam</a> named <a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MobileCoin</a>!<ul><li><a href="https://infosec.space/tags/KYC" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#cyberfacism</a> that is <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#EncroChat</a> and <a href="https://infosec.space/tags/SkyECC" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#Signal</a> stenches like <a href="https://infosec.space/tags/AN%C3%98M" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ANØM</a>: <a href="https://infosec.space/tags/Honeypot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Honeypot</a>-esque!

Kevin Karhan :verified:<a href="https://social.vivaldi.net/@ueeu" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#OpenStandards</a>, because <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a> solution.</li></ul><a href="https://infosec.space/tags/ReproduceableBuilds" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">@monocles</a> / <a href="https://infosec.space/tags/monoclesChat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#monoclesChat</a> does perfectly and that <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#security</a>, choose *real <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfCustody</a> of all the <a href="https://infosec.space/tags/Keys" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keys</a>!

Kevin Karhan :verified:<a href="https://fediscience.org/@petersuber" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@petersuber</a> except <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@signalapp</a> is <a href="https://infosec.space/tags/commervial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commervial</a> as in <a href="https://infosec.space/tags/VVmoneyBurningParty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VVmoneyBurningParty</a>, <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a>! <ul><li>It really is that simple...</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@bdf2121cc3334b35b6ecda66e471" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bdf2121cc3334b35b6ecda66e471</a> <a href="https://social.glitched.systems/@froge" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@froge</a> <a href="https://mastodon.social/@fj" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fj</a> maybe but it's better than a <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleBendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleBendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a> solutiom as it just works even on <a href="https://infosec.space/tags/throttled" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#throttled</a>, sub-<a href="https://infosec.space/tags/2G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2G</a> speeds over <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a>...<ul><li>And you get real <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfCustody</a> of all the Keys!<a href="https://infosec.space/@kkarhan/114223266562515116" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://infosec.space/@kkarhan/114223266562515116</a></li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@fj" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fj</a> I still think <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@signalapp</a> has fundamental flaws like demanding <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PII</a> (<a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PhoneNumbers</a> can't be obtained anonymously around the globe and are trivial to track down to devices and thus users), being subject to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudAct</a> as an unnecessary & 100% avoidable risk as well as <a href="https://infosec.space/tags/Shitcoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Shitcoin</a>-<a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scam</a> shilling (<a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MobileCoin</a>) and it's <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a> nature that makes it inferior to real <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a> with <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfCustody</a> like <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PGP</a>/MIME & <a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OMEMO</a>!

Kevin Karhan :verified:<a href="https://kolektiva.social/@licho" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@licho</a> <a href="https://hachyderm.io/@osman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@osman</a> provide evidence the code <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@signalapp</a> released is actually being deployed.<ul><li>Whereas <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@monocles</a> has <a href="https://infosec.space/tags/ReproducibleBuilds" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ReproducibleBuilds</a> to the point that <a href="https://floss.social/@fdroidorg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fdroidorg</a> literally pulls their <code>git</code> and builds it from source.</li></ul>Not to mention pushing a <a href="https://infosec.space/tags/Shitcoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Shitcoin</a>-<a href="https://infosec.space/tags/Scam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Scam</a> (<a href="https://infosec.space/tags/MobileCoin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MobileCoin</a>) disqualifies <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a> per very design! <a href="https://www.youtube.com/watch?v=tJoO2uWrX1M" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=tJoO2uWrX1M</a><ul><li>Given the collection of <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PII</a> like <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PhoneNumbers</a>, the ability to restrict functionality based off those and the fact that <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a> is subject to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudAct</a> make it inherently not trustworthy.</li></ul>And don't even get me started on the fact.it's not sustainable to run it as a <a href="https://infosec.space/tags/VCmoneyBurningParty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VCmoneyBurningParty</a>!<ul><li>As soon as Signal becomes a problem, it will be taken offline, and due to the fact that it is <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a> that's trivial for authorities.</li></ul>Same as identifying users: They already got a <a href="https://infosec.space/tags/PhoneNumber" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PhoneNumber</a> which in many juristictions one can't even obtain without <a href="https://infosec.space/tags/ID" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ID</a> legally, thus making it super easy to i.e. find and locate a user. Even tze cheapest LEAs can force their local M(V)NOs to <a href="https://infosec.space/tags/SS7" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SS7</a> a specific number...<ul><li>All these are unnecessary risks, that could've been avoided, but explicitly don't even get remediated retroactively!</li></ul>Again: Signal has a <a href="https://infosec.space/tags/Honeypot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Honeypot</a> stench, and you better learn proper <a href="https://infosec.space/tags/E2EE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#E2EE</a>, <a href="https://infosec.space/tags/SelfCustody" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfCustody</a> and <a href="https://infosec.space/tags/TechLiteracy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechLiteracy</a> because <a href="https://web.archive.org/web/20210606070919/twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener noreferrer" target="_blank">corporations can't pull the 5th [Amendment] on your behalf!</a>

Kevin Karhan :verified:<a href="https://hachyderm.io/@osman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@osman</a>, no because <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@signalapp</a> is a <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/centealized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#centealized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a> solution that demands <a href="https://infosec.space/tags/PII" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PII</a> like <a href="https://infosec.space/tags/PhoneNumbers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PhoneNumbers</a> for no valid reason, is subject to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CloudAct</a> and only continues to exist because it's convenient as a means to fo <a href="https://infosec.space/tags/BulkSurveillance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BulkSurveillance</a> and mark it's users as <a href="https://infosec.space/tags/PeopleOfInterest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PeopleOfInterest</a>.<ul><li>I'd rather donate to <a href="https://anonsys.net/profile/ccc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ccc</a> for running <a href="http://jabber.ccc.de" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://jabber.ccc.de</a> and buy a <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@monocles</a> <a href="https://infosec.space/tags/subscription" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#subscription</a> instead!</li></ul>

Kevin Karhan :verified:<a href="https://flyovercountry.social/@encthenet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@encthenet</a> granted, I'd be wary given the fact that <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@signalapp</a> is a <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#centralized</a>, <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a> solution.<ul><li>Tho you are correct in that this entire fuckup should not have been possible to begin with, but the "Chief Moron" <a href="https://infosec.space/@kkarhan/114219718791838165" rel="nofollow noopener noreferrer" target="_blank">decided to not obey existing rules</a>!</li></ul>

Blort™ 🐀Ⓥ🥋☣️Good luck <a href="https://fosstodon.org/@weblate" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@weblate</a> ... While <a href="https://mastodon.xyz/@nextcloud" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nextcloud</a> talks about FOSS and decentralization, people have been asking them for years about using <a href="https://social.tchncs.de/tags/Peertube" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Peertube</a> and <a href="https://social.tchncs.de/tags/Weblate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Weblate</a>, but it's always crickets and continued exclusive use of <a href="https://social.tchncs.de/tags/YouTube" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#YouTube</a> and <a href="https://social.tchncs.de/tags/Transifex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Transifex</a>.There's virtually never even a response why they exclusively use the closed, <a href="https://social.tchncs.de/tags/centralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#centralized</a>, <a href="https://social.tchncs.de/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> services.I respect <a href="https://mastodon.social/@Karlitschek" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Karlitschek</a> and <a href="https://fosstodon.org/@jospoortvliet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jospoortvliet</a> but the org seems only interested in <a href="https://social.tchncs.de/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> / <a href="https://social.tchncs.de/tags/Privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> / <a href="https://social.tchncs.de/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a> in their own code / marketing.

NovaI believe Dan plans to never <a href="https://techhub.social/tags/federate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#federate</a> , revoke federation, or at least retain the ability to do so. See term 2 on Loop's website: <a href="https://loops.video/legal/terms-of-service" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://loops.video/legal/terms-of-service</a> which says such things as "under this license you may not:...use the materials for any commercial purpose, or for any public display (commercial or non-commercial);.....transfer the materials to another person or "mirror" and the materials on any other server...This license shall automatically terminate if you violate any of these restrictions and may be terminated by Loops at any time." and "Loops may revise these terms of service for its website at any time without notice" Loops' terms are not open source and could be used to justify <a href="https://techhub.social/tags/defederation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#defederation</a> or changing policy on federation. And considering how dan behaves with peers who disagree with him, I could see him deciding federation isn't what he wants to do with Loops, which he treats not as an <a href="https://techhub.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> thing but as <a href="https://techhub.social/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> NO <a href="https://techhub.social/tags/FOSSWASHING" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSSWASHING</a> <a href="https://techhub.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://techhub.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://techhub.social/tags/loops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#loops</a> <a href="https://techhub.social/tags/pixelfed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pixelfed</a> <a href="https://techhub.social/tags/dansup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dansup</a>

Thor A. HoplandIsn't it about time we start rallying against <a href="https://snabelen.no/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a> <a href="https://snabelen.no/tags/firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firmware</a> already? From every <a href="https://snabelen.no/tags/EV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EV</a> and <a href="https://snabelen.no/tags/car" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#car</a> being a glorified <a href="https://snabelen.no/tags/telemetry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#telemetry</a> machine, to every chip out there basically harboring <a href="https://snabelen.no/tags/SecretSauce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecretSauce</a> with the "trust me bro" guarantee attached. Neither <a href="https://snabelen.no/tags/US" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#US</a> interests, <a href="https://snabelen.no/tags/Chinese" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Chinese</a> interests or private interests should hold so much power. No one should. All firmware; I repeat, ALL FIRMWARE should be <a href="https://snabelen.no/tags/OpenFirmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenFirmware</a>. The firmware isn't open? <a href="https://snabelen.no/tags/Ban" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ban</a> the <a href="https://snabelen.no/tags/product" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#product</a> outright.<a href="https://www.tarlogic.com/news/backdoor-esp32-chip-infect-ot-devices/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.tarlogic.com/news/backdoor-esp32-chip-infect-ot-devices/</a>

Kevin Karhan :verified:<a href="https://birdbutt.com/@colinstu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@colinstu</a> except <a href="https://infosec.space/tags/discord" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#discord</a> is worse than <a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IRC</a> in every possible way...<ul><li>Simply because it's a shitty <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SaaS</a> that is <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#proprietary</a>, <a href="https://infosec.space/tags/centralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#centralized</a> & <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleVendor</a> / <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SingleProvider</a>! </li></ul>At least IRC allows for <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHosting</a> and way more granular control...

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#proprietary