One problem with that is that SSRIs are much more accessible than therapy. In my country, they are fully covered by social security and procuring them is relatively easy, while therapy is too expensive for lots of people.

> If you read further in your [1] you'll see that the rate of side effects is not "in excess of 70%" but lower, and it depends on both the medication and the dose. Switching medications and changing doses is often sufficient to ameliorate some or all of these effects.

In my case, and according to studies I'm not the only one, the side effects can be persistent. Neither the doctors nor the medication's notice warned me of this. If I knew that when I was young, I would have made different choices.

SSRIs did help me, but it cost me a lot, and I still cry about it. Of course, there is no way to know if this is a better outcome for me than what would have happened if I managed to refuse to take them.

Some feedback :

- it is.. relatively slow ? especially when focusing on different panes (tab/shift+tab). on my machine it takes at least half a second to react

- the unit list is missing page-up/page-down handling

- in some unit attributes, the ordering of some values frequently changes (for example, on unstarted services, in `TriggeredBy`)

- it could be interesting to integrate the output of `systemd-analyse security`

Nice work !

From https://nuclearweaponarchive.org/Usa/Tests/Brownlee.html :

> As usual, the facts never can catch up with the legend, so I am occasionally credited with launching a "man-hole cover" into space, and I am also vilified for being so stupid as not to understand masses and aerodynamics, etc, etc, and border on being a criminal for making such a claim.

Generally, you want to measure the voltage difference between live and neutral depending on the load. However, depending on the tools you have access to, taking this reading properly can be a bit tricky both because simple high-impendance multimeters can easily be tricked by ghost voltages caused by bad connections and inductions from other cables, and also because understanding what to measure requires knowing how is the electrical system wired.

If you know you are in a TT system with 240V between Live/Neutral, I can tell my procedure for inspecting neutrals. In a two-pole TN-C-S system with 120V between L1/Neutral and 240V between L1/L2, I suppose it would be similar, expect that we'd have to do more tests (both L1 and L2 to neutral, and I imagine also L1 to L2).

EDIT: a first simple check to do is to check, using any multimeter, if there is voltage drop in your office when the hairdryer is in use.

This may indicate that your neutral line is undersized and/or damaged.

The new interpreter is nice, but I wish they had incorporated the display of variable values in the traceback (similarly to ipython's xmode attribute, or to traceback-with-variables), this is something I've always missed in Python.

The write-hole issue did take a long time to fix, and yes it's annoying that the fix requires full RMW cycles, and yes it's frustrating to know that the design of btrfs means that there probably won't be a better solution, but it doesn't mean that "people cannot rely on it after 10 years". Some people do rely on it, it serves them well, if it was that unreliable it wouldn't be the default filesystem choice on a major distribution.

Weirdly, this only happened on a few datasets that were not used a lot, the datasets that have lots of IO have only had the innocuous errors (the ones that refer to deleted files).

I did try debugging some of this with a ZFS developer, but we were not able to recover the data, and digged deep enough to see that something was very wrong with these datasets (it was not just a bitflip somewhere, rather that dataset used a key from the keystore that was supposed to exist, but didn't.

This kind of luxury will always be reserved to the wealthiest in society, and its availability dependent on the relentless exploitation of land and human beings.

I also have my own frustrations with some contributions to the Nix project, where my input and concerns were completely disregarded and ignored, in cases where I suspect that the interests of external companies (heavily invested in Nix) played a big part.

The parent poser never said anything about "evil big pharama mind control", however "pharma companies trying to make money disregarding long-term health of patients" is not a particularly narrow-minded view, anti-depressants are used to put people back to work disregarding their long-term health, and widespread over-prescription of SSRIs by physicians (not even psychiatrists), even to children, is a thing as well.

If 15 years ago, when I was 16, someone had told me that these meds would potentially make me lose the ability to feel pleasure, I probably would'nt haven taken them, but there was no such warning.

Of course, neighbors have started using more and more rat poison, so sometimes I do see some rats dead on the ground, rotting in the sun. And recently, I've started seeing dead raptors in the farmland close to us.

I think at that point I would just have been too scared that this would cascade-delete the old account as well ^^

- unmanaged clients ("power users") get an ONT that is very easy to monitor remotely, and we never had a situation where they were unable to setup a DHCP client

- managed clients pay a bit more and get an AP/router that they cannot directly configure, except for things like the wifi password and some NAT mappings.

It would not make sense to price it this way if we were selling data about their home network, and I suppose that's part of the reason other big ISPs here prohibit their users from connecting to the ONT directly.

You also need to add misbehaving clients on your list of things not to use with a message-queue, just opening the queue's folder on Outlook to inspect it may be enough to completely corrupt it (Outlook will happily reorder, even rewrite, header fields of incoming messages, replicate messages to infinity, or who knows what else).

I'd be worried to have a message queue that is compatible with such a cursed ecosystem and transport protocol.

Yes, ideally, an infrastructure provider should not dictate what kind of IP packets the commercial ISP can use, and there are dozens of technologies that would allow them to provide transports that don't care about the routing layer, but in practice, these providers (that we never really hear about as end-users) often make very bizarre choices, for example setting up a complex DHCP interception schemes that feed both the OLT to "open the port" and a BGP route server to announce connected clients at the collection point, of course not supporting IPv6.

In one of the ISPs I work for, we literally have /48s assigned to all of our clients, but the infrastructure provider's doesn't route them to us : IPv6 traffic is rejected at both ends of the transport. The ticket has been open for years (IPv6 was supposed to be part of the network they were commissioned to build), and insiders told me that they had difficulties adapting their transport system for IPv6.

We may end up having to tunnel IPv6 through IPv4 to our clients, but we try to fight against that so that the infrastructure provider doesn't declare the problem "fixed" and decide that the proper way for ISPs to provide IPv6 is to tunnel it through IPv4 so that they don't have to change anything.

At least with multipart/form-data we get to avoid transfer encodings, which are also quite annoying to handle (especially as they can be nested, which is probably the worst aspect of RFC2046).