aspiring Rustacean, JavaScript jockey, 3D printing addict, use Arch Linux btw, Apple-captive, Google-captive, Meta-escapee, parent, spouse, cisgender, he/him
- 26 Posts
- 28 Comments
I’m currently using Signal, and happy with it, but they still don’t have reproducible builds, making it impossible to confirm that the code we can read on GitHub is actually what is running on my device
So, even now, it could be doing something that isn’t able to be audited
I guess Element/Matrix or Briar are the better options from this perspective, without losing any end to end encryption
Can I ignore flatpak indefinitely?
Sure, at least until software you want to use is flatpak only, e.g. Bottles
I agree that there are much bigger problems, but those bigger problems have solutions that are not allowed under capitalism and USA imperialism, so labels is all we’re allowed to fix 🤷
The legal drinking age in Australia is 18 years old, and it has always struck me as odd that it’s so high in the USA
Australian sports fields are covered in alcohol logos So the entire time you are watching football with your children, they are exposed
Ban all advertising for alcohol, too, please
Planet America, orbiting the American sun, in the galaxy called America
The whole thing is weird and the CEO especially so, and not weird in a good way: https://d-shoot.net/kagi.html
https://www.partykit.io/ sort of? maybe?
Gosh darn it I only just onboarded to Omnivore a few months ago Now I guess I need to find a new place to store bookmarks
One example I can think of is Widevine DRM, which is owned by Google and is closed source: https://en.wikipedia.org/wiki/Widevine
Google currently allows Mozilla (and others) to distribute this within Firefox, allowing Netflix, Disney+, and various other video streaming services to work within Firefox without any technical work performed by the user
I don’t believe Google would ever willingly take this away from Mozilla, but it’s entirely possible that the movie and music industries pressure Google to reduce access to Widevine (the same way they pressured Netflix into adopting DRM)
For disappearing messages to work, your conversation partner has to promise they won’t take photos of their screen, and they have to promise to use an app that actually implements the feature instead of just pretending to, and the app developers have to promise to have implemented the code to delete a message when the service says it should
Is there actually a cryptographically-sound and physically-complete method for ensuring that a message is only legible for a temporary duration once it leaves your own device and is delivered to someone elses?
Hmmm, is CloudFlare known for being a bad actor in terms of privacy?
Setting that aside, no matter what you pick, you’ll be exposing your IP address, from which your ISP and/or general location may be derived
If you don’t trust CloudFlare with that information then you basically cannot trust anyone else, so maybe you’d need to run your own service and ping that instead now that you’re in a situation where you can only trust yourself 🤷
The other issue that comes to mind is that you’re only testing reachability to one address, which means you could get a false negative where that address stops working but the rest of the internet is actually fine
Without being specific, I’d try to get something with firmware updates available on LVFS: https://fwupd.org/
And you might want to check for distribution specific notes on that model e.g.
- https://ubuntu.com/certified/laptops
- https://wiki.archlinux.org/title/Category:Laptops
- https://linux-on-laptops.com/
- https://www.linlap.com/doku.php
If Wayland is more important to you than AI/ML/LLMs then you probably don’t want anything with an nVidia GPU
We need a verified check-mark for true wayland users :P
I did actually do this already, separate from working on this issue, but can confirm the intermittent problems with the combination of wpa_supplicant and systemd-networkd
I’m not an expert, but my understanding of the Global Shortcuts portal is that it’s very much designed for the push-to-talk use case where an app is not focused but still receives button events for exactly the keys its interested in and no other keys: I think this would cause problems if an app requested every key (e.g. if the request was approved then no keys would work in every other app)
It’ll be interesting to see how the remaining compatibility/accessibility issues are tackled, either in portals or in wayland protocols
Yeah, that’s going beyond the software and making the physical supply chain possible to validate by a sufficiently equipped and educated consumer
The trade off here is that it’s very difficult to produce verifiable circuitry that is also fast