Ayesh

Friendly reminder that none of the PHP 4,5, AND 7 series receive active security support, and are EOL.

PHP 7.4 still receives some updates from LTS vendors, and PHP 8.0 reaches EOL Nov 23rd.

I guess there will be one last release towards Nov 23, because I'm already seeing some activity (https://github.com/php/php-src/commits/PHP-8.1/).

Those cheap laser "1D" bar code scanners cannot read off a screen (except maybe eInk). It sucks because the supermarkets I frequent have their loyalty cards based off barcodes. Fortunately, barcode readers emulate keyboards so you can just type the code on a keyboard.

I recently started to use Caddy v2, which doesn't even support SSL at all, and TLS versions older than 1.2.

Basically, yes. There was a really nice article here in HN about it, I couldn't find it but hopefully someone will point at it.

HTTP/3 is supported in Nginx 1.25, available from nginx.org's repo. I tried it a couple days ago, and worked great.

None of the Nginx builds available out there seemed to fit my use cases perfectly, so I resolved to customize it (https://gist.github.com/Ayesh/7c7a1bf08d37497aef8672644a7fd5...) to my exact use cases.

I gave up on Nginx because it was impossible, or incredibly difficult to figure out how to append/modify HTTP headers. I wanted to send CSP headers if the reverse proxied application did not set on their own, and I wasted a whole fruitless day trying to do it. I gave up.

Yeah I've built quite a lot of muscle memory having used Apache for about a decade too, and the configuration felt quite intuitive, but Caddy's configuration is such a fresh breath and I'm really enjoying it so far. More than Apache's to be honest.

Funny, I saw this on HN while I was taking a break from testing Caddy, which has HTTP/3 support, and is even enabled by default. I suppose it's based on Go's implementation.

I'm using Apache at the moment and it's working great. HTTP/3 isn't even in the horizon for Apache, and it is the reason why I'm trying out Caddy/Nginx/OpenLitepseed in the first place.

Would nghttp3 eventually bring HTTP/3 to Apache?

I'm using Xiaomi 20,000 mAh power bank, and passthrough works great. Mine only supports 18W out, when I have my 30W charger plugged in, the power bank charges as well.

Yeah the linked post is a bad rehash of the original blog post. Thanks for linking it.

Unfortunately I don't think it's possible. The router can only intercept as far as DNS goes, and DNS Blocklists are already incapable of blocking YouTube ads.

> still

Never had problems. FWIW, I'm using AES/256 bit keys/HMAC SHA-512 on all of my volumes.

I meant the long static passwords Yubikeys "type" when you touch the button when plugged in. It's just a static long text that has no context.

I haven't used BitLocker or anything else, so I can't really compare.

Veracrypt has a neat benchmark tool so you know the speed beforehand. I suppose most CPUs have native support for the popular algorithms, so the bottleneck really is the disk, not CPU itself or the software.

Using it for a few years now, and I'd hesitate not one bit to recommend. It's not as "technical" as said in comments either tbh. But us in HN are not qualified to call it non tech friendly I guess.

Performance is great, nearly "metal" SSD speeds. I use it with a hidden partition of an external HDD, and works great too, once I got Windows to stop asking me to formally that partition.

The only feature I wish it could have is better Yubikey (and alike) integration. I can use those static passwords as an encryption key, but I'd need something better.

I started to use those stand cases, and I'm not going back. They Make the phone so much more thicker, but also make it so much easier handle.

On mobile, it constantly opens the keyboard, and I think it's perfect!

Geocoding is certainly _much_ cheaper than other providers.

Link to Youtube blog: https://blog.youtube/news-and-events/podcast-destination-on-... Support doc: https://support.google.com/youtubemusic/thread/236590252

To summarize:

Donuts (one of the biggest TLD registries) is increasing their TLD wholesale prices for 204 TLDs by USD 2-6 on Oct 4.

- https://icannwiki.org/Donuts - https://news.gandi.net/en/2022/09/augmentation-de-prix-sur-l... - https://ntldstats.com/registry/group/Donuts-Inc - https://www.identity.digital/registry

Not the previous poster, and I don't use Kopia, but after reading Kopia features and docs, they seem to be in par. I use Duplicati quite extensively for personal backups, and didn't really have any issues.

Duplicati has a web interface, so with a proper authentication in place, you can use it to remotely monitor and manage backups.

Duplicati doesn't keep a local cache. It uses SQLite files for file meta data, but not for the content themselves.

I like Duplicati's snapshotting mechanism. You can specify how long or how many snapshots to keep, and my anecdotal evidence is that it's archival storage-friendly. I imagine S3 and it's lifetime management rules can bring a decent and cost effective backup solution.

I'm using Google Drive 2TB plan, and I didn't see Kopia supporting Google drive out of the box.

Nobody should be using DNS service provided by their registrars. They tend to be insecure, slow, and like you said, missing a lot of features.

As a Xiaomi user, the iOS update lifetime and frequency is not even close to the Android and Android Security updates Xiaomi phones get.

I used to travel with a DSLR, and while the photos were phenomenal in comparison to my phone's output, the ease of minor edits, photo reviewing and management, backups, and posting them were strong enough reasons for me to ditch my camera setup.

I now travel with an Insta360 X2 that is much more convenient and compact, but there are certain types of photos (night time, star trails, light trails, portraits, etc) that phones and action cameras are just laughably bad at.

Probably the most common use case is SaaS providers that support custom domain name for whatever the software it is. For example, a site uptime monitoring service might offer a feature to host a status page on a custom (sub)domain of the customer. The SaaS now needs to programatically create virtual hosts on demand, issue HTTPS certificates, run routine updates, etc.

An API and a web server with small segmented updates make this so much easier. Compare this to Apache, that has to wait to properly end existing connections before reloading, has a config file parsing overhead, and probably does not scale that well with several virtual hosts anyway. There are hardware/File System level limitations as well.

It's $38K for 100 years.

Because WordPress.com is the .blog registry, I guess they could pull it off for .blog domains. Other tld registries have bitten dust already, and other registries have jacked up prices in the previous years. But even at a 10% increase a year (likely the case for .com), the domain renewals will cost about $5K for 100 years. With hosting, support, and WordPress being able to run for 100 years, I think that price is justified.

If ICANN screws WordPress, or whatever WordPress.com uses for hosting screws them, they will be in a mess.

> Unlock full access (page 2) by uploading documents or with a 30 Day Free Trial

Scribd is the Pinterest of PDF files.

I use Vultr, Digital Ocean, and Scaleway quite extensively, and my personal anecdote is the Scaleway, while gives a great bang for buck, comes with disk speed issues in their low priced servers.

If I read correctly, this is now the most watched live video on YouTube! Congratulations to India and the team on this fantastic feat of an achievement.

5,8 million now. I have never seen _any_ live video with that many views.