I use Nextcloud. Of course that only makes sense when you use the other Nextcloud stuff as well.

Don’t take a gift from a German as remedy.

You can click the eye on top of a feed to switch between seeing and hiding read posts.

I don’t understand why they don’t use the client side filter-variable in Lemmy UI. It has been available for a while now. It solves a whole bunch of problems. Summit implemented it a few versions ago and it works great. I can hide and unhide posts with the push of a button.

Sir, this is a Wendy’s memes community.

Although the amount of bad punctuation and emoticons might shift this into shitpost territory.

I don’t have a 486. I don’t know anyone who has a 486. I wouldn’t know what to do with a 486. I know full well that all versions before 7.1 will be fully usable forever and that someone would fork the kernel if they actually needed to run modern Linux on a 486.

And still this makes me a little bit sad and angry.

Switch and Click had a video about that recently: https://youtu.be/M9qJI2u_be0

I was and still am on HDD. The CPU was upgraded as well. I migrated to a new server.

The main culprit was the database. As far as I’m aware Lemmy is missing some indexes and due to the ORM they used didn’t always have optimised queries. Now with 64 GB RAM the whole database (almost 30 GB) fits in there fixing most of those issues.

The real fix will probably come with Lemmy 1.0. They radically changed the database layout and queries.

Image proxying wasn’t bad for performance. Just storage space. It was growing really really fast. Now that only I am using it to host the pictures I uploaded it is still much too large (24 GB). But its directory structure is so convoluted that I can’t really debug it. My stuff really shouldn’t be taking up more than a few hundred MBs.

I am the only one using this instance. I am subscribed to a hundred communities or so. I am always pretty up to date with my Lemmy versions.

RAM. Maybe 32 would have been enough but 64 cost as much as 32 so that decision was easy.

Same stuff you do on any other instance. Looking at stuff, upvoting, downvoting, posting and commenting.

Control. I’m not beholden to anyone. My server is federating exactly those communities that interest me.

I run an instance just for myself and it was a nightmare on HDD and 16 GB RAM. It was slow as molasses. Supposedly the database layout will be fixed with the 1.0 release that is just around the corner.

Since I upgraded to 64 GB it’s been pretty smooth. Still wild that that is necessary for a single user.

Also, disable image proxying. I have no idea what pict-rs does but it seems to be too much.

You should consider running Piefed instead. It’s not as resource hungry as Lemmy.

I finally finished Spider-Man: Miles Morales and just started Spider-Man 2. Man, that game runs like ass on the Deck while I have to make it look worse than the previous two.

And it actually feels like what I’m experiencing are bugs and not necessarily the Steam Deck’s fault. Stuff like models popping in without animations. I remember seeing pictures of that when it was new. Strange that they didn’t manage to fix it. Couldn’t they just have stayed on the old engine? It worked perfectly fine!

They have this very complex system of presenting you with two links. One lets you access the tiddies, the other sends you to Club Penguin. Impossible to circumvent. But some hackers claim to manage to do it by “reading”.

Whoray!

Famous astrophysicist Dr Brian May can make music? Yeah, right!

There have been plenty of similar techniques (esync and fsync) in Proton for years. That’s basically why the work was started to get this into Wine in the first place.

The way I understand it this is proper support in the kernel and Wine. So you will still get some improvement. But it won’t be any way nearly as large as the article suggests.

I bet those patches are already in Proton-GE or at least GE is likely already working on adding them. For Valve’s Proton I suspect they will be added for version 11 or 12 at the latest.

Imagine how it looks from the person sitting in front of them. It’s perfect.

But they make the numbers bigger! Biggest number is best number!

The thing is, you don’t need to know anything for that. Things like pricing, storage amount, maybe anti spam measurements, maybe quality of the interface are much more important. The underlying technology is more or less irrelevant.

But let me try to give you a quick overview to hopefully sate your curiosity:

The server program to send and receive emails is called an SMTP (Simple Mail Transfer Protocol) server. It receives the mails sent from other company’s SMTP servers. The so called MX (Mail eXchange) entry in the domain system tells everyone where to find that server. Popular open source servers are Postfix, Exim and Sendmail.

If you have an email program (the email client) on your computer or smartphone it will log into the SMTP server and give it the mail you want to send. Popular email clients are Thunderbird, Outlook and I think the one on MacOS is just called Mail. If you are used to send your mail from the Gmail website that website is the email client.

SMTP does not give you anything to actually read the mails. That is usually done through an IMAP (Internet Message Access Protocol) server. Your client connects to the IMAP server to get a list of all your mail folders and the mails in there and whether they are marked as read, unread, important, etc. Usually the username and password for SMTP server and IMAP server are the same for convenience.

In terms of encryption your connection to these servers from the mail client and the connections between SMTP servers can be encrypted. But the mails themselves, ie what is stored on the server, are not encrypted.

There are some standards like GPG (GNU Privacy Guard) to encrypt mails but they are not very widespread. And most importantly they require sender and recipient of the mail to have the encryption set up. They encrypt the content of the mail but not the meta data like the sender and recipient, send date, ip addresses of sending and receiving SMTP servers, etc.

Hope that helps. Feel free to ask questions.