That site seems horrible though. Random words in the body like reddit are hyperlinks to SEO landing pages on the same site. And there must be a better (original) source for the story than this...
2,570 karma · joined June 25, 2014
Email: hn@mjanja.mozmail.com
That site seems horrible though. Random words in the body like reddit are hyperlinks to SEO landing pages on the same site. And there must be a better (original) source for the story than this...
Fall of Civilizations is excellent too.
I've been blogging since 2006 and I feel the same way. The past few years I blog less, but I do try to write more to the point and use less idioms and spoken writing style.
More limiting is that the current release doesn't support custom Office365 tenant IDs. So basically, unless you are using outlook.com this won't currently work yet. I'm lucky that my org hasn't disabled SMTP and IMAP, but it's been so slow lately...
/usr/bin/chromium --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --user-data-dir=/home/myuser/.config/chromium-ilri --app=https://teams.microsoft.com
Works incredibly well (put this in a `.desktop` file with `Exec=` and you can launch it via your desktop's launcher). Some of the settings may not be needed anymore, as Chromium has come a long way in terms of Wayland support. I use Firefox for everything else, but haven't tried Teams there.I'm curious to see what happens going forward with these aging and under-resourced—yet critical—libraries.
This seems to work in Caddy, using a CEL expression:
@unrealistic-browsers <<CEL
{header.User-Agent}.matches("(Chrome|Firefox|Safari)")
&& ! ({header.Sec-Fetch-Dest}.matches("^.+$")
&& {header.Sec-Fetch-Mode}.matches("^.+$")
&& {header.Sec-Fetch-Site}.matches("^.+$"))
CEL
handle @unrealistic-browsers {
abort
}
Maybe there is a better way. And maybe this stops working when all low-effort bots add these headers to their crawlers.BTW if anyone has an invite on Lobsters I would appreciate it. :)
Shmatko, A., Jung, A.W., Gaurav, K. et al. Learning the natural history of human disease with generative transformers. Nature (2025). https://doi.org/10.1038/s41586-025-09529-3
Gluster was OK. We never pushed it very hard but it mostly just worked. Performance wasn't great but we encouraged users to use scratch space that was local to the node where their job was running anyway.
I modified the script slightly based on some of the comments in the thread and my own usage patterns:
#!/usr/bin/env bash
#
# See: https://news.ycombinator.com/item?id=45034496
bin=$(basename "$0")
echo "==========================="
echo "Wrapping $bin in bubblewrap"
echo "==========================="
exec bwrap \
--bind ~/.cache ~/.cache \
--bind "${PWD}" "${PWD}" \
--dev /dev \
--die-with-parent \
--disable-userns \
--new-session \
--proc /proc \
--ro-bind /etc/ca-certificates /etc/ca-certificates \
--ro-bind /etc/resolv.conf /etc/resolv.conf \
--ro-bind /etc/ssl /etc/ssl \
--ro-bind /usr /usr \
--setenv PATH /usr/bin \
--symlink /usr/bin /bin \
--symlink /usr/bin /sbin \
--symlink /usr/lib /lib \
--symlink /usr/lib64 /lib64 \
--tmpfs /tmp \
--unshare-all \
--unshare-user \
--share-net \
/usr/bin/env "$bin" "$@"
Put this in `~/.local/bin` and symlink it to `~/.local/bin/npm` and `~/.local/bin/yarn` (and make sure `~/.local/bin` is first in your `$PATH`). I've been using it to wrap npm and yarn successfully in a few projects. This will protect you against some attacks that use postinstall scripts to do nefarious things outside the project.I do believe in and love the open web. But the AI scrapers need to change, not me! They're the ones with the money and the 10x engineers (apparently). Read my sitemap and crawl my content from one IP, don't just haphazardly crawl and click every damn link and search term from hundreds or thousands of IPs every day!
By the way, rift valley software? I'm writing to you from Kenya, one of the homes of the great rift valley. It is truly remarkable to drive down the escarpment just North of Nairobi!
Very impressive! Thankless work. A reminder to myself to chase down some warnings in projects I am a part of...
#!/usr/bin/env bash
#
# See: https://news.ycombinator.com/item?id=45034496
bin=$(basename "$0")
echo "==========================="
echo "Wrapping $bin in bubblewrap"
echo "==========================="
exec bwrap \
--bind ~/.cache ~/.cache \
--bind "${PWD}" "${PWD}" \
--dev /dev \
--die-with-parent \
--disable-userns \
--new-session \
--proc /proc \
--ro-bind /etc/ca-certificates /etc/ca-certificates \
--ro-bind /etc/resolv.conf /etc/resolv.conf \
--ro-bind /etc/ssl /etc/ssl \
--ro-bind /usr /usr \
--setenv PATH /usr/bin \
--symlink /usr/bin /bin \
--symlink /usr/bin /sbin \
--symlink /usr/lib /lib \
--symlink /usr/lib64 /lib64 \
--tmpfs /tmp \
--unshare-all \
--unshare-user \
--share-net \
/usr/bin/env "$bin" "$@"
Notably `--share-net` should be moved down since it is negated by `--unshare-all`. I also added a reminder that the command is being bubblewrapped, modified the second read-write bind to the current directory, and changed the final exec to use `/usr/bin/env` to find the binary so it can be more flexible. I tested it with npm and yarn just now and it seems to work well. Thanks!The known good list is IPs and ranges I know are good. The known bad list is specific bad actors. The data center networks list is updated periodically based on a list of ASNs belonging to data centers.
There are a lot of problems with using ASNs, even for well-known data center operators. First, they update so often. Second, they often include massive subnets like /13(!), which can apparently overlap with routes announced by other networks, causing false positives. Third, I had been merging networks (to avoid overlaps causing problems in nginx) with something like https://github.com/projectdiscovery/mapcidr but found that it also caused larger overlaps that introduced false positives from adjacent networks where apparently some legitimate users are. Lastly, I had seen suspicious traffic from data center operators like CATO Networks Ltd and ZScaler that are some kind of enterprise security products that route clients through their clouds. Blocking those resulted in some angry users in places I didn't expect...
And none of the accounts for the residential ISPs that bots use to appear like legitimate users https://www.trendmicro.com/vinfo/us/security/news/vulnerabil....
For example, from a discussion on the Caddy forum https://caddy.community/t/using-caddy-to-harden-wordpress/13...:
(harden-wordpress) {
@harden-wordpress expression `(
!{path}.matches("/wp-includes/ms-files.php$")
&& ({path}.matches("(?i)/wp-includes/.*\\.php")
|| {path}.matches("(?i)/wp-admin/includes/.*\\.php")
|| {path}.matches("(?i)/wp-content/uploads/.*\\.php")
)
)`
respond @harden-wordpress "Access denied" 403
}One thing keeping me from switching to Caddy in my places is nginx's rate limiting and geo module.
https://wiki.hypr.land/Getting-Started/Master-Tutorial/#forc...
It has been common for years to use such flags for Electron-based apps on Wayland. It's not specific to Hyprland, and it's not as bad as it sounds. Chromium has been working on Wayland support for years and it was behind a feature flag. It's worked well for a while now and will be the default soon. https://www.phoronix.com/news/Chrome-Auto-Ozone-Platform