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).

Getting the device speed right seems way more difficult without a Global Positioning System.

Hopefully it will eventually be deployed [0]

[0] https://techport.nasa.gov/projects/146938

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.

With Pro accounts limited to 100 users, I believe this is a good opportunity to recall [0], that lists businesses that overprice SSO

[0] https://sso.tax/

I've discovered by default, CloudRun only allocates one core per HTTP request, and exclusively during request execution [0].

So your app runs at 0 CPU when there is no requests ongoing, and can't use more than 1 processes in the same container. It means you can't have a container with nginx+rails, as only nginx will have a core to execute, rails has no core and it leads to a timeout.

Maybe you should ensure your app is not trying to use a second process?

[0] https://cloud.google.com/run/docs/configuring/cpu-allocation

If you want goods imported in containers from China, you have to have empty containers in China.

The ship may be full of empty containers.

At some point of the pandemic, we will discover we should have put more effort in the psychology effects of the words.

Make people panicking is probably not a very good thing to do if we want to expect them to take the best decisions.

Special mention to French president that described March 2020 situation as « This is a war ».

This is what HTTP/2 does with HPACK compression to compress headers and its "static table" [1] for common headers.

There are 61 headers already defined in this table.

[1] https://httpwg.org/specs/rfc7541.html#static.table.definitio...

If all of them suffer from the same issue (let's say memory corruption), you end up with 5 satellites that will fail on the same timeline.

When operating multiple devices to improve reliability, diversity is one point.

curl has a very handy --resolve option for that:

curl --resolve 'panel:443:192.168.10.5' -k -X GET https://panel/rest/configuration

Hostname can be set to * in recent versions of curl, it's even more handy:

curl --resolve '*:443:192.168.10.5' -k -X GET https://panel/rest/configuration

If you can afford a one off 1 second of latency for your SQL queries, then using logical replication with pgbouncer seems way easier :

- setup logical replication between the old and the new server (limitations exist on what is replicated, read the docs)

- PAUSE the pgbouncer (virtual) database. Your app will hang, but not disconnect from pgbouncer

- Copy the sequences from the old to new server. Sequences are not replicated with logical replication

- RESUME the pgbouncer virtual database.

You're done. If everything is automated, your app will see a temporary increase of the SQL latency. But they will keep their TCP connections, so virtually no outage.

So where is the source code of this Perl script ?

A copy of the source code has been stolen.

To be honest, DNS is probably the only piece that can easily take the entire infra down (including the staging one).

It's so easy to rely on DNS names everywhere...

When using an external service like this one, you have no guarantee:

- this service will last forever

- this service won't be acquired by someone else with evil intention and will never lie

Do not use this service. It has the power to steal your traffic.

Ariane 6 first flight was planned to bring OneWeb satellites in space.

If they can't launch them, I wonder what will be the payload of the first Ariane 6.

Probably because they want to improve the response time with a more precise DNS answer.

With s3.amazonaws.com, they need to have a proxy near you that download the content from the real region. With yourbucket.s3.amazonaws.com, they can give an IP of an edge in the same region as your bucket.

You can't enumerate sub domains via DNS (except if you use DNSSEC with NSEC algorithm, but nobody do that).

It does not prevent people guesssing it tough.

One great advantage of wildcard certificates is the privacy of the domains.

If you use customer1.mycorp.com, customer2.mycorp.com, etc. the names of your clients is exposed twice :

- if you issue one certificate with all the domains, all the domains are readable in the certificate (Cloudflare free cert. has this issue too)

- all the LE certificates are published in Certificate Transparency logs. So you can detect if anyone issues a cert. for your domain, but anyone can view the certificates you issued.

With a wildcard certificate, the subdomains used are not public.

Note this issue applies to "internal" subdomains too. You probably don't want to expose the hostname of your backoffice (admin.mycorp.com) or your new top secret project (linux.microsoft.org).