chtitux

With the (future) shutdown of WorkMail, AWS almost did the full circle.

5 years ago , LLM was "beyond minimal conversation, intelligence isn't happening".

I'm pretty sure in five years, local LLM will be a thing.

I strongly suggest UUIDv7, with our birthdate encoded as time.

Ordering the world population by birthday becomes so easy. Plus no endless discussion on wether or not we should use UUID as primary key.

It could be interesting to understand the actual content of the qrcode. part1 is a static id, so likely linked to the membership.

part2 seems to be a timestamp. Maybe we can try to forge the value to "now - 10 seconds".

And if the implementation has been done right, the "part3" should be a signature of part1 and part2, not a "salt" (so forging part2 should be detected and code rejected).

Wait until we'll be assigned IPv6 as phone number.

Maybe just use Starlink from the satellites, so we don't rely on a specific ground station.

Starlink Ground Station Network is global, spread in many different countries and look more resilient than a single one.

[1]: a delete command was wrongly issued to all Cassandra servers during a planned maintenance

[2]: a database server had its disk full that lead to a corrupted database

SRE is tough.

Limiting characters can also be a feature, so users can't use emojis in their password (this is so fun), to realize later they can't login, because they don't know how to input emojis from their desktop computer.

Hopefully passwords will be gone soon (at least that's my hope).

The technical investigation is impressive.

I'm wondering if the author contacted the JAXA team. Maybe they would share how the data is encoded?

If the information is secret, it's probably encrypted (SpaceX eventually did that once radio amateurs decoded the video stream), but if it's not, maybe JAXA would be happy to help?

The number of certificates issued/inserted on 25th December, which is almost the same as any other day in December, while being a bank holiday in most Western countries, makes me happy: the industry successfully made certificate renewal fully automatic.

For LetsEncrypt, all renewal requests are done with ACME clients, so this is not a surprise.

I'm curious to know which part of DigiCert and Certigo certificates are actually renewed with an ACME request (both support it).

Given the number of people now relying on Clouflare 1.1.1.1 to "get Internet" (ie using 1.1.1.1 as recursive name server), I can't imagine APNIC deciding to stop Clouflare using this range.

It seems "too late" to revert this decision. Otherwise people will experience "Internet stopped working", blaming their ISP.

APNIC may decide to keep a working DNS server on 1.1.1.1, but ethically, routing traffic to someone else than Cloudflare is not great.

> I want 2007 Google back.

The SEO mess was indirectly caused by Google PageRank and other related optimizations.

Maybe we want 2007 Internet instead?

The AI world will inevitably lead to "content optimization", so the Chatbots that will be asked "questions about life" (as of Today, where people usually search on Google "I have fever/depression/a turbulent child/tomatoes in my fridge, what should I do?") will more frequently answer specific products.

Instead of promoting a single website (Current SEO strategy), content producer will be tempted to produce many texts on a great variety of sources, to reinforce the model on a specific subject.

Time will tell if in 2035, we will want 2023 ChatGPT.