#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 --> Linux Scaffolding Log_Connections

* 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

🇺🇦 #NowPlaying on #BBC6Music's #The6MixWithMaryAnneHobbs

Calyx:
🎵 Repercussion

#Calyx

https://criticalmusic.bandcamp.com/track/repercussion

https://open.spotify.com/track/5QwzglOoJYJodaed3ExhUr

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)

the idea of #calyx moving its infrastructure to ~the cloud~ was a recurring proposal from the engineering director for years, but it had been opposed by the founder, the board, and most staff, particularly for cases involving personally identifiable information. if such a data transfer were required, most of us would have insisted on either getting explicit member consent or - at minimum - notifying in advance. the eng director apparently found such positions unreasonable. (3/9)

in july, the #calyx institute membership server - members.calyxinstitute.org - was quietly moved from a server owned and operated by calyx, to a cloud hosting provider, along with all associated member data (personal information). from what i was told, this decision was made by the engineering director, the executive director, and the board. (2/9)

"My reading of the privacy policy is different from yours."

i want to elaborate on why i left #calyx / #calyxos. (everything in this thread is my opinion or interpretation.)

while there were many factors, the breaking points for me were a non-consensual transfer of members' personal information to a third-party server, a total lack of notification, and a ridiculous defense. the following messy posts will continue my perspective and recollection of this particular event. (1/9)

Calyx & TeeBee - Pure Gold (Feat. Kemo)

🎧 https://www.youtube.com/watch?v=fs5jbHHd59E

Info: https://www.discogs.com/master/485781-Calyx-TeeBee-Feat-Kemo-Pure-Gold

Info: https://www.beatport.com/track/pure-gold/20058553

#Music #NowPlaying #Electronic #DnB #DrumNBass #MusicVideo #Calyx #Teebee #CalyxAndTeebee

@mason

allegedly, and from my perspective as a former calyxos employee (i do not represent them)...

the founder was the keeper of the signing keys, and has stated this publicly. when he separated from the institute (which is a whole other story), he didn't give the signing keys to the institute in a timely manner, if at all. although there was no evidence that the keys had been compromised or accessed from outside the organization, there *was* reason to believe that they had not always been handled in a secure manner (which is yet another whole other story). also, because these were key *files*, and probably not even protected by passphrases (but i don't know), copies were always *possible*.

the OS team decided to only release updates signed with *fully* trusted keys going forward, that were not subject to unauthorized copies. the OS team has been working on a hardware security module-based solution for signing. the exception to this was one last update to inform users about this situation, to the extent permitted by comms folks. this was facilitated by eventual cooperation from the founder.

that being said, i do not myself believe that there is any actual risk today associated with using a build signed with these older keys, apart from it not having the latest updates. but i also support switching to new keys that are better safeguarded, and i can't guarantee there wouldn't be a risk associated with these older keys in the future.

there is more to know as well, but too much to write here. still, it is false to say that the calyxos team doesn't want you to know this.

source: i worked on #calyxos while all this was happening. i no longer work for #calyx. and this is all just alleged, based on what i experienced and was told. i never signed an NDA 🙃

on september 30, i stepped down as a developer for the #calyx institute.

i am proud of everyone on the OS team, who all pulled together and showed so much dedication to #calyxos and its users, despite the last few months' challenges.

still, in my opinion, calyx has a lot of work to do to rebuild trust, both inside and outside the org. i have a few starter ideas: listen to your workers. act swiftly on bad behavior. and don't shield the men who engage in it from consequences. ...repeatedly.

i'm so tired of it. people deserve better.

¡Atención usuarios de CalyxOS!

La plataforma no va a recibir actualizaciones de seguridad por hasta 6 meses. En el enlace está el comunicado oficial.

https://calyxos.org/news/2025/08/01/a-letter-to-our-community/

#Calyx #CalyxOS #Android

got my new hotspot from calyx in the mail! yaaaay! i think they maybe turned off the spigot to my old hotspot a few days ago, because i have not gotten any internet from it for days. so i'm very happy to have proper internet again and looking forward to years with my new lil buddy hotspot 🥂

if you're not familiar with calyx, you pay a yearly fee and get unlimited wifi via mobile hotspot: https://calyxinstitute.org/

#internet #calyx #wifi #tech

So a few weeks ago I switched over to #GrapheneOS. I am a long time #Calyx user (and supporter) and I understand the position that they're in... I just cannot go six months without security updates (and stock Android was not an option).

So far, it's been a good experience and I'm hoping that Graphene will be a solid replacement for Calyx. I wish the Calyx team well, and I enjoyed it while it lasted. For now, I'm with Graphene.

https://grapheneos.org/

Question: Does the dutch digital wallet app #yivi run on #e_os, #calyx, #lineage, #graphene_os etc?

#privacy

This week in #FDroid (TWIF) is live but late to toot:

* Slow updates? There's a reason, or 2️⃣
* Don't be surveilled, engage in our research 🔭
* Using #Calyx #CalyxOS? Read now! 💔
* #DeltaChat hits v2, #ArcaneChat soon™
* #NeoStore finally upgrades to Index-V2
* #NewPipe in your 🚗 ? Maybe...
* #Wesnoth is back 🐴 ⚔️
& 164 more updates
- 4 apps archived

Saturday reading break: https://f-droid.org/2025/08/07/twif.html