With all due respect, on the point of developer or tech savvy aspect, why won’t researchxxl publish his dev profile, complete the f-droid reproducible build, publish your and researchxxl’s public signing key, and IDK, the communication being silent is weird. Also whats about the issue that starts with “dont play with my desktop“ implying hacker getting into your computer, which info are correct?
the dichotomy of one big changelog vs many releases notes (Aves in contrast to, standard notes), i get it. what i dont get is the communication going silent. IDK anymore about cryptography, but Linus has his rage over email listing
OutOfTopic
(east bloc diverging from west bloc linux codebase [no idea about NK linux distro], Unicodia stance is fine, i like his approach since its linguistic, but it’s also not possible without neologism since u s spellings are more lingua franca than uk-en right now as su per po wer, but it’s a fine approach, linus is also justrified, since he lives in the u s, the agency is on his thr oat, and it will also jeopardizes the whole internet stack, so diverging east bloc and NK linuxes are fine, harmonyOS of chi na will probably help br ic tech stack or something similar, the xkcd comic of standardization)
OOT, and your silence. other could chime in, with the cryptography aspect, sorry for the comment, this is my main syncing app, so this is why this sounds urgent, and defensive, or just usual “reproducible build”, public signing key gpg verification, ways of devs to legitimate apps, confirm pdf, email. I might not produce any of this cryptographic app release aspect, but I do have keepass + syncthing workflow;
so I have researched cryptography before, but yeah with all due respect this is out of my scope, I’m gonna go with nel0x or martchus for now. this is kind of similar to how the linux codebase diverge after the triple a agency knock on linus door, so yeah at least this one doesn’t get that much coverage.
To compare even though abrupt, the forks and original devs communications are better in picocrypt vs picocrypt-NG, no silence, the og dev is kind of fed up with neural network but thats a different story.
DivestedOS went EOL, Ironfox and AXP OS for android take some of the projects into a new fork but with new names. havent see dialogues between them, but the divestedOS dev is live again with commercial profile, old repos archived.
while picocrypt will probably use his trademark for commercial release but still allowed picocrypt-NG to exist and provide FOSS community with a fork release. something like tachiyomiSY existing even tho Mihon exist, also because of QoL or features differences.
answering this might strengthened your defense/clarification, but it’s your decision to answer or not.
making an exhaustive chronology since your last commit up to researchxxl commit or dialogue might make this clear. I really dont get why you dont take picocrypt or divestedOS approach, archived repos, but still let others make fork of your work?
- f-droid reproducible build,
- maybe github version of token or public signing key (gitlab asymmetric key needs to be made if one made gitlab acc from github acc, similar to token) to prove the legitimate handover of catfriend1 to researchxxl repo, (maybe an ignorant assumption from me, CMIIW)
- the full chronology why catfriend1 account is gone,
- last commit of yours up to researchxxl first commit chronology?
email or pdf gpg are out of scope. those 2, 3, or 4 questions are probably enough for clarification.