Thanks. I wasn't planning to go there anyway...
It's annoying how the title throws such a general open question and then they don't clarify this at all.. there isn't even a single match for "USA" or "America" in the whole article, you have to sort of guess.
Yes, although Ctrl-M would be the "Carriage Return" character (\r). For the "Line Feed" newline character (\n) the Control combination would be Ctrl-J. Both of them would normally produce a new line when you press them on most terminals.
That's why if you open in nano/vim a file with Windows style EOL (/r/n), you might see a strange ^M symbol at the end of each line.
To be more precise, it's the "EOT" (end of transmission) control character, the 4th symbol in ASCII, from the non-printable character area.
Those are more like engine reimplementations rather than alternatives, which explains the fear of EA interference.
It's a pity so many open source games go in that direction. I honestly wouldn't mind even if the graphics were ugly placeholders or it took a minecraft-style pixelated approach.
Phasmophobia & other multiplayer horror games of sorts (eg. ghost watchers, Labyrinthine, Pacify, devour, etc). I don't think there's any multiplayer horror game like any of those in the open source world.
I searched and I think there was at least one attempt at the idea (openphobia), but I don't think it ever had a playable release before it was abandoned.
Were they using Twitter to provide exclusive updates not available anywhere else?
My impression from the post is that they are publishing the exact same updates in multiple locations, including mastodon at https://framapiaf.org/@debian ...so just because they were publishing in that one extra site to make it accessible to a particular subset of people does not mean all other people were being shut off from receiving updates.
However, I do agree with the move, but only because Debian being a FOSS initiative should stay away from proprietary platforms and promote FOSS.
I think there are situations that fsync does not cover very efficiently, to the point that it can cause timing issues that lead to some bugs / incompatibilities. The timing issues might be rare, but that doesn't mean the overall efficiency is the same. It would be interesting to see benchmarks of fsync vs ntsync.
You still call the period before when the sun is directly overhead “morning” and the period after “afternoon” and similarly with “evening”, “night”, “dawn”, “noon”, “midnight” etc.
Note that the Sun position is not consistent throught the year and varies widely based on your latitude.
In Iceland (and also Alaska) you can have the Sun for a full 24 hours in the sky (they call it "midnight sun") during Summer solstice (with extremelly short nights the whole summer) and the opposite happens in Winter, with long periods of night time.
I think it still makes the most sense to decide that the days of the week (“Monday”, “Tuesday”, etc) last from whatever time “midnight” is locally to the following midnight, again probably rounding to the nearest whole hour.
Just the days of the week? you mean that 2024-06-30 23:59 and 2024-07-01 00:01 can both be the same weekday and at the same time be different days? Would the definition of "day" be different based on whether you are talking about "day of the week" vs "universal day"?
"you want a government backdoor on GPL licensed code? publish the backdoor for everyone to use, see and exploit/check for themselves. And/or watch as people simply take a version of the software built from a more reputable source without that backdoor instead. Thanks for the money!"
"you want to force all foss projects existing in the global internet across countries to get paid by you or close? enjoy your logistic nightmare as you pay to be made fun of by all other countries while I fork projects with one click"
like how not being able to sign up for something with tor and monero is a privacy violation, it’s not.
Note that "secrecy" and "privacy" are often understood in Security lingo as different things. One protects confidentiality, the other one protects anonymity.
It's possible to have one and not the other...
You can have a very private system through onion routing but have the contents of the messages exchanged be in plaintext, open to the public. Nobody will be able to know the one who wrote the message was you. But they can see the message. (then there is privacy, but not secrecy).
Or you can have very strongly encrypted communications (say HTTPS) but have the DNS exchanges (or the TLS handshake, or the IP addresses) be in the clear, so people in the middle (eg. your ISP.. or your workplace tech guys) can know exactly that the packages are sent by you and where you sent them, even if their content is encrypted. They can know which service you tried to access to, for how long and how many times (so you have secrecy, but not privacy).
If they were complaining about cronjobs being created (like the post says), then they must have known what cron is.
That was long ago, I wonder if he might be using now GNU Guix, since it's a GNU project.