good luck cancelling commands after rebinding Ctrl+C. it sounds like a good idea, but it isn’t. Ctrl+C/V is acting differently in the terminal for a reason.

most terminals have bindings for Ctrl+Shift+C/V, though!

This is likely to have every one of your logins, not just a single login that may or may not be used on other sites, but the specific username and password and which site it’s associated with. On addition to access to those accounts, this links all of your accounts to a single identity which companies spend billions to do with advertising IDs, cookies, embedded scripts, and lots of other, usually shady, practices. This is a gold mine, though usually only for one or a few users, so generally not a major target unless you’re being targeted personally for some reason. So, even if they don’t get the passwords, they’ve now linked every account you have on every site to your identity.

afaik everything is encrypted. not like a big blob, but the properties of items are encrypted separately, if the encrypted export format has anything to do with the database structure

How about fixing the bugs so they’re not there to report? That’s the real “unpatched hole in the floor.”

but spam will still come, making it harder to find the occasional honest bug report. and then there are feature requests and other things too.

sounds dumb. if they were using github issues, then they would have lots of junk issues instead, and that too would be overwhelming.

It should at worst give people a copy of my media if there’s a security issue.

that’s not the worst possibility. the worst possibility is an RCE into your server.

Personally I went out of my way to make this be the case, i have my instance locked into an unprivileged lxc whitelist only on syscalls which took a while to figure out the minimum needed for function but

that’s a pretty exotic setup. Exciting, but for most people learning to manage a VPN is easier

It should at worst give people a copy of my media if there’s a security issue.

that’s not the worst possibility. the worst possibility is an RCE into your server.

Personally I went out of my way to make this be the case, i have my instance locked into an unprivileged lxc whitelist only on syscalls which took a while to figure out the minimum needed for function but

that’s a pretty exotic setup. Exciting, but for most people learning to manage a VPN is easier

until you have a choice

retire

lol

we are not going to retire

but you present your “wide populace” fact without giving sources too

my statement is not that many people are using passkeys today. but that if there comes a time when many people will use passkeys, they will be as careless and convenient as they are with everything else today, accepting any restrictions, because “why would anyone not use Google Passkeys? It’s the most convenient thing!”.

and not only that. I was talking about device locking but that’s only part of the problem. isn’t it that passkey receiving services can identify the client software, and decide they will only accept passkeys from x and y clients?

this seems to be a heavily vibecoded project, the readme has at least one contradiction and weird statements and formatting.

I mean now is it clicking ads or is it not? and what’s the reason for including the “tech stack”?

It’s on fdroid

edit: oh you just edited it

not half of that is true.

wait, did Godot enshittify?

what were the questions to which they gave those responses? It’s really not clear. link the source.

element was very buggy a few years ago. the new clients are just now starting to get feature parity, and in my experience calls are still quite unstable, requiring your server to have some specific additional setup (which most public registration instances don’t have), besides that not a lot of clients have implemented yet MatrixRTC calls. even the client list on matrix.org is only showing whether a client supports the former calling system.

so for the layman it’s definitely not production ready yet. and even for new tech literate users some of the things are still challenging to figure out.

but it’s so much easier to grab torches and pitchforks than to read an announcement

except when the wide populace starts accepting it being device locked, and your opinion does not matter anymore to those making the decisions

namely the VC funding and the huge resource hungry clients to me

why $(pwd) instead of just . ?

good news for those being locked out of their data by one of the faulty windows 11 upgrades!