@MachoManPierreCardin
#calyx og #riseup tilbyder #vpn uden at forlange betaling eller login.

selv hvis man giver dem en donation, så vil det være svært at påvise, at den er tiltænkt som en tak for deres #vpn, fordi de også udbyder alle mulige andre tjenester.

https://f-droid.org/packages/org.calyxinstitute.vpn
https://f-droid.org/packages/se.leap.riseupvpn

Calyx VPN | F-Droid - Free and Open Source Android App Repository

Free VPN Service offered by The Calyx Institute

#Molly app has a socks5 option but only #Orbot "VPN" mode will work. What if #Arti from @torproject could bind with Molly on socks5 via #Termux?

would be nice to have #systemd like @postmarketOS

*Termux @termux
pkg update (possible to plug in keyboard and display to #android #mobile app)
then proot-distro login --isolated debian
su - user because Arti will complain eventhough phone is not really rooted, change etc/resolv.conf to cloudflare, add dependencies needed for #rust rustup and cargo on #debian #trixie, chmod g-w ~/.config

* #Oniux --> E0560

* Arti --> works great. Have not noticed any "anti-effects." Also works on #Alpine / #PostmarketOS in Termux tests.

* apkeep #EFF https://www.eff.org/pages/apkeep --> shared storage path, package manager chokepoint won't install

* network monitoring like Nyx with #tokio-console

In a way, like passwordless root in QubesOS. Some good customizations can be made in Dom0, though, unlike GrapheneOS.
#UbuntuTouch #Brax #Mobian #deGoogle #Tor #Linux #AOSP #GuardianProject #Calyx #Phone #Development

Repercussion, by Calyx

from the album Repercussion / Forever

Critical Music

look, i don't want to bully #grapheneos. everyone be nice! but i'm tired of staying silent while their accounts spew unchecked lies for years, so i'll just say this and then go back to ignoring it again.

in my time working for #calyx / on #calyxos (a time which has now ended), despite graphene's claims to the contrary, i *never* saw anyone from calyx spread or encourage malice toward their project or community or harass them *at all*. if anything, due to a history of negative attention coming from their direction, calyx has long had a rule *not* to discuss their project in calyx's online spaces, but has still demonstrated respect for their OS in public, e.g. at conferences, acknowledging it's a good choice for some.

meanwhile, there has been a steady stream of smears, accusations, and now schadenfreude from their side about calyxos. you need look no further than their official social media accounts for evidence of this; you don't need the "receipts" from me to see the malice. it's all on full display, no background knowledge or rewriting of history required to understand.

contrary to their claims, during my time, by policy, calyx didn't even *look* at their code, let alone incorporate it (apart from some early remnants that are properly attributed, like signing scripts). in fact, with the exception of a weird, random proposal from the founder, as far as i know, calyx never even tried to interact with them whatsoever.

anyway... 4-5 years ago, before i had even finished deciding what OS to use, i was banned from grapheneos's chat channels before even getting around to send any messages - apparently just for existing in the calyx channels - and that made my OS decision easy: i wouldn't use an OS run by folks who'd do something like that. funnily enough, if not for that ban, and subsequently learning more about their behavior, who knows? i may have used grapheneos, just ignored the community stuff, and never ended up working for calyx in the first place.

so, while there were other things that influenced my decision to resign from #calyx, in the end, the biggest were the on-going outrageous behavior coming out of the engineering department, and a failure of leadership to do anything meaningful about it. although i deeply respect the #calyxos team and the many great folks at the institute, unfortunately, until/unless something is done, i cannot support calyx, and i cannot recommend donating to them right now. (9/9)
none of this even delves into the #calyx engineering director's endless gaslighting, predictable derailing of discussions and decision-making, hoarding of access and information, attempts to delay / sabotage the revival of #calyxos, and apparent eagerness to direct $10,000's of member donations toward goods and services from the warmongering likes of AWS and thales. those would warrant threads of their own. (8/9)
some may think, "i don't mind if #calyx moves my name, email, address, etc to vultr. it's not like it's AWS" - or "this is why i never share any personal info that i can't afford to be leaked anyway". but in my mind, given that calyx has hosted its own services for years - VPN, tor exit nodes, #calyxos release server, etc - i think people have come to expect this and to hold them to a higher standard for data handling and transparency. it's your data. shouldn't you know who has it? (7/9)
when i became aware that the #calyx membership site's dns was changed to point to a cloud provider, i had questions, so i did something controversial: i asked. i wanted to know why, and who was involved, and what considerations were made. i emailed the board and anyone else i thought might know more. and i got a response from someone in leadership saying, among other things, "My reading of the privacy policy is different from yours." (i hadn't even mentioned the privacy policy.) (6/9)
if #calyx were going to have a functional, actually-online datacenter managed by its existing engineering department, it would have happened by now. instead, the infrastructure conversations shift seamlessly from excuse to excuse, with minimal tangible accomplishments in *years*, and the powers that be *just don't care*, despite virtually all calyx workers complaining that the lack of progress - and the technical excuses for it - make no sense. (5/9)
one day in july, after years (or nearly so) of the engineering dept failing to address known problems with the membership server - which is the same story as almost every other #calyx server - finally it "crashed", and they seized on the opportunity to migrate it to ~the cloud~, "temporarily", until calyx has its own new metal to put it on. but without a leadership change, that's never going to happen... (4/9)