As already mentioned several times, selfhosting a mail server is not recommended unless you’re particularly interested in hosting a mail server, but with that said, you might find this project interesting:
As already mentioned several times, selfhosting a mail server is not recommended unless you’re particularly interested in hosting a mail server, but with that said, you might find this project interesting:
“These features and experiences need to be trained on information that reflects the diverse cultures and languages of the European communities who will use them.”
No, they do not, these features and experiences don’t need to exist at all.
I don’t really see the big problem here?
The primary problem in this story is the lying. If there are Bluetooth earbuds in the box then it should say Bluetooth on the box.
However sometimes people don’t realize which community they are in and they just look at the title.
Guilty as charged. After reading the title it didn’t even cross my mind that it could possibly refer to anything other than mobile apps so I saw no reason whatsoever to look at what community it was posted in as the app I came to think of as a good recommendation is cross platform.
When I finally learned about Pocket just a few years ago it surprised me greatly that I didn’t know about it before and now I use it daily:
In general, no. Most malware that runs its own process simply uses some name intended to make you not notice it. But it is possible, in Linux just as in every other operating system that ever existed, to imagine that some unusually sophisticated malware manages to exploit some unknown vulnerability to gain full control of the kernel and then all bets are off, then it would be able to do anything.
If you don’t actually have an opinion, just go with the default, ext4 really is a very good file system, but if you want to have an opinion and not go with the default, zfs is truly a fantastic file system.
Why should this be at the editor level?
Because for every programming language there’ll be people using text editors, but you’ll never succeed in even creating code formatters for them all.
The greatness in this project is in aiming low and making things better through simple achievable goals.
Seriously, Slackware at that time was wonderfully well planned and optimized, the stack of floppies needed for a fully usable system was remarkably small and downloadable.
It was the only distro I could get my hands on because who would download a distro on dialup.
I would, I downloaded Slackware through dialup, sometime late 1994.
I don’t think it’s ever happened to me that anyone told me that it was inconvenient for them that I didn’t have iMessage, compared to pretty much weekly exclamations of “But why can’t you just use WhatsApp like everyone else!?”
How could you possibly know that?
Not a joke:
Write your own device driver.
Preferably for some kind of esoteric hardware that you own but no-one else has, but it’d also be a valuable experience to do it for some commonly used piece of hardware for which good Linux drivers already exist.
For any moderately talented programmer this should be a reasonably difficult exercise, which will teach you very valuable lessons about Linux (and be quite fun at the same time).
For the usecase you describe, I’d go with a Chromebook, and build ChromeOS from source myself if that aspect felt important.
When PDF was introduced it made these things so much better than they were before that I’ll probably remain grateful for PDF forever and always forgive it all its flaws.
Really, an Arch user who didn’t mention that they’re using Arch, there’s certainly a meme hiding here somewhere!
When you’re not telling us which package you’re trying to install in which packaging system, the only meaningful answer is: you’re trying to install the wrong package.
You might find this project interesting:
https://maddy.email/