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!
yeah. but in my experience, what’s worse is people just have a hard time using it. especially when they only need it rarely and don’t have the need to learn it. and it doesn’t help that it’s redesigned every year.
its just as usable with KDE, but depending on distro you might need to install the server part yourself.
but also these are LAN only solutions, and VPN. for actual remote access you have to forward ports but I wouldn’t do that for risky things like that. Instead use rustdesk, but even teamviewer would be a better idea
rustdesk
not really a problem. it stays unlocked, and for when she occasionally needs to log in again it will be printed on a paper
that’s not the worst possibility. the worst possibility is an RCE into your server.
that’s a pretty exotic setup. Exciting, but for most people learning to manage a VPN is easier