tambre

That's why different European pricing zones were merged into a single EU zone, no? Should no longer be an issue because of that?

> [...] have letters that can't be capitalized (for example ß).

Here's ß capitalised: ẞ

Bad example, but you're otherwise correct. My personal pet peeve is systems mangling names with umlauts. Such names used to be common in my country, but they've become pretty rare now with globalisation likely to blame. But a workaround nowadays seems to be to give two different first names: one that has no special letters and another with.

Personal email server so I only send a small amount. Sometimes a few emails per day, some weeks only 1.

Did the outgoing emails for the site ramp up fast? Did you only encounter issues with Gmail or with other big providers too?

Been running my mail server on Linode for almost 2 years now. Fortunately I've yet to run in any issues. Having setup all the stuff properly from day 1 probably helps (TLS, SPF, DKIM, DMARC, MTA-STS).

A big caveat not mentioned for Digital Ocean is that they blackhole IPv6 email traffic. It took a while for me to figure out why it wasn't working since it wasn't documented in their documentation and there was no ICMPv6 response indicating this. Moved to Linode after that.

I wonder if the same caveat applies to other providers that have improperly implemented IPv6 by not providing a /64.

Have you tried LaTeX3? I find it to be a huge productivity booster compared to the old TeX ways that I never managed to grok.

Why you'd think that? It's assembly meant to run on a virtual machine in browsers. The textual representation is similar to your normal assembly code, albeit a bit more high-level.

Offers subpar speed and accessibility. Of course all the problems could be solved by simply using a CDN like Cloudflare.

Why? Just block ranges.

S3 website hosting lacks official IPv6 support, HTTP/2, TLS 1.3.

> while a billion smartphones were added

A huge number of them being on IPv6-only mobile networks using NAT64 to access the old Internet.

CVEs are typically reserved in blocks by big organizations.

> Ghidra's UI is better than IDA's at: defining structures, for example

IDA 7.4 introduced a new structure editor, arguably better Ghidra's. [1]

[1]: https://hex-rays.com/products/ida/7.4/index.shtml

IIRC, they plan to deploy IPv6 in 2020 spring. Unfortunately I can't remember the source.

And they've had it in few select residential areas as a trial since 2018 autumn [1].

[1]: https://www.dslreports.com/forum/r32136440-Networking-IPv6-w...

They used to support IPv6. When they added HTTPS support they removed it because of it [1]. Which is a complete nonsense reason. Using the old IPv6 range works for *.github.io domains even now.

But IIRC, you can fetch GitHub Pages custom domains over IPv6 with HTTPS too, but you don't get the correct certificates, because they simply don't have an IPv6 range pointing to the newer HTTPS-supporting infra.

[1]: https://github.com/isaacs/github/issues/354#issuecomment-385...

If you want to use HN over IPv6 then add the following to your hosts file:

    news.ycombinator.com 2606:4700::6810:686e

I do. I think it's essential if you've a website/blog or occasionally someone wants to contact you personally regarding one of your comments. I find it extremely frustrating to read a blog post, notice an error or a technical configuration issue with their website and then not be able to let the author know. Please make yourself reachable.

I run my own email server and don't do any spam filtering, so I definitely receive more spam than others (0–2 per day), but Thunderbird always puts them into my spam folder.

I hope to eventually add a spam filter in Postfix to deny at the SMTP level. However, configuring DMARC verification and requiring proper RDNS already cut the spam to a third.

I also recently switched to the hexadecimal encoding explained by u/bitmedley on my website. There's been no perceptible change in spam from that.

DMARC shouldn't be an issue for mailing lists, as long as one of DKIM/SPF passes. Are you seeing reports of both DKIM and SPF failing for mailing lists you use?

Properly configured mailing lists shouldn't modify contents of emails causing DKIM to fail.

I personally use Linode and would recommend them. But basically any tier 1/2 provider, i.e. too big/popular to block, will do. However, I would avoid DigitalOcean per my experience due to them completely blocking SMTP on IPv6 in addition to badly implemented IPv6 support and seemingly subpar support.

If you actually are looking for advice, then in descending importance order:

* Enforce a DMARC policy instead of explicitly disabling it.

* Enforce a strict SPF policy instead of ~all.

* Send over IPv6. Usually stricter rules are applied and not-up-to-snuff emails are rejected at the SMTP level.

* Your provider hosts lots of spammers for their size. Consider switching.

* Enable MTA-STS.

The first two I'd consider obvious glaring mistakes. The next two are less important, but would help. MTA-STS is a nice-to-have.

I can't analyse your DKIM setup, since I don't know your selector. Feel free to send me a sample email if interested.

Steam's cut is now 20%/25% depending on how much you sell. Pretty much applies only to big AAA/AA games. [1]

[1]: https://www.theverge.com/2018/11/30/18120577/valve-steam-gam...

Unfortunate that their crawler doesn't support IPv6. Trying to save IPv6-only websites results in "Couldn't resolve host". Hopefully that'll get fixed soon and not too much will be lost...

Their moderation tools aren't completely IPv6 compatible. I've emailed HN every so often about IPv6 support over the past few years and they seem to have been making progress on it.

The title "Hacker News in Now Reachable via IPv6" is false. The Ungleich guys have done amazing work on promoting IPv6, but this is simply a proxy.

However, if you want to actually use HN over IPv6, then force it in your hosts file:

    news.ycombinator.com 2606:4700::6810:686e

This comment's written over IPv6. :)

It being triggered certainly depends on very specific microarchitectural conditions that happen to be created by the instructions generated for those two functions and the 16-byte alignment also happens to be one of the required triggers.

Applying this fix to all other functions would certainly bloat the binary due to unnecessary padding and likely reduce performance for all, since the shipped binary is same for everyone.

> their reasons for not resolving archive.is

They do solve archive.is. But archive.is's DNS servers have been configured to return bogus answers to queries from Cloudflare's servers.

Supporting IPv6 natively would be cheaper as they'd need to invest less in NAT capacity.

Instead of a reactionary remark please provide arguments and explanations for your viewpoint to actually further the discussion.

Please explain your points instead of off-the-hip vague statements.

I suggest you have a second look at the HN guidelines [1].

[1]: https://news.ycombinator.com/newsguidelines.html

Volume controls aren't the only type of media keys. There's also pause, backwards, forwards and others. Most of them don't make much sense in the context of the OS, so applications need custom handling for them.

> I prefer the Slack web client to the native version.

Slack doesn't have a native version, does it? They have a desktop client, but that's just the web version wrapped inside Electron.