Simplest is use /etc/hosts to set up names, if there are just a few.
Simplest is use /etc/hosts to set up names, if there are just a few.
I mostly notice it in the feed, not sure about other places. I’ve just give back to jerboa from Voyager now that I have a new enough phone to use jerboa again.
Yes, remove the thumbnail and expand the text into that space. Sorry for the confusion.
The options I see there are card, small card, and list. All of these show the thumbnail. This is in 0.0.65 currently on f-droid. Is that not expected?
No a lot less, twilio is $1/mo, see also VoIP.ms and vitelity.net
deleted by creator
If we told just anyone, it wouldn’t be private!!!
Srsly any phone app is inherently insecure because the phone itself is insecure. And there’s lots of metadata leakage, like the phone broadcasting its location. There is no “go to app”. It all depends on what you are trying to do and who you are trying to communicate with.
If this is for live disks or mirrors (not backup), LUKS is reasonable. Backup is different from mirroring since one of the things it protects you from is accidentally deleting files. If you delete a file from your main drive, it also disappears from the mirror drive, so mirrors are not backup. For encrypted backup, I’ve been using Borg backup which is quite well thought out, though confusing at first. The backups go on a remote server which is ok since they are all encrypted.
You mean the blog link? That’s an awful lot of articles. Is there a single sentence somewhere saying what it is?
What is the project anyway? It’s not obvious at all.
Dang, FSF shop temporarily closed. https://shop.fsf.org/
The PFS comes from deleting the secret DH parameters after you are done using them.
The codecs are built into the client (I’m using linphone) and they all sound like crap. Provider is vitelity.net but I have a twilio account so could try that. Also, they only work at all when the phone is online by wifi. Using the phone’s mobile data is total fail. Too many dropouts etc.
This forwards to an (oh the irony) blogspot post, https://articlesgallery8543.blogspot.com/2023/10/lets-decentralize-web-together.html It encourages people to move off sites like facebook towards sites like lemmy. Great but I think we knew that already.
Voip call quality is terrible, it is near unusable over mobile data IME, it adds latency etc.
I guess an intermediate measure might be to make all your phone calls through a forwarding proxy (e.g. implemented with Twilio API) so that all the mobile carrier sees is that your phone calls all go to the same number. Similarly you’d give out a VOIP DID number that forwards to your mobile, so all your incoming calls would appear to come from the same number.
About a year ago I found Osmand near unusable. Maybe I should try it again. I currently use Organic Maps and it’s pretty good, though it’s missing a few basic features that are probably on a todo list. Also, some of its data is wrong. I expect Osmand uses the same wrong data. Unfortunately last time I hit an error, I had no internet, but will try again next time I’m there.
Don’t know about Signal but the way PFS usually works is there is something like a Diffie-Hellman (DH) key exchange. Each person generates a random (private) number, remembers it, crunches it mathematically into a public number, and sends the public number to the other person. Each then combines their private number with the public number that they got from the other person, and this (because of how DH works) cleverly gives both people the same secret number they use for the encryption, but the secret can’t be reconstructed without knowing at least one of the private numbers. Finally, the PFS part is simply that each person permanently deletes both the shared secret and the private number they generated for that exchange (they will create new ones next time they want to communicate). That means there is no way to reconstruct the secret and re-decrypt the message.
Of course, authentication also has to be added to all this.
For more info, probably easiest to look up Diffie-Hellman key exchange online.
I don’t care much about any of these technical intricacies regarding word matching. I want Lemmy to be a human institution, which means no bots editing people’s posts beyond possible spam control. If there is a serious trolling problem featuring specific keywords in a community, I’m fine with a moderator manually kicking off some automatic action to remove a bunch of posts at the same time. But we don’t need robot nannies surveilling and messing with all of our posts.
Here’s another example, not from here. Before celullar phones, before television, before broadcast radio and even before the telephone, there was the telegraph. Communications with it were done in Morse code, by operators tapping away on telegraph keys. Telegraph keys were typically made of brass, and people who used them all day were called “brass pounders”. That profession is long since obsolete, but there are still ham radio enthusiasts who use Morse code as a hobby, and there is a group of them called the BPL, for “Brass Pounder’s League”. There are also people who simply try to honor the history of the venerable telegraph even though they recognize it as being a relic from the bygone era.
Anyway, where am I going. Someone started a pretty good site about telegraphy and telegraph keys, called “brasspounder.net” which was a really cool name. Unfortunately Google’s algorithm seems to have classified that name as that of a porn site, because it saw the word you get if you ignore the “br” at the beginning, leaving “ass pounder”. Whoops. The site ended up changing its name to telegraphy.net, which is fine but less evocative in my opinion. Oh well.
The above is an example of the so-called Scunthorpe problem. Let’s see if Lemmy has that too.
I used proxmox and have played a little with nix and guix, but simplest is just use debian, put /home on a separate logical partition from the system partition so you can reinstall the system without clobbering user files, and as people keep saying, backup early and often.