netzvieh

There are both variants in the wiki:

https://wiki.postgresql.org/wiki/Don't_Do_This#Don't_use_tim...

> Don't use the timestamp type to store timestamps, use timestamptz (also known as timestamp with time zone) instead.

> Why not?

> timestamptz records a single moment in time. Despite what the name says it doesn't store a timestamp, just a point in time described as the number of microseconds since January 1st, 2000 in UTC. You can insert values in any timezone and it'll store the point in time that value describes. By default it will display times in your current timezone, but you can use at time zone to display it in other time zones.

> Because it stores a point in time it will do the right thing with arithmetic involving timestamps entered in different timezones - including between timestamps from the same location on different sides of a daylight savings time change.

> timestamp (also known as timestamp without time zone) doesn't do any of that, it just stores a date and time you give it. You can think of it being a picture of a calendar and a clock rather than a point in time. Without additional information - the timezone - you don't know what time it records. Because of that, arithmetic between timestamps from different locations or between timestamps from summer and winter may give the wrong answer.

> So if what you want to store is a point in time, rather than a picture of a clock, use timestamptz.

In Germany at least you (can) buy a prepaid sim card and activate it. That gives you a phone number and you usually get the price you paid for the sim card added to your account balance. From then on you don't have to pay anything to keep using that phone number to receive calls/SMS. Calling/sending SMS costs are coming of your balance. You can buy packages (usually good for 4 weeks) with e.g. 300MB data volume or unlimited calls.

There's also the model where you pay a monthly subscription and receive a new device every few years or have some other benefits.

Because the key has to be revoked on AWS side, not just removed from the repo. And probably the person pushing to Github and the person paying the AWS bill/the AWS admin are usually not the same..

> 1. Where do the upstream RHEL sources live? CentOS sources are in https://vault.centos.org/8.3.2011/BaseOS/Source/SPackages/, but where do they get them upstream? I believe they're only available to RHEL subscribers, does this give RH a way to block clones?

Red Hat publishes it's sources on https://git.centos.org. Those are then used to build CentOS Linux packages.

In the future they'll do their development there, and build CentOS Stream and Red Hat Packages from there.

See also: https://crunchtools.com/before-you-get-mad-about-the-centos-...

> Remember, the source code at git.centos.org is basically read only, downstream code from RHEL. That’s how Red Hat complies with the GPL. Technically we go above and beyond because we are only legally required to provide code to customers, and not required to provide code for BSD/Apache/etc licensed code, only attribution.

Regarding question 2, CentOS has a somewhat custom build system for each major version afaik, for 8 this would be https://koji.mbox.centos.org/koji/