

1 step forwards 3 steps back is still 1 step forward 3 steps back
OpenBSD admin and ports maintainer
1 step forwards 3 steps back is still 1 step forward 3 steps back
Very good! Please remove anonym/PPA, DoH to cloudflare, Google search, telemetry, and pocket next, and I’ll make a consideration to stop calling your browser malware!
OP was asking about syslog so I answered about using using syslog. You’re reading too much into it. They asked if they could go with or without a syslog daemon, so I told them they can disable syslog if they want to. They did not ask about journald so I didn’t answer about journald.
Like how you cropped my message to make it seem like I was implying you couldn’t disable logging on systemd
Thank you Xhitter for blocking ads!
If you’re on arch you use redhat’s garbage. On non-corpo linux syslog can be disabled if you want, though I’d prefer to just symlink/mount /var/log to a memory filesystem instead.
User-agent: *
Disallow: /
tbh
View the end of humanity as a positive, the suffering machine will be over (at least until it re-evolves).
I call this one forbidden knowledge because I see it so little in public, but I’m sure it’s well known in privacy communities: A password like “I have this really secure password that I type into computers sometimes” is a much stronger and easier to memorize password than “aB69$@m”. It seems more often than not I find networks where the SSID is a better password than the WPA key.
Nothing, actually. I just decided one day I was going to install Arch Linux for no reason in particular, and now I’m on OpenBSD. I wish I had that kind of determination these days.
based, IRC is more based though.
I hate being trapped alone with my mind so no
Yes, wireless charging is the pinnacle of design and totally isn’t a huge waste of power for a slight increase in convenience. Also I’ve haven’t read it myself, but I’ve hearsay’d some amazing(ly awful) things about the USB-C spec (or lack thereof).
Replying to this pretentious comment for the sake of others reading this:
Replying to this pretentious comment for the sake of others reading this:
Run history | grep genpasswd for why this is not a good password storage solution. One must image skill issue.
I have history disabled in my shell, and unless your shell logs to a file, the password stays in memory.
The sooner you abandon javascript and css, the sooner you can be free
One must imagine skill issue.
I suggest looking at how many dynlibs your password manager links against and tell me it’s “simpler” again.
/etc/unwind.conf
block list "/var/db/unwind_blocklist"
forwarder { X.X.X.X port X DoT X.X.X.X port X DoT }
preference { DoT }
unwind_blocklist is generated with this script I wrote:
#!/bin/sh
# Blocklists for unwind(8)
blocklist=/var/db/unwind_blocklist
[ ! -f $blocklist ] && \
(umask 117; touch $blocklist && chgrp _unwind $blocklist)
{
ftp -V -o - \
https://blocklistproject.github.io/Lists/alt-version/everything-nl.txt \
http://winhelp2002.mvps.org/hosts.txt \
http://sysctl.org/cameleon/hosts \
https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt \
https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt \
https://raw.githubusercontent.com/Perflyst/PiHoleBlocklist/master/android-tracking.txt
echo twitter.com
echo www.twitter.com
echo www.x.com
echo x.com
echo facebook.com
echo www.facebook.com
} | awk -safe '
!/^M|#|(^|\.)[[:blank:]]*$|^definitely_not_porn$/ {
if ($1 ~ /127\.0\.0\.1|0\.0\.0\.0/) {
$0 = $2
}
if ($0 ~ /[[:upper:]]/) {
print tolower($0)
} else {
print $0
}
}
' | sort -u >$blocklist
rcctl restart unwind
Regenerates occasionally with cron.
This is truly the question of all time
Why would I use a password manager when this is much simpler and less error-prone?
100%, the remaining 20% grift their way to success