dice.camp is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for RPG folks to hang out and talk. Not owned by a billionaire.

Administered by:

Server stats:

1.7K
active users

#toldyaso

1 post1 participant0 posts today
Replied in thread

@signalapp no it's not.

Being a #centralized, #SingleVendor & #SingleProvider solution subject to #CloudAct makes you inherently vulnerable by your own choice and thus trivial to shutdown compared to real #E2EE with #SelfCustody of all the keys and true #decentralization as well as #SelfHosting (i.e. #PGP/MIME [see @delta / #deltaChat et. al.] and #XMPP+#OMEMO [see @monocles / #monoclesChat et. al.]!)

And don't even get me started on you collecting #PII (espechally #PhoneNumbers) for no valid reason, (thus violating #GDPR & #BDSG)...

But yeah, I'll be patient to shout "#ToldYaSo" to your annoying cult of fanboys!

Replied in thread

@dalias I sincerely disagree because none of my claims got debunked and no evidence against #XMPP+#OMEMO have come up to me as of today.

I hope to be proven wrong, but up until now I've always been at the position of saying #ToldYaSo!

@lauren

You know what's sickening to me is when someone asks for my #honest and #professional advice, knowing that it is grounded in #experience and #knowledge just to knowingly disregard it and then come on #whining when precisely happens what I predicted!

It's just fucking disappointing to me, cuz there ain't any valid reason to spitefully disregard my word.

  • Espechally when I'm willing to go over all the painpoints and address any issue.
Replied in thread

@GrapheneOS Well, you've to ask #Google and #Fiarphone that and consider invoking #Regulators like @EUCommission, @kartellamt@social.bund.de and others in that matter.

Which again proves my point:

  1. #AllGAFAMsAreEvil and NOONE shoud've ever trusted them with anything!

  2. The #Android ecosystem is fucked up and there is a need for #vendors to refuse to bow before #Google and actually do #secure & #repairable devices.

Again: You seem angry at the wromg person if that means you're angry at me.

The question to me is how is #GrapheneOS gonna go about this?

  • Cuz we both know Google can afford to go "maximum asshole" on you [the Grpahnene OS Project] and even in the worst case their legal department won't even notice this whole shitshow even if miraculously by the wounders of everyone from @eff to @fsf to @noybeu and @CCC forcing Google to literally support and endore GrapheneOS, because by the time any binding court ruling would be enforced, Google would've choked the project out of the market.

So my question is when will you get forward and work with other #vendors instead of tying your project to Google-specific and thus sorta-proprietary implementations?

[...] Pixel targets have a lot of device-specific hardening in the AOSP base along with some in GrapheneOS which needs to be ported over too. For example, various security features in the kernel including type-based Control Flow Integrity (CFI) and the shadow call stack are currently specific to the kernels for these devices. [...]

To me that sounds like some very serious #VendorLockIn you're stuck in, and now it bites you in your rear...

I hate to say it, but #ToldYaSo sadly happened!

I guess you gotta have to bootstrap it from scratch starting with #toybox + musl / #linux sooner or later...

Not to seem like an asshole, but I do sincerely wish GrpaheneOS and it's team only the best of luck and that the issue gets fixed sooner than later, because this #Vendor #LockIn is a major issue [and yes I do blame the Device Vendors that shit out unmaintained garbage] so unless you can afford the legal cost of actuall enforcing #EU laws re: #SecurityUpdates and force Vendors like #Fairphone to actually follow their claims re: #Security and #Updates, this won't move anywhere.

  • Yes I know you don't have that money and I don't expect this to be the case!

I do however also don't expect you to find a magical solution. My point is that there needs to be a change of strategy, and relying on Hardware you neither own nor control in the sense of Stakeholding isn't going to provide you with the necessary stability.

  • Because Google is a [pulicly traded] #Corporation and Corporations are explicity nobody's friend!
GrapheneOSGrapheneOS build documentationBuilding instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
Replied in thread

@moehrenfeld ist keine #Desinformation, sondern #UnbequemeWahrheit dass ale #zentralisierten Lösungen shice sind!

Wenn @signalapp #Datenschutz und #Sicherheit erst nehmen würden, würden die dies garnicht erst tun!

  • Aber glaub' was du willst, wenn die shice den Leute um die Ohren fliegt wie #EncroChat und sich wie #ANØM als #Honeypot herausstellt werd' ich da sitzen und "#ToldYaSo!" rufen!

Und solange #Signal eine #SingleVendor & #SingleProvider - Lösung ist wird dies anfällig sein, denn aich @Mer__edith wird eher snitchen als Knast riskieren...

Twitterthaddeus e. grugq on Twitter“I’m gonna tell you a secret about “logless VPNs” — they don’t exist. Noone is going to risk jail for your $5/mo https://t.co/Q2aOQJkG4g”

@Walker @DivineKestrel @bsi #NotLegalAdvice but to me that #risk alone makes #Windows in general a non-starter...

It's also not that I want to brag, but I always #ToldYaSo to everyone that #Windows11 will be even more incapable to comply than #Windows10 with #GDPR & #BSDG.

  • And that's just in the regular context of an average #SmallBusiness that writes invoices and prints shipping labels and has to file taxes and do accounting.

  • Don't even get me started on anything #confidential containing #PII or #MedicalRecords...

In fact, I'm convinced a lot of places I know will now frantically call up their lawyers and when those refuse to put their career and livelyhood on the line they'll get real panic and be forced to migrate away...

  • I wished I could go into more details but I've to abide NDAs that won't expire, so I guess I'll be busy taking inbound calls for help soon...

@SheDrivesMobility @bmdv also ich glaube dass bei solchen Bullshit-Aktionen die Gefährliche Eingriffe in den Luftverkehr darstellen die #VorhersehbarenKonsequenzen kommen...

  • Das ist nur minimal weniger shice als sich aus Protest gegen #Diesel-RTWs und NEFs vor ne Rettungswache zu kleben; Allein die enormen Mehrverbräuche an Treibstoff und Mehrkosten dürften für jene ne Privatinsolvenz nach sich ziehen...

Das einzige was passieren wird ist dass jene*r Schichtleiter*in der Security und Sicherheitschef*in daraus nen Strick gedreht wird denn gem. #IATA & #ICAO-Standards hätte keine*r von @AufstandLastGen auch nur ansatzweise in den Perimeter eindringen können dürfen, geschweige denn auf Rollfeld und Landebahn...

Für mich wirkt das was #LetzteGeneration abzieht mehr und mehr nach #AgentProvocateur um ne Steilvorlage zu haben damit #Proteste kriminalisiert und #Massenüberwachung legitimiert werden kann!

Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)@AufstandLastGen@climatejustice.social Na dann, viel Spaß mit den #VorhersehbarenKonsequenzen... - *Gefährliche Eingriffe in den Flugverkehr* ist nicht witzig und alles was dies erzeugen wird sind #NoFlightList-Einträge bei #IATA-Mitgliedern, #Regressforderungen vom Betreiber und Airlines sowie Passagieren und Frachtkunden... Ich garantiere euch damit bewirkt ihr noch weniger als Jackass beim Pissen gegen Turbinenabgasen... - Aber okay, das habt ihr euch halt überlegt undneuch entschieden... Mal sehen wie die #Flughafen-Feuerwehr und #Bundespolizei euch vom Asphalt entfernt... - Ich könnte mir vorstellen dass die notfalls euch eiskalt runterreißen... Macht' nur nachher kein #Mimimi weil's #Aue macht, weil das ist genaimuso vorhersehbar wie Handschellenklicken und/oder Faustschlag ins Gesicht wenn Mensch versucht ne*m Polizist*in an die Dienstwaffe zu packen...