> For COVID to cause severe illness in a few % -- enough to kill in rare cases -- but to not cause permanent lung or heart or kidney damage etc. in some significant percent who got very sick is implausible, even incoherent with all other theories about how viral diseases cause disease.
So then why do we never talk about long flu? Long meningitis? I don’t think people are in disbelief COVID can cause long term damage to specific people. Obviously that’s a possibility.
I think they don’t believe there is a specific disease called “long COVID”. Call it what it is - be that a damaged lung or heart or kidney. Hell even “post COVID symptomatic disease”. But “long COVID” strongly implies that you have a long, currently present case of COVID. That somehow just doesn’t show up on any tests. After 2 years.
“Lingering effects of influenza”, which I stated obviously can exist. Would you associate the words “long marriage” with “lingering effects of marriage”?
Not a single one of your sources used “long X” terminology. I wonder why that is? Perhaps because “long X” in the English language refers to either a large length or a large duration of time. Not “after effects”.
I suspect the authors of each paper knew this and intentionally made sure not to imply it was a continued disease. But I suppose when something is politicized people find it hard to move on, such as the COVID era.
The thing about a neologism--the one that's relevant here anyway--is that it's neo, and the linear nature of time means that one would not expect to see it in use before it was coined.
With both RSV and influenza, infection as a baby or toddler seems to increase the likelihood of asthma in later life. Do we talk about asthma?
I think it is just so ordinary, an accepted part of life, and often not thought of in terms of being caused by an identifiable pathogen, that it's not really remarkable. Sort of like the fact that viral pneumonia is what kills the very elderly -- if nothing else gets them first -- the older someone is the more likely viral pneumonia will be the cause of death, rising to around half of all deaths in the 90 yo+ demographic. RSV, rhinoviruses, influenza. We're used to it. And short of getting our influenza shots and washing our hands, there's not terribly much we can do about it.
> currently present case of COVID
Well, that's just people abusing terminology. Technically, COVID is not the virus; it's the illness caused by the virus SARS-CoV-2. Same sort of distinction as between HIV/AIDS. A person with severe AIDS who hypothetically was cured of HIV, would still have severe AIDS until/unless they manage to recover some immune function.
It is poorly named I guess. People still mix up AIDS/HIV today and I don't even bother to correct them; can't really blame them for conflating two closely related concepts.
> With both RSV and influenza, infection as a baby or toddler seems to increase the likelihood of asthma in later life. Do we talk about asthma?
I think this reinforces my point succinctly. It’s not “extended RSV” or “persistent influenza”, it’s asthma.
COVID is a completely politicized term and dying on a hill to use it to describe symptoms people are stuck with after recovering from the acute disease, especially in a way that implies they’re still infected, is just - well you can see what it does.
Asthma induced by influenza would be about right, I think.
Much of this is novel, in having the ability to attribute to a specific viral cause, easily and cheaply and widely. This is new ground, new technology. Much of this was until recently, put up to non-specific viral infection, or even idiopathic.
We may start to re-conceive of asthma as different diseases if we could attribute the factors which went into causing a particular person's asthma. Flu-asthma, toxin-asthma, autoimmune-asthma, and COVID-asthma - and hybrid cases.
Those interested in seeing funding devoted towards the study of this would do well do steer away from the political COVID branding. And if that’s too hard, call it “post COVID disease” or something.
That’s not what LongCovid implies, that’s possibly referring to persistent spike proteins but that a separate thing. LongCovid specifically refers to post covid sequelae, as in not a chronic infection but the after effects from an acute infection.
Viral impairments were called ME/CFS, the main difference now is that such a large number of people got it at one time which is making it more difficult to ignore.
99.999% of the population, including those who claim they have long COVID, do not know the words “persistent spike proteins” or “post COVID sequelae”.
Therefore I assert you are incorrect, “long COVID” implies a “long case of COVID”. Similar to how no one would interpret “long marriage” to mean the after-effects of marriage.
P.S. no I will not cite a source for the statistic nor will I cite one for the sky being blue.
We now suspect that many pre-2020 ME/CFS cases were caused by a viral infection, so in some sense it is Long-Flu or Long-RSV, but we just don't call it that.
I myself still have long-term issues from a non-Covid viral infection a few years back, probably RSV.
Exactly, it's the exact same thing under a new branding. Because of that new branding, most people seem to think it's new and unique when it really isn't.
Does the alternative exist - being uninformed and eager to criticize power? How are we meant to differentiate the two?
I think one way is to note that this post was about being inaccurately charged with a felony - not about cops. The request for stats was not “cop stats” but identity fraud based felony and as a result arrest at routine traffic stop.
If a cop sees you have multiple felonies in another state, it’s quite literally their job to arrest you. Do you suggest they see someone charged with multiple felonies and just say have a good day?
No, the post was about being charged inaccurately due to identity theft. Perhaps you are overly eager to criticize police and became uninformed with reading the comment thread.
I can’t find anything stating this is “very common”. I guess as a rough metric for “very common” let’s say on a similar level to heart attacks. Quite rare still but common enough that you could be justified in calling it very common.
People who own a computer but prefer the iPad form factor, (taller aspect ratio is nice for code), and like having a portable 120Hz whiteboard, and arent afraid of operating said computer remotely via the iPad.
I tried it a year or two ago and I had issues with the keyboard shortcuts (had to disable keyboard shortcuts on ipados) and scrolling behaviour. I seem to recall having other issues with safari and the local files but it’s been a while.
I’m not in a place I can try it out, but if it works then that would open up remote web development.
Yes. There’s also a slightly different version of it it blink shell, which packages a web version of vscode as well. In general this one performs a little better imo and has integrations with local filesystems
I do web dev casually with it all the time via a vpn to my server back home and the inspect app for debugging
Is it that wild? There are a few questions we have to ask
1. Do these agencies have the motivation to do the above? I think the answer here is an obvious yes to everyone
2. Do these agencies have the technical ability to hack the VPNs, the finances to pay them for access, or some other reasonable measure to coerce compliance?
If 1 and 2 are both true, then the OP claim is also certainly true.
Given that 1 is true, I don’t think it’s “wild” to claim that these agencies cannot satisfy 2. In fact I’d say given the historical record, the more wild claim is that the CIA/NSA etc is incapable of satisfying #2.
It's a crime. Maintaining continual access to every major vpn provider increases the probability of getting caught breaking the law towards one while continually risking the methods required to acquire such access each time your implant is discovered.
If you are using unknown exploits not passed on to relevant software projects each discovery further risks said exploit being discovered then used against us individuals and enterprise.
It is a potentially very high cost for mediocre gain as criminals can turn to more secure methods leaving you with a lot of data on whose hiding piracy from their ISP but little of actual value.
Meanwhile you can direct attack targets any other ways when they are likely to have actual intelligence instead of hoping they log into nord VPN.
In brief speculation is incredibly likely to be based on bad logic and should probably attend more to actual know.
Eg most people aren't important enough to directly target. Uncle Sam probably knows the entire contents of your Gmail but not what you do via nord VPN. At such time as you become an international drug lord your privacy is likely to fall apart when Sam starts serving providers who do business with you.
The Interpol literally took over a darknet market (Dream) using stolen admin credentials and continued to run the site for months to gather intelligence on vendors and buyers. Not the same thing but if LE is willing to operate a major illegal drug trafficking operation then surely hacking a few VPN companies doesn't seem impossible.
Great example however unlike constantly hacking all VPN providers this is potentially deemed legal kind of like under cover cops doing controlled buys to trace drug networks. Also unlike hacking all the VPNS. It's also pretty high benefit for a very finite and controllable risk.
What crime is it for the NSA/CIA, who are explicitly tasked by the government with gathering intelligence on foreign agencies, to hack say Mullwad, a Swedish entity? That’s like saying it’s a murder for the police to shoot someone who has hostages. I mean yes it’s the same action, but when it’s been deemed justified by the government, it’s not really a crime in the same way.
A crime in Sweden perhaps. Who will Sweden charge? Do they even have names for individual employees?
It’s also a “crime” to sell false and compromised products to customers yet CryptoAG existed for decades.
> At such time as you become an international drug lord your privacy is likely to fall apart when Sam starts serving providers who do business with you.
Then you’re simply agreeing under point 2, I.e they have they ability to coerce cooperation when desired
Why pay for a whole month though? Depending on your work, spin it up and down as needed. If you're just building a binary you only need it up for minutes or seconds. Been on my mind lately. Lot more sandboxing too. And if you want to build fast you can just scale up your instance since its so short lived. Want to switch from x86 to ARM? no problem. Spin up 40 of your current app? no problem.
That's fair. But above I read about a dev box with Emacs running on it, etc. You likely don't want it to be too short-lived. You can switch it off during night, of course!
I am consideirng going pure ipad + ssh an AWS instance as a dev environment. i already just use ipad + ssh local machine. would have as much automation as possible to spin things up/down when developing. I don't know how I'd set this up to be nice and seamless just yet.
Pay for 3 years of AWS savings plans to make it cheap. Perhaps run a permanent instance for small things, make a setup that lets me spin up super power machines when i actually want to build.
Most of the time I'm at my ipad remoting in Im not actually compiling, just editing. I can just edit locally and pay for the few seconds/minutes it takes to build..
because honestly after about 3 years i always want to upgrade
and i can get windows that are completely functional for me on remote monitors with ipad now. just starting to wonder why im paying for physical compute power but 99% of the time browsing the web and editing code but not building it.
i love orbstack, like actually love it to the point where now i have to complain about its issues a lot, because i cant use anything else
still has a lot of things to imrpove on in general, which are annoying when you encounter them suddenly. most frustrating for me is the "unlimited permission" setup. Sometimes thats useful as hell. Other times i would indeed like to run a servive using the convinience of orb stack, but you know, a little more sandboxed...I loved /Users/yyy/Documents being tied to my iCloud Drive. Had to disable that once i started using orbstack for personal reasons. orbctl / orb really need much more explanation of a lot of the options. especially whatever the config options do.
or let me bind to other network interfaces not just the one :(
but i love orbstack. hard too go back after finding it. impossible actually. havent been at the computer in like two weeks so mabye its changed by now
Totally fair! There are definitely still limitations.
Support for "isolated" machines that don't have bind mounts is planned (https://github.com/orbstack/orbstack/issues/169). This is actually mostly implemented internally, but I'm not exposing it until a few remaining security gaps are plugged or it would just give a false sense of security.
If you meant binding servers to specific interface IPs, it might be possible one day but it's very challenging to implement as all of the host's IPs need to be assigned to an interface in the guest and managed accordingly. If you meant connecting machines directly to your LAN, it'll be supported eventually but it's low priority due to unavoidable compatibility issues. https://github.com/orbstack/orbstack/issues/342
I think you're looking for too much out of a versioning scheme.
If you're seeing 1.2.3 -> 2.2.3, updates, i..e the dev is saying THIS 100% BREAKS SOMETHING IN MY OPINION, and you just do your normal set of analysis and walk away happy that's a bit scary.
If you do anything other than your normal analysis, you've just gone ahead and used semver.
So then why do we never talk about long flu? Long meningitis? I don’t think people are in disbelief COVID can cause long term damage to specific people. Obviously that’s a possibility.
I think they don’t believe there is a specific disease called “long COVID”. Call it what it is - be that a damaged lung or heart or kidney. Hell even “post COVID symptomatic disease”. But “long COVID” strongly implies that you have a long, currently present case of COVID. That somehow just doesn’t show up on any tests. After 2 years.