

Check out stalwart mail! Not sure it has all the features you need, but it is really flexible through scripting and has got a nice admin web-interface!
Check out stalwart mail! Not sure it has all the features you need, but it is really flexible through scripting and has got a nice admin web-interface!
I think if every contributor ever agreed, you could switch to a more permissive license that permits a superset of the original license.
Who said it was superjesus? It’s one of the smaller points on the long list of rusts advantages over other systems level PLs, but nonetheless notable. Especially if you consider that the feature that makes this possible is used for a ton of other useful stuff. And seriously, the boilerplate does matter, especially if you also add Ord, Hash and Debug impls. Your comparison with pictures in a noval makes no sense, since these add something valuable to the text and are easily distinguished from it. Heaps of boilerplate at a glance look just as meaningful as important sections of code, so being able to avoid it makes navigation significantly easier.
Isn’t it obvious? More code to skim, scroll over and maintain if something changes. If you add a struct field, your manual EQ implementation still compiles and seems to work but is wrong and will lead to bugs. Yes, solving this for 99,999% of cases with an attribute is just far superior and does make a difference (while keeping it easy to manually implement it if needed). Hash and Ord and some other traits can be implemented in a similar fashion btw…
Then just download it e.g. from github: https://github.com/rsms/inter/releases
For a fair comparison you should at least use the same font and font size. Did you try that? It will still look different on windows, maybe better, but I think you can get pretty close. I use the “inter” font on debian xfce and it looks very clean (the font is probably in your repos as well).
docker-compose up -d
Oof what a pain this was! Glad it finally works and I can move on with my life!!
But of course everyone decided it is just easier to nag all the users with a big splash screen.
Nope, the thing is, you’ll very rarely find a website that only uses technically necessary session/login cookies. The reason every fucking website, yes, even the one from the barber shop around the corner, has a humongous cookie banner is that every fucking website helps google and other corporations to track users across the whole internet for no reason.
Interesting! What’s better about owncloud?
I’d say at 1000 lines it usually makes sense to extract some parts into other files. But sure, I guess most obscurities have positive aspects. On the other hand, nothing is stopping you from writing a separate file with only function signatures next to your python scripts. It’s just not required, because why would it ;)
The stone-age called, they want their languages that need header files back!
(I use Rust btw.)
I can recommend debian testing. I’m using it on laptop and desktop for several years, always running “apt update && apt full-upgrade && apt --purge autoremove” and it never broke. It’s not officially a “rolling release” but practically it is.
I recently tried selfhosted grocy. It’s really amazing, but in the end does seem over the top for us, so we went back to intuition and communication based “household management” ;)
Obviously not. Building a modern browser engine from scratch is an immense undertaking, so it’s definitely possible that it will never be usable as a replacement for every day webbrowsing. But for now I won’t give up hope :)
“trustworthy AI”
Why? Why can’t we have even a single decent browser? Servo is my last hope.
It’s not a rolling release though, right? I mean mint is nice, but I am absolutely pleased with my experience using debian testing as daily driver for years while it just stays perfectly up to date and never breaks (as opposed to arch or even manjaro).
Debian (testing branch): Add normal firefox to the repo. Firefox ESR is total bullshit that makes zero sense to use. I always install it either as flatpak or from the unstable repos using apt-pinning (which works great though!)
This is the way!
I also think it’s more descriptive. Just like blocklist and allowlist.
If you need to hook it up to other stuff (where there is a solution using postfix), it’s probably easier to stick with postfix. As an all-in-one mail server I prefer stalwart over docker-mailserver, mailcow, etc. because it’s one unified software with sensible configuration instead of a clusterfuck of services put together using string and duckt tape.