1,800 karma · joined January 17, 2019
That's what we thought the first time. And it did happen, a sane person did get elected a few years later, but then another few years later Trump got elected again. And it's pretty clear that he and his crew are rapidly turning the USA into a fascist authoritarian hellhole, and they show all signs of not being willing to step back from power. It's a real tragedy both for USA's own people, especially the ones that Trump doesn't like, but also for people in other countries.
That has real consequences. Here is, with thanks to user malauxyeux for neatly summarizing, a case that should anyone start thinking real hard of the consequences of using American services:
Nicolas Guillou, a French judge at the International Criminal Court, discusses in an interview with Le Monde the consequences of US sanctions imposed on him and eight other judges and prosecutors at the court. The sanctions were introduced after the court issued an arrest warrant for Israeli Prime Minister Benjamin Netanyahu.
The concrete consequences of the sanctions extend far beyond a travel ban to the US. "The sanctions affect all aspects of my daily life. They prohibit all US individuals or legal entities, all persons or companies, including their foreign subsidiaries, from providing me with services", Guillou explains.
All his accounts with US companies such as Amazon, Airbnb, PayPal, and others have been closed. "For example, I booked a hotel in France through Expedia, and a few hours later, the company sent an email canceling the reservation citing the sanctions. In practice, you can no longer shop online because you don't know if the packaging your product comes in is American. Being under sanctions is like being sent back to the 1990s", he says.
"Overnight, you find yourself without a bank card, and these companies have an almost complete monopoly, at least in Europe. US companies are actively involved in intimidating sanctioned individuals – in this case, the judges and prosecutors who administer justice in contemporary armed conflicts", he notes.
He emphasizes that sanctions can last for more than a decade or even longer.
https://nordictimes.com/world/how-french-icc-judge-faces-us-...
(link to malauxyeux's comment where I found this summary: https://news.ycombinator.com/item?id=46738790)
The alternative that's looking best to me so far is Kolab Now. I don't see a lot of user reviews of it on Reddit though, or anywhere else, so it seems to not be very popular at first sight. That's perhaps not a good sign.
In any case I'm planning on trying it out for a while, with a domain I don't use it all that often, before deciding to migrate to it.
"That's the kind of performance that actually changes how you work. It's no longer doing the same thing faster, it's allowing you to work in a completely different manner. That is why performance matters and why you really should not look at anything but git. Hg (Mercurial) is pretty good, but git is better."
(in a talk he did at Google, of which I the I found the transcripts here: https://gist.github.com/dukeofgaming/2150263)
Sometimes making something much faster turns it from something you try to avoid, maybe even unconsciously, to something you gladly make part of your workflow.
Since I started using uv I regularly create new venvs just for e.g. installing a package I'm not familiar with to try some things out and see if it fits my needs. With pip I would sometimes do that too, but not nearly as often because it would take too much time. Instead I would sometimes install the package in an existing venv, potentially polluting that project's dependencies. Or I use uvx to run tools that I would not consider using otherwise because of too much friction.
I was skeptical at first too. It's not until you start using uv and experience its speed and other useful features that you fully get why so many people switch from pip or poetry or whatever to uv.
The massive shift of communications to digital channels has put mountains of data right there for the grabs, which is extremely attractive for people who want access to all that data.
Or don't you have small local businesses (restaurants, pubs, stores) with duplicate names as long as they're in different locations? I know here in Flanders we have, for example, tens if not more places called "Café Onder den toren" (roughly translated as "Pub beneath the tower"). Do all local businesses in the UK have different names?
I have observed countless times how many people fill in a field, than move their hand to the mouse to move the focus to the next field or button, than move their hand back to the keyboard, instead of just pressing tab to move the focus. It's painful to watch. Knowing just a few keyboard shortcuts makes filling in forms so much faster.
Things are getting worse, unfortunately. Modern user interfaces, especially in web interfaces, are made by people who have no idea about those efficient ways of using them, and are starting to make it more and more difficult to use any other method than keyboard -> mouse -> keyboard -> mouse -> ... . Tab and shift-tab often don't work, or don't work right. You can't expand comboboxes with F4, only the mouse. You can't type dates, but have to painstakingly select all the parts in inefficient pickers. You can't toggle options with the spacebar. You can't commit with enter or cancel with esc.
str.split() splits on runs of consecutive whitespace, any type of whitespace, including tabs and spaces which splitlines() doesn't do.
>>> 'one two'.split()
['one', 'two']
>>> 'one two'.splitlines()
['one two']
split() without custom delimiter also splits on runs of whitespace, which splitline() also doesn't do (except for \r\n because that combination counts as one line ending): >>> 'one\n\ntwo'.split()
['one', 'two']
>>> 'one\n\ntwo'.splitlines()
['one', '', 'two']I didn't have the guts to tell my family about goatse.
For something like Facebook, it's OK to use je/jouw. But for something like a government website, or perhaps things like banks or insurance companies, je/jouw is not appropriate and u/uw should be used.
I just checked some samples: Facebook uses je/jouw, LinkedIn uses u/uw, government website MyMinfin uses u/uw. That all seems appropriate, so the choice is perhaps not as delicate as I first thought.
(There is a tool to convert the old configuration syntax to the new, but it requires a working installation. There is a command line option to enable support for the old format, which if nothing else helps to be able to run the conversion tool, but there's no information how to enable that command line option in the way Debian starts pdns-recursor.)
I had another issue during my upgrade to Debian 13 that also wasn't mentioned in the release notes. I filed a bug report, but I was told that the issue was not important enough to put in the release notes, and I should have instead more closely read NEWS.Debian of the package. So I don't really know anymore what the "Issues to be aware of" chapter in the release notes is for, because apparently it's only a small selection of issues you need to be aware of.
We often associate moon with night, and night with needing high ISO, long exposure and wide open aperture. And when you use the auto mode on camera's, that is indeed what you will get because even with telephoto lenses the moon is only a small part of the field of view, so the camera will base its exposure on the dark sky around the moon. That will case an overexposed moon, with a lack of contrast.
(Another issue you'll encounter trying the view or photograph the moon is that when viewed with large amplification, the moon is actually pretty fast and you're going to have to re-aim your camera regularly.)
- com, example.com, foo.example.com are all domains
- com is a TLD
- subdomain is a relative term, not an absolute one:
. example.com is a subdomain of com
. foo.example.com is a subdomain of example.com
. bar.foo.example.com is a subdomain of foo.example.com1,234
in a CSV file SHOULD mean "two values: 1 and 234", regardless of the local decimal separator."
Yes, I agree, it SHOULD mean that, but that is NOT what Excel does when the decimal separator is set to "," in the regional settings. Excel wrongly thinks it should apply the comma as decimal separator, and reads that number as 1 unit and 234 thousands.
Locale MUST NOT be used for data formats, but Excel does it anyway.
This problem doesn't manifest itself when you're using a locale which matches the CSV's separators. Consider yourself lucky if you're in that situation.