1500100900 | 6 months ago | on: Recreating the US/* time zone situation
1500100900's comments
1500100900 | 1 year ago | on: Upstreaming Linux kernel support for the Snapdragon X Elite
1500100900 | 2 years ago | on: OpenBSD Workstation Hardening
1500100900 | 2 years ago | on: A peculiarity of the GNU Coreutils version of 'test' and '['
1500100900 | 2 years ago | on: Postgres: The next generation
1500100900 | 2 years ago | on: Azure dropping database support for MariaDB. Users advised to migrate to MySQL
1500100900 | 2 years ago | on: Louis Rossmann calls community to leave Reddit
1500100900 | 3 years ago | on: Waiting for Postgres 16: Cumulative I/O statistics with pg_stat_io
1500100900 | 3 years ago | on: Ask HN: Why is there so little info on the web about IBM mainframe programming?
1500100900 | 3 years ago | on: Why Twitter didn’t go down: From a real Twitter SRE
https://www.citusdata.com/blog/2017/04/20/analyzing-postgres...
1500100900 | 3 years ago | on: The FreeBSD/Firecracker Platform
1500100900 | 3 years ago | on: PostgreSQL 15
1500100900 | 3 years ago | on: It's time to halt starting any new projects in C/C++
1500100900 | 3 years ago | on: Ushering out strlcpy()
Not BSD, it was OpenBSD specifically.
1500100900 | 3 years ago | on: FreeBSD – A Lesson in Poor Defaults
1500100900 | 3 years ago | on: Technical reasons to choose FreeBSD over GNU/Linux (2020)
And when they do fix any of those things, what is his reaction going to be? So far it's been "it took them so much time to fix this, let's keep that in mind".
The point of it is clearly to convince people to use OpenBSD instead of FreeBSD.
1500100900 | 3 years ago | on: Technical reasons to choose FreeBSD over GNU/Linux (2020)
What's the reason? Surprisingly, the file is never edited in place.
1500100900 | 3 years ago | on: Use one big server
1500100900 | 3 years ago | on: Use one big server
1500100900 | 3 years ago | on: What FreeBSD can offer compared to other operating systems (2020)
By the way, as an example, you can also disable IPv4 and IPv6 in the kernel, I'm not sure how to do it in Linux.
For the event, your backend only needs to store the timestamp in a timestamptz field and make sure that clients set the correct time zone on session start (this you might want the backend to store in the database too, but probably in the users table).