I don’t believe it’s possible for a CA to decrypt TLS traffic with their private keys. They sign a site’s public key with their own private key after verification but are never given the private key itself. Public CAs only provide identity verification, they do not take part in the encryption process itself. Let’s Encrypt is perfectly safe in that regard.
I run Lemmy, Plex, and a bunch of other services from a desktop in my basement. It works great. The Lemmy docker setup is a little finicky but works well once you get it.
Digital assistants are good for timers, turning on smart lights, and sometimes playing music. None of those things require a large language model to spit random text back at me.
There are quite a few creators who are primarily funded off patreon and release content to YouTube. I imagine a group like MCDM (Matt Colville) who has patreon, merch, crowdfunding, and products doesn’t really care about ad revenue.
I disagree. Each distro is a user of a thousand different open source systems. When a distro developer integrates gnome, systemd, bluez, or whatever other system they’re finding, reporting, and possibly fixing bugs that end users might miss. Other than arch users, who else is compiling these things from scratch and really digging into the documentation?
Here’s my guess.
I’ve never seen side mounted USB-C and HDMI before. It’s a neat space saving idea, I wonder how their mechanical stability compares.
Doing this by hand is challenging but possible.
First you need a hex editor, not a text editor. xxd on linux will get you started but you might want something a little more user friendly.
Then look for a label for a value you know, xxd and other hex editors will show ascii text on the side. Hopefully you’ll be able to identify the value (in hexadecimal, probably 4 bytes but could be 1, 2, or 8 as well) somewhere before or after the label. You might have to get familiar with endianness, two’s compliment, and binary floating point before the numbers make sense.
Once you know how to read a value after a label you’ll need to find some label for the information you don’t know. If it isn’t displayed in the program it might not have a super readable label.
Distributed but high trust.
Zero-trust blockchain tech has no value. There is no such thing as a zero trust system in real life.
Except blockchain solves no useful problems so you will never find it behind anything that isn’t explicitly using it for marketing.
In case anyone hasn’t seen Folding Ideas - Line Goes Up. He gives a great overview of the history of crypto and is worth every minute of the 2 hour run time.
Plus he isn’t a crypto bro like OP here.
The default mobile web view literally has sidebar at the top of the page when viewing a community. If your app is missing a basic feature you don’t get to complain and be a dick about it.
I don’t believe so. I’m not sure what their long term goals look like.
There’s no need to run an LLM on the same system it was trained on. Once the model is built it contains all the information already. If you want a model to live on long term you would just release the file(s) publicly, like hugging face does with theirs, then anyone could use it or host an interface for it.
Your instance would have connection logs for whatever browsers or mobile apps you used, but other instances talk directly to yours and know nothing about you. So use an instance hosted in a jurisdiction you’re comfortable with or like you said tor or another basic vpn is plenty to anonymize you.
Lemmy federation only starts when a user on your instance searches for and subscribes to a community on another one. So unless a user on your instance goes searching for cp it’s not really an issue.
They also host their own f-droid repo if you want one built by the developers and not f-droid. https://fdroid.fedilab.app/repo/
Nope, I’ve seen nothing firm about them doing or not doing it, but OP asked about current information and at the moment they are open source and do not have a standards document.
As it stands I wouldn’t jump on AT for a project of mine and wouldn’t recommend it as a superior protocol on those grounds.
So when Bluesky introduces a new feature or a breaking change in the protocol anyone downstream will find out when it gets pushed, maybe a little ahead of time when it comes in as a pull request. Bluesky goes live with the change immediately, maybe in a public beta channel, maybe straight to prod, depending on their testing setup. Anyone running a bluesky compatible server becomes immediately incompatible until they rush to implement the new changes. The best user experience will be had on first party servers, driving the vast majority of users there.
For a standard defined protocol, like ActivityPub for example, to introduce a change like that it would first go to the standards comittee where it would be discussed publically with stakeholders. The changes would be published and then all parties would begin implementations at a pace that makes sense to them. It’s like when you hear about new Wi-Fi versions several years before any devices actually support them. One group doesn’t just get to come out with some crazy new change that everyone else has to reverse engineer and then race to keep up.
What Bluesky is doing might be fine and make sense for their model, whatever that may be. I just want to point out that there is a difference and it drastically changes what the future of the service will look like.
Very cool combination. How are you managing single sign on with all those services?