Client side TLS certs are basically the same stuff and it works nicely. Too bad they didn’t improve on that. My guess is that the big boys want to handle it at application layer.
Client side TLS certs are basically the same stuff and it works nicely. Too bad they didn’t improve on that. My guess is that the big boys want to handle it at application layer.


People also don’t understand IP, TCP, DNS, TLS etc. and yet can use programs that use all of that. I find e2ee still pretty cumbersome in the long run.


I read the post, its very exhaustive and future seems promising. I might have missed the section but why it this separate mechanism needed in the first place? Is it just because of the key lifecycle management? If so, naiive approach of publishing public key on your profile falls short because of this and without public key management everything falls apart sooner than later?


Google resells their search ad buys to middlemen that then place web ads of the lowest quality across the web. Its a few billions worth industry. I briefely worked for a company in that “value” chain.


its not private, but its FOSS, it has great mobile&desktop client


I still see master branches everywhere, even my new personal repos. This git renaming story is one of the most stupid OSS pushes I remember. That and Gimp fork, that then died out I think.


30×50=1500, 50 tests per day is a lot. That is a lot to read and understand all the edge cases, let alone writing them.
Agree with this explanation. Also in a monorepo it’s much easier to reference code between modules and I think this leads to too much coupled code. It takes more discipline to limit the scope of modules.


I hope we see induced demand for labour in the end. Worst case would be higher workloads for everyone.


Android offers it in settings. Parental control and digital wellbeing says it on my phone. I have it set for all social apps.
labwc has it :) I use it with XFCE, integration is pretty rough but will hopefully get there over time. No crashes so far!
If I have to cross reference info from two windows I like to have one floating and always on top. In that case its nice being able to roll-up the window to see whats behind it. Minimizing would be similar but it feels more permanent than rolling up.
So there is no shading on KDE Wayland? This feature works in Labwc. Death by thousand papercuts…


Google itself. GrapheneOS bridgea the gap but still…


No, there is no modern smartphone like that, yet AFAIK.


I understand security implications but I’ll be getting Fairphone 6 with /e/OS over Pixel with GrapheneOS. For me FOSS ranks higher than HW security features, and buying Google device goes against FOSS principles.


Its nutjobs like them that are pushing progress further. State security apparatus doesn’t want to work by law. That can be observed worldwide.
French went after Telegram even though it doesn’t market itself primarily for security. It was just that some public channels went against their strategic objectives and they felt the need to bruteforce their way.
So GrapheneOS is very right to be nervous and pack their bags before they come knocking at the door.
Is your B point properly addressed by Passkeys? With all this talk about export I presume not. Client certs seem abandoned, you can’t use it on mobile.