> False dichotomy. The recommendation is for people on SSRIs to also do therapy.
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.
- That the tab pane switching is the slow part is a bit weird. Is there a difference when you see all units and a subset of units? Maybe open an issue and I can provide more possible settings that could be changed.
- Jep, page up/down handling will be added. Thanks!
- Not quite sure when this happens. Maybe an example screen shot (before/after) could help?
I've opened an issue about the reordered attribute values (+ another bug I found). Tab pane switching stopped being slow (I suppose my laptop was simply overloaded, and I'm too used to things being fast even when it is).
It's an interesting event, but this article is a bit misleading, and the title outright wrong : the object did not reach space in any meaningful way, and Robert Brownlee never said that it did. In fact, since meteors with a similar weight coming in at a third of the lower bound of the manhole's velocity can not reach the surface, we can assume that the manhole burned up in the atmosphere pretty quickly.
> 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.
A first thing to test would be that your voltages are nominal, but the exact details depend on how many phases are coming from the transformer, how they are wired, and whether you are on a TT, TN-C-S or other kind of grounding system, which depends mostly on where you live. Also, you need to take your voltages both at low impedance (simulates a load) and at high impedance (negligible load, "classical" meters are generally high impedance).
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.
Type defaults are a nice addition, they were something I lacked a lot back when I was still writing Python code.
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.
I agree with Josef Bacik, the constant trashing of btrfs is getting really annoying and disrespectful to the filesystem developers, and it's sad to see how another filesystem developer refers to btrfs.
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.
I've had a few cases data loss related to ZFS encryption, causing a total loss of a dataset and all of its ancestor snapshots. The key used by this dataset is simply missing from the keystore, and so it fails mounting with I/O error. We have no idea why or how could it happen, but the pool also had a lot of these "innocuous* bugs, while ZFS never reported a single error from the backing disks. This happened on two different full rebuilds (from scratch, using zpool-create and manual recreation of all datasets with rsync) of the same pool, but on the same hardware and with the same workload. I am 99.999% sure that this is caused by the native encryption code, probably compounded by sending very regular snapshots (not raw, though).
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.
With climate change and our general impact on environment worsening each year, our relationship with technology is starting to be like a big elephant in the room. Do people really think a sustainable and equitable society is possible while having microprocessors and telecommunication devices in beds ?
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 empathize with what you're saying, but "we shouldn't have things people want" is a solution to climate change in the same way that "we shouldn't have gravity" is a solution to air travel. It's not gonna work. Find another approach.
It's an overpriced bed with a tiny computer in it. It uses the same resources as a cheap bed + a tiny computer and lots of people have those. There's no extra exploitation going on here, these beds are just expensive because they're paying a bunch of engineers to do questionably necessary things.
The problem with activists is so many of them are foolish and just like complaining about things. Go find an actual problem to solve.
Puritan morality is so deeply embedded in our culture people don't even realise they're repeating it.
If I told them they couldn't have a coal-fired home blacksmithing setup "for the environment" then this would seem unfair.
But a 10c microchip? Suddenly this must be evidence of excess! (Even though the price represents that fact that it's a staggeringly efficient use of resources that also has supply-swappable carbon impact).
For every ISP serving my area, it is indeed a "per customer, immutable" prefix. IIRC, some have a 96-bit prefix, some have a /64, but that's the kind of thing that a "maxmind" style database of prefix length per isp lets you nail down easily -- if those databases don't already exist today, they will soon.
I hope this call to action will come to some form of resolution, as I indeed feel quite uneasy with both the current state of the Nix project and with the involvement of contractors such as Anduril. I've lost good friends that died crossing borders to find a better life, and I'd prefer to stay away from projects involving the tracking of migrants by ML-trained drones running Haskell and NixOS. However, my current livelihood is built around Nix, so I cannot simply threaten to quit using and contributing to NixOS, and going back to Debian after the Nix experience would be quite frustrating.
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.
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.