Also it'd be nice if there was an underlying grid plotting the metric/distance function to help conceptualize distance/relationships better when you get to the edges.

Also of all the cryptocurrencies Bitcoin is a pretty poor choice since it could be pretty well argued that it has lost the original purpose and devolved into a raw "line go up" financial instrument.

Other quirks with their writing style seem to lend support to this being an "ESL-ism" as well.

Fun fact this is still practicing medicine without a license. You are just less likely to have someone come after you for it.

If you present yourself in such a way that you could be misconstrued as a medical expert, then if you are practicing medicine, even if you never explicitly claim to be a medical expert you are still practicing medicine.

This is why you see the "This is not to be taken as medical advice"/"I am not a medical professional" verbal condoms all over the place WRT medical discussions. You see the same thing with IANAL for the legal profession as well.

On the one side you have white hat hackers and pen-testers who you pay a contract or salary to prod your system. If you really piss them off (i.e. by stiffing them of their pay) some might just steal your data and threaten to leak it unless you pay them.

On the other side are black hat hackers who will drive by your system and if they find a way to break in they'll offer to keep your data private for a ransom fee. And maybe if you have some charisma, decent pay, and/or a good repertoire you might recruit them on/convert them into white hats for your org.

That's not the situation here. The more accurate case would be:

> If someone without a medical license provided blatantly incorrect medical advice with respect to safe medication usage to an individual via a direct one-on-one discussion, would people be filing lawsuits?

And the answer is yes. You can be wrong and you can say incorrect things. What you can't do is provide medical advice unless you are a licensed medical professional. You can still speak about medical topics but you have to disclaim your lack of licensure. You have to make it clear that you are not providing medical advice.

If this was a person doing this it'd be a crime, clear as day. It's called "practicing medicine without a license" and in the US it is a criminal offense in all 50 states, Washington DC, and all 5 inhabited territories. Whether it is a misdemeanor or a felony is dependent on the jurisdiction and the case but it's a crime everywhere in the US.

They can always just hack them again but with a different method this time.

The ransom doesn't bind them from hacking the company multiple times. It just obligates them to destroy the data they collected from this attack.

As a matter of kindness and good business they'll probably wait a few months or a year or so before poking around again but they'll almost certainly continue poking at Instructure's systems.

Data exfil ransom attacks are a business first and foremost. They don't permanently halt or destroy the original infra and their goal is to get a payout for their labor and move on. Maybe the come back around in the future with another, different attack, maybe they don't.

They made their money and made it big in the news as having complied with the ransom payout, no reason to hurt their reputation trying to double dip. Plenty of other soft targets to poke.

An ischemic stroke (i.e. stroke due to a clot) caused by vascular or cardiac issues can be mitigated. A cryptogenic stroke however is idiopathic and therefore has no understood cause. These types of strokes make up 30-40% of all strokes. Unless we figure out their cause, there's no way to really prevent them.

But then there's also hemorrhagic strokes which are an entirely separate category that has causes and mitigations more or less diametrically opposed to those for ischemic strokes.

And of course those are just your broad painted categories and they are generally looked at as the start of a medical emergency but strokes happen all the time as a consequence of other medical emergencies.

Even if you could perfectly prevent strokes in generally healthy populations, those same people may still end up suffering from a stroke during a surgery or during/after a major accident or injury. No amount of preventative medication can prevent someone suffering a stroke caused by a brain bleed after a car accident. Likewise for someone with a crush injury, internal bleeding, or broken bones that end up throwing a clot which makes it into the brain.

So any advancement in halting and reversing damage from a stroke will be a massive boon for emergency medicine until the end of time. Unless of course we somehow find a way to cure/render humans immune to blunt force trauma or lacerations.

That's not the issue. At least in the US it is unconstitutional to bar inmates from speaking or communicating in non-English languages.

Likewise the US legal system is required to provide you an interpreter who can speak in a language you are proficient in.

Whether these rights are properly upheld in the US is another question but they are rights you are entitled to.

That's the main issue. These are rights that Americans are accustomed to and it's not always obvious to them when they leave the country that these rights aren't universal among developed countries.

The equivalent of a knot in gitlab is a gitlab instance or for forgejo a forgejo instance. There's just not really a clean equivalent.

A knot is a git server but it's not the git host/remote. The remote is the appview (which is the software stack called "the tangle"). The knot isn't just a storage backend either.

The knot is a little bit of a lot of things from the existing models so it just does not and cannot fit cleanly into an existing definition. Doubly so because what the knot does today is not the only things it will do. It will likely gain additional functionality in the future so to give it a reductive label now will only add to the confusion.

Instead it's a knot. That's what it is. And you can explain what a knot is if someone asks but at the end of the day it's a knot and what that means is specific to this project and network.

Minecraft and gmod are still definitely staples of the young internet.

> The answer that came to me again and again was play. Every human society in recorded history has games. We don’t just solve problems out of necessity. We do it for fun. Even as adults. Leave a human being alone with a knotted rope and they will unravel it. Leave a human being alone with blocks and they will build something. Games are part of what makes us human. We see the world as a mystery, a puzzle, because we've always been a species of problem-solvers.

https://taloswiki.org/images/3/36/Scientist-02_ProblemSolver...

Document file formats are a fucking nightmare, especially the Microsoft ones, and needing perfect compatibility with them spanning a generation is hell on earth.

Firefox is a similar scenario but for the web and decades of "it works on the dominant browser but the dominant browser refuses to follow the spec".

And GNOME is a matter of varying levels of direct hardware support/integration and app compatibility across basically the entire personal desktop computer and laptop eras.

Each of those has a compatibility scope that's absolutely massive.

Comparatively Tangled is a greenfield project with no compatibility requirements other than "support git" and "don't break compatibility with itself".

I'll make a proper announcement when it's anywhere close to presentable or even functional and I imagine the tangled folks will amplify that when I do.