I'm one of those (though I usually do not publicly complain about it).
1,744 karma · joined December 14, 2020
I'm one of those (though I usually do not publicly complain about it).
I hear that argument often. When a program uses $XDG_CONFIG_HOME/tool/ for its config files, to what value should I set XDG_CONFIG_HOME to get the old behavior where it puts its config in $HOME/.tool/?
It's not only about the comments we can see, but also about those comments that get filtered out by the moderator
> Also funny that you wonder if people would take the hurdle to send an email instead.
Of course you also get non-friendly emails. I was wondering if the people that leave those comments would send an email instead.
Roughly: > The Autonomous Antifa Freiburg has released internal chats from that association which give more detail.
How does a local antifa group get access to internal chats of a Burschenschaft?
And for the rare case where I have to do something which requires a lot of mouse pointer motion (e.g. CAD modeling or reading schematics) I prefer a real mouse over a trackpad.
What system headers are you trying to minimize?
I've seen this photo a hundred times and never thought about that. I wonder when ergonomics started being a thing when designing computer workplaces.
I must admit that I was way to long already at adult age before I got the final joke.
I just stumbled over it. I find it very interesting. Exactly because it made such a strange impression on the first look. The web design and the choice of C89 are not that common in nearly 2023.
> sim is a simple, interactive, multi-file text editor designed for screens with monospaced font. It is heavily inspired on the 'vim' and 'sam' text editors, hence the name sim. The main goal of this software is portability. It only depends only on the C89 standard, and tries to minimize the usage of system calls as much as possible, making it easy (or not even necessary) to port to another environment.
Does this mean I can have a vi-like experience, but I have to configure it myself? A quick look into the help page of mle was not very helpful.
Aside, I was not complaining about the Let's Encrypt stuff, I'm totally ok with using https nowadays.
Why is all this configuring with different headers necessary to publish a web site? For me it looks like the system is broken.
Somewhere in history we took the wrong turn making a simple thing like publishing a website that complicated.
I'd say, this is a security feature - even if the code is not the most secure.
Out of interest, did you report your findings from fuzzing? Did things got fixed?
I never used mothra, but heard a lot of good things about the plan 9 tools. They got the advantage, that they could start afresh. I'm curious how much work it would be to port it to a *nix system.
The linked article mentions some reasons. I use it, because it fits my console-focused work style. It's blanzigly fast, removes all the distractions like unnecessary images and ads, doesn't require me to take my hands of the keyboard, works very well if I'm working on a mobile hotspot, can be used while being ssh'd into a server... and because opening the side in a regular modern browser is only a key press away.