Readit News logoReadit News
gucci-on-fleek commented on Ban me at the IP level if you don't like me   boston.conman.org/2025/08... · Posted by u/classichasclass
kldg · 13 hours ago
What is the commonality between websites severely affected by bots? I run web server from home for years on .com TLD, is high-ish in Google site index for relevant keywords, and do not have any exotic protections against bots either on router or server (though I did make an attempt at counting bots, for curiosity). I get very frequent port scans, and they usually grab the index page, but only rarely follow dynamically-loaded links. I don't even really think about bots because there is no noticeable impact either when I ran server on Apache 2, and now with multiple websites run using Axum.

I would guess directory listing? -But I'm an idiot, so any elucidation would be appreciated.

gucci-on-fleek · 10 hours ago
For my personal site, I let the bots do whatever they want—it's a static site with like 12 pages, so they'd essentially need to saturate the (gigabit) network before causing me any problems.

On the other hand, I had to deploy Anubis for the SVN web interface for tug.org. SVN is way slower than Git (most pages take 5 seconds to load), and the server didn't even have basic caching enabled, but before last year, there weren't any issues. But starting early this year, the bots started scraping every revision, and since the repo is 20+ years old and has 300k files, there are a lot of pages to scrape. This was overloading the entire server, making every other service hosted there unusable. I tried adding caching and blocking some bad ASNs, but Anubis was (unfortunately) the only solution that seems to have worked.

So, I think that the main commonality is popular-ish sites with lots of pages that are computationally-expensive to generate.

gucci-on-fleek commented on Air Canada strike: Flight attendants reach tentative agreement   thestar.com/business/air-... · Posted by u/ryandv
abdullahkhalids · 7 days ago
I am glad the flight attendants are getting some of their demands met.

Can someone explain why a strike is needed to specifically get flight attendants get paid for all the hours they work? Isn't it already illegal to have a work contract which says you have to do these tasks but you won't be paid for them?

Why couldn't the flight attendants approach the courts and resolve it there?

If not already illegal, any political party or other political entity (unions) demanding a law banning these practices?

gucci-on-fleek · 7 days ago
> Isn't it already illegal to have a work contract which says you have to do these tasks but you won't be paid for them?

Labour code mostly doesn't apply if you're unionized:

https://www.canlii.org/en/ca/laws/stat/rsc-1985-c-l-2/latest...

https://www.canlii.org/en/ca/laws/stat/rsc-1985-c-l-2/latest...

gucci-on-fleek commented on The Best Line Length   blog.glyph.im/2025/08/the... · Posted by u/zdw
throw0101c · 14 days ago
TeX has a default of 66 characters per line. There's been research on this:

> Traditional line length research, limited to print-based text, gave a variety of results, but generally for printed text it is widely accepted that line lengths fall between 45 and 75 characters per line (cpl), though the ideal is 66 cpl (including letters and spaces).[1] For conventional books line lengths tend to be 30 times the size of the type, but between 20 and 40 times is considered acceptable (i.e., 30 × 10pt font = 300 pt line).[1]

* https://en.wikipedia.org/wiki/Line_length#Printed_text

There's a section of "electronic text" as well which goes into some factors (flicker, glare), but the number doesn't seem to change that much.

* https://webtypography.net/2.1.2

gucci-on-fleek · 14 days ago
> TeX has a default of 66 characters per line.

LaTeX defaults to that, but Plain TeX defaults to 10pt font with 1in margins, which is ~100 characters per line (which much too long to be readable).

gucci-on-fleek commented on Why the em dash is attracting unfair suspicion   theglobeandmail.com/life/... · Posted by u/throw0101a
firasd · 15 days ago
> (Disclosure: The Globe and Mail style guide mandates the use of en dashes, which is why you won’t see em dashes used here.)

What does this mean? You can't use an en dash as a 'dash'. It's for specialized applications like saying 1994-1995 etc. I think the author (or whoever came up with this 'rule') is confused here

gucci-on-fleek · 14 days ago
I myself prefer to use em dashes in this case, but spaced en dashes are an accepted alternative:

The Chicago Manual of Style §6.89 “En dash as em dash”

> In contemporary British usage, an en dash (with space before and after) is usually preferred to the em dash as punctuation in running text – like this – a practice that is followed by some non-British publications as well. See also 6.91.

The Elements of Typographic Style §5.2.1 “Use spaced en dashes…”

> Use spaced en dashes – rather than close-set em dashes or spaced hyphens – to set off phrases.

> […]

> In typescript, a double hyphen (--) is often used for a long dash. Double hyphens in a typeset document are a sure sign that the type was set by a typist, not a typographer. A typographer will use an em dash, three-quarter em, or en dash, depending on context or personal style. The em dash is the nineteenth-century standard, still prescribed in many editorial style books, but the em dash is too long for use with the best text faces. Like the oversized space between sentences, it belongs to the padded and corseted aesthetic of Victorian typography. Used as a phrase marker – thus – the en dash is set with a normal word space either side.

gucci-on-fleek commented on I tried living on IPv6 for a day   xda-developers.com/the-in... · Posted by u/speckx
dogcow · 23 days ago
Yeah, I know about the workarounds, but that just kind of defeats the purpose for me. Also, I've read comments from folks stating they were having a hard time getting a larger prefix from Comcast using PD... don't know how universally true that is.

Using DNS to resolve everything solves part of the problem, but firewall rules are another issue. The router would need to have the capability to update everything dynamically when the prefix changes. I think this in the works for pfSense, but I'm not sure if its actually supported yet. It looks like you might have to mess around with some 3rd-party script to make it work.

I guess I'm just generally disappointed that the whole process seems unnecessarily messy. I don't have a v6-compatible ISP right now anyway. I was thinking about trying a tunnel, but I'm not seeing the benefit in it right now.

gucci-on-fleek · 23 days ago
Yeah, this is the constant problem with IPv6: it's a much better design than IPv4, it's simpler to understand, and it should be theoretically much easier to use, but the tooling is all so terrible that it's often easier to just use IPv4. Which is too bad, because so many of the problems with IPv4 completely go away when you use IPv6, but right now we're stuck with dual-stack, which just doubles the amount of work to set everything up.
gucci-on-fleek commented on I tried living on IPv6 for a day   xda-developers.com/the-in... · Posted by u/speckx
dogcow · 23 days ago
Thanks, I appreciate your explanation. I was aware that there are workarounds, but to me that defeats one of the core tenants of IPv6, which is that we're supposed to be doing away with this NAT and NAT-like nonsense by giving everything a globally rotatable IP.

When I was reading up on everything, I also learned that your router can request a bigger prefix, but I ran across several posts from various folks stating they could only get a /64 from Comcast no matter what they tried, so I'm not sure how universally supported DHCPv6-PD requests are.

gucci-on-fleek · 23 days ago
> I was aware that there are workarounds, but to me that defeats one of the core tenants of IPv6, which is that we're supposed to be doing away with this NAT and NAT-like nonsense by giving everything a globally rotatable IP.

The nice thing with IPv6 is that devices have no problem with being assigned multiple addresses on the same interface. So most of my devices actually have 5 IPv6 addresses [0]: a globally-routable DHCPv6 address (the default), a globally-routable SLAAC address, a ULA DHCPv6 address, a ULA SLAAC address, and a link-local address. So you can have a globally-routable IP and a locally-stable IP at the same time. And this is arguably a good thing, since it would be annoying to have to renumber your local network if you ever changed ISPs.

> I ran across several posts from various folks stating they could only get a /64 from Comcast no matter what they tried, so I'm not sure how universally supported DHCPv6-PD requests are.

That's annoying, and also means that you probably won't be able to get NPT to work either. FWIW, both Shaw and Telus (in Canada) will assign you a /56 via DHCPv6-PD if you request it.

[0]: I don't actually want this many addresses, but a link-local address is required for IPv6, I want my devices to have constant/easily-memorable IP addresses so I need DHCPv6, Android only supports SLAAC so I have to keep that enabled too, devices will prefer IPv4 over a v6 ULA so I need to keep the globally-routable addresses, and I want to use static addresses in my LAN so I need ULA enabled as well.

gucci-on-fleek commented on I tried living on IPv6 for a day   xda-developers.com/the-in... · Posted by u/speckx
dogcow · 23 days ago
I recently decided that it was high time to stop ignoring IPv6 after 30 years of computing and actually learn how it is supposed to work.

So I started digging in, and there's definitely a lot to like.

But I see two big problems that are showstoppers in my opinion, at least for my home network (not even considering the fact that very few residential ISPs even support v6 at this point):

1. Generally speaking, the IPs of your LAN are based on the prefix assigned by the ISP. Most residential ISPs don't offer static prefixes. This means that every time your prefix changes, the IPs of all your devices on your LAN change. Seems like this "feature" was developed in a more idealistic era when people probably thought everyone would be getting static IPv6 addresses, since shortages would never be an issue. Unfortuantely, they failed to foresee the fact that most major ISPs are terrible, greedy organizations that either outright refuse to offer static assignments, or continue treating them as if they were scarce IPv4 resources, charging a premium or requiring business-class service to even get them.

2. The ISPs that do support v6, like Comcast/Xfinity in the USA, are only allocating one /64 prefix. This means you can only have one subnet (VLAN) on your LAN! Why are they being so stingy?

I would love to migrate to IPv6, but these two issues alone make it feel like a clown show for home users.

gucci-on-fleek · 23 days ago
1. nftables supports NPTv6 (Network Prefix Translation), which is similar to NAT, except it's stateless and every device remains individually addressable. So you can configure your DHCPv6/SLAAC to assign to each device both an address from your globally-routable prefix and from your ULA prefix, and then NPTv6 will handle mapping your ULA prefix to/from the internet.

2. Lots of ISPs only assign a /64 by default, but if you configure your router to request a /56 via DHCPv6 prefix delegation, you'll usually get the larger prefix.

FWIW, I'm using both of these on my home network, via a router running OpenWRT.

gucci-on-fleek commented on Evolution Mail Users Easily Trackable   grepular.com/Evolution_Ma... · Posted by u/mike-cardwell
gucci-on-fleek · 2 months ago
Evolution lets you default to the plain text version of an email, even if it contains an HTML version [0], so if you have that setting enabled (which I do, and strongly recommend), it should hopefully reduce the impact of this issue.

[0] Edit > Preferences > Mail Preferences > HTML Messages > HTML Mode = Show plain text if present

gucci-on-fleek commented on World Curling tightens sweeping rules, bans firmer broom foams ahead of Olympics   cbc.ca/sports/olympics/wi... · Posted by u/emptybits
peeters · 2 months ago
In some ways it's a shame because I love the finesse game as a counterbalance to the focus on power that seemed to peak around the time Brad Jacob's crew was dominating the scene. I don't follow curling quite enough to know what the impact will be on the meta game though. More guards? Fewer? More takeout attempts? It's interesting because finesse and power both have critical roles in both scoring and defending so it's not obvious to me where the negative/positive impacts to the game will be.
gucci-on-fleek · 2 months ago
> In some ways it's a shame because I love the finesse game as a counterbalance to the focus on power

The relatively recent ban on takeouts before the 5th rock [0] has pushed the game back towards finesse, so if you haven't watched curling for the past few years, you might find it to be a little more interesting to watch now.

[0] https://en.wikipedia.org/wiki/Curling#Free_guard_zone:~:text....

u/gucci-on-fleek

KarmaCake day36May 18, 2025
About
https://www.maxchernoff.ca/
View Original