they could be doing that already, throwing away messages that contain certain words

just bother to look around?

java: try-with-resources, AutoClosable

java: try-with-resources, AutoClosable

lol wtf, I don’t know what is the post about but you have worked hard for all these downvotes. here, take mine

Voting doesn’t matter

voyager keeps a local count, it helps to tell apart people who frequently talk like you

So fuck everyone.

thanks, you too

you don’t request the permission from the teacher though. It’s a school policy and a teacher likely cannot overrule it anyway. you request the permission from the principal or the school psychologist, or whoever deals with kids special needs.

yes, git is a godsend. but who will you trust that they checked the new code, and found nothing bad? different people have different expectations too.

have you ever used Gentoo? if you do, you know how long it takes to build updated software from source code.

vetting all that, even just the changes would take a lot more time. and it’s a constant effort.

that’s not “alive next to it”. you can’t see both at the same time

When I open nheko, a dialog box says “Activate encryption”; “to make this device trusted {blah blah blah}” with a big “Verify” button. Pressing it does the same as closing the dialog, so a whole lot of nothing. Same right now. I did try logging out and back in on different devices, back then only though.

I don’t use nheko, I think it should have shown a menu saying something like “waiting to accept verification request”. thats what other clients do.

did you have any other client opened on another device when you pressed verify?

I’m surprised the kernel anticheat didn’t autoban you right away starting the game

back then there was no AI like these, but otherwise yeah

Personally I tend to avoid running untrustworthy programs outside of a sandbox or VM.

what does that mean? are you not running any programs at all? you cannot know just by looking at the name if a program reads such sensitive info. and its not unlikely that some developer figured it would be a good idea to include it in automatic crash reports

yes, this is sensitive information. its like your fingerprint, you cannot change it. I think its quite obvious. web browsers firefox is fighting to hide more and more that even indirectly could lead to identification. websites can’t read this ID, this is just a comparison.

Like, right now for me, nheko and Element say everything is unverified but fluffychat says everything including itself is verified.

its not desynced, it is just not presented well. I think when it shows whether another device was verified, it actually does not show if you have completed verification of that device on your account, but instead whether that device is trusted by the current one (for purposes of sharing keys and whatever). in short, it’s not “the user account trusts the device”, but “this device trusts that device”.

when you verify device A with device B, they will mutually trust each other. if device B already trusted devices C and D, device A will immediately start trusting them too.
if you then log in on device E and you don’t verify it with any of the others, it will basically form a distinct “trust group”.

in your case it seems there are also cases when device A says it trusts B, but B says it does not trust A. how long ago did you verify your nheko, element and fluffychat devices? it looks like their verification could not complete, maybe one of them had a bug at the time or crashed before properly saving its database.

both issues won’t solve themselves automatically, you will have to verify the unverified device again. or if it does not work, report the problem with logs with the function in the app, on both sides.

Not Element Classic, I meant aTox (Tox for Android). It still functicryptosystem

I see. tox seems to be faring worse in security. in matrix, encryption is optional in the protocol, but it’s built on well studied cryptosystem. so far when it fails, it’s people not being able to read messages they should, not unexpected people being able to read messages. and that’s because of flaws in key distribution.

in tox, it seems encryption is mandatory, but they roll their own cryptosystem. and their cryptosystem has flaws that nonexperts commonly run into

Jason Donenfeld, wireguard creator to expert:

I think when your homebrewed crypto protocol falls to basic crypto 101 vulnerabilities that modern AKEs are explicitly designed to prevent, it’s time to pin up the red banners telling people not to use your stuff.

https://github.com/TokTok/c-toxcore/issues/426

downvote was not me.

you are wrong. people would buy it without thinking twice. also, it doesn’t need to be obvious, anything could be hidden in an additional package that looks like the other memory chips on the stick

that’s not even true. they are trying to follow the latest tech giant design trends making everything with huge gaps, rounded corners and huge memory usage, and the ui lagging more than anything 20 years ago

I’m experimenting with AI-based live transcription (eww, AI, slop, I get it) but it only works real time with English at the moment.

the real problem there is not AI slop, but if you are basically uploading their voice to a company. if you are doing it locally, I would say fine. LLMs are better (not flawless) with translation than facts.

Yeah but XMPP sounds so techy you know.… /s

the trick is to not mention XMPP to the end users. if they dig deep in the app settings they can find it out, but otherwise all that end users need to know is just, download the app named conversations, and use this domain and username. the domain could likely be hidden from them by deep linking, and sending the link in a company email. then they just need to log in as anywhere else.

what security dialogs? and what race conditions? do you know what that means, or are you just throwing around words?

if you mean the “verify your new device” dialog, yeah, it has a problem. it won’t appear most of the time on clients that were not open when you sent the verification request from the new device. I don’t know why, and this is not comfortable, but then I can start verification from a device I already have, and it will work. or I can also just fill in the password from my password manager, which you surely have too.

but I haven’t seen other problems with it recently.

XMPP at least functions reliably, if you ignore all of the protocol extensions and use it like IRC with images of course.

which does not even have a bolted on security that way.

Though the main and only good Android client got archived.

calling element classic good is a bit of a stretch. it was very slow.

the process started a bit earlier. people were already complaining what they do despite their motto