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?

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!

there’s a bunch of improvements too

wow, that fluent search is basically the kde plasma’s app launcher

ironfox is not a brand new browser, but a soft fork like librewolf, always kept up to date. what it removes is the garbage google components, nothing useful is removed as I know. it even has a couple additional settings related to privacy, and Unified Push support for some reason I could not yet figure out

which I presume is nowhere close to feature equivalent to Firefox.

why do you presume that?