Been using/abusing wezterm for years, my scrollback is set to 1000000 and text selection has never been a problem... copy mode however does make it even easier

I hed to look this up, so here's a correction: it was one large line logically split, not smaller lines. So you can't select, say, a long compact JSON line.

Still not fixed: https://github.com/wezterm/wezterm/issues/3494

I really wanted to switch to ipv6 only for certain services but then found out that AWS itself doesn't support ipv6-only for most of its infrastructure https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-su...

This forced me to dual stack just for AWS services to intercommunicate...

They *are* making progress on it: https://aws.amazon.com/new/?ams%23article-feed%23pattern-dat...

They seem to have been averaging about two services per week for the past year. But they have a lot of services...

HTMX with Django backend really excels in this regard.

I'd prefer Unpoly over HTMX, but yes, it excels.

Over 90% of english capable internet users use the metric system so maybe it should be the primary unit system...

My understanding is that they use the IP range assigned for CGNAT as their private address range to avoid conflicts, but do they use CGNAT?

For the oauth login it requires the following permissions: View basic information about your account, Manage your data in Google Reader, View your email address Manage your contacts, View and manage your Google Contacts, Perform these operations when I'm not using the application

Why would it want access to view AND MANAGE my contacts? This seems a bit odd.

I understand your concern ... see my response here:

https://news.ycombinator.com/item?id=5373701

Short answer, we don't want access to manage your contacts, there's just not a read-only option (last time I checked).

I had to google 'revieled' ;P

Memcache is designed to be run on a trusted network and only accessed by trusted clients. Therefore sharing a memcache daemon in its current state is not recommended at all.

See http://www.slideshare.net/sensepost/cache-on-delivery on what can be done with a publicly accessible memcache daemon.

Many sites also use memcache to cache page fragments that will be sent verbatim to clients with the rest of the webpage.

As Marco demonstrated in his slides one can easily inject into caches and if one can change the values of keys related to page fragments then it is a major security risk.