OneDeuxTriSeiGo

Strokes will never be preventable. You can mitigate them but a stroke isn't really a disease. It's a symptom.

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.

Oh. NGL I've never heard it used in that context before (as an american)

It's a British term for halfway houses specifically for people out on bail.

> The arrogance of American tourists is truly boundless. How dare Japanese people not speak English! Who do they think they are?

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.

As far as I can tell MTP is unique from regular speculative decode because the small model is trained to consume and operate on the big model's hidden state for prediction.

That's not the point. The point is that there is no good, clean name. You can either adopt the brand specific name another org/productline picked for their version (which is somewhat similar but often not the same).

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.

Garry's Mod didn't get replaced. It's still alive and well. The new generation grew straight into it and now are slowly moving to s&box (i.e. gmod2). It's just as lively as ever but other games have blown up by an order of magnitude larger.

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

My guess is that it's the dependencies for the game engine. They use a custom engine but with how fast they got it up and running I'm guessing it's based on a pre-existing game engine which would almost certainly get it put under NDA.

I immediately have to reach for a quote from the game "The Talos Principle" as I think it just perfectly sums up my view on how core play and games are to humanity and how they are essential to what makes us as a species special:

> 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...

The difference is that LibreOffice, Firefox, and GNOME are really really technically complicated.

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".

Oh I haven't uploaded anything yet but I'm around in the Tangled discord (and you can find me on bluesky/tangled with the handle onedeuxtriseigo.nullpo.dev).

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.

> system of the down

System of a Down

> then remix it and it gets popular, their automated DRM system will probably C&D me and their label sue me to oblivion using the same AI.

Yes it will because remixing is not a cover. Remixing is a derivative work of the recording and therefore is subject to the terms of the mechanical license on the recording itself. The copyright on a recording is legally distinct from the copyright on the composition (the melody and lyrics).

You are protected under a provision of the Copyright Act of 1909 to modify and perform your own renditions of the original composition (provided it has been recorded previously). Provided you supply some level of original creative input and don't use the recording in your work, the original rights holder are required to provide you at no cost what is called a "mechanical license" for your cover granting you the right to distribute and sell the recording of your copyright.

In the past, granting of mechanical licenses was between parties (i.e. IP holder reaches out when they discover you made a cover and they grant you a license or you go to court and the court grants you the license. But as of 2021 a non profit body was formed under the guidance of the federal government to handle the blanket granting of mechanical licenses to any and all human covers (provided they did not use the original recording in their work).

If you sample the original work at all then you are now creating a derivative work of the recording and you must negotiate for a mechanical license (which is not required to be free). Likewise if you remix it.

They are soulless because often they are AI covers of existing songs trying to mimic the original artist so that they get substituted in as replacements for the original with limited realization on the part of the average listener.

Which of course that means the AI covers get the listens and the associated revenue instead of the original artist.

So instead of listening to "System of a Down", you get a cover from the AI artist "System of the Down" and now that you listened to that cover you start getting more covers in your recommended from them and eventually you are getting covers from them instead of from the real band since you started listening to them instead.

And even if it's not that extreme, the listener is getting served these knock off covers with no actual person behind them. If the listeners don't realise that's what's happening it will reflect poorly on the original creator and hurt their listenership (which wouldn't be impacted if shitty AI covers weren't being subbed in).

It even gets to the point that now you have artists who have upcoming albums and AI cover artist bots scrape the song list and upload auto generated "covers" of the unreleased original song to try and capture listens that would go to the original artist while people go to pull their music up prior to, on, and after release day of their new album.

Overwhelmingly AI songs on Spotify are autogenerated slop from bots trying to leech off of actual artists by creating a shitty knock off to skim some cash out of those artists' paycheck. (This is distinct from actual cover artists who at least contribute their own unique human touch to the covers).

If you want to make music and you happen to use AI in the process then whatever but Spotify has a major AI cover/clone problem.

Events in atproto speak are changes to metadata/records, i.e. repo/MST events on a PDS.

So for tangled that means federation of issues, PRs, comments, follows, stars, and anything defined in an atproto lexicon. i.e. everything except the actual git repo itself. Those repos are singularly hosted on a given knot for the time being.

Now it's not a huge leap to imagine extending functionality to support cross-knot mirrors but that's not a supported feature yet. And of course you can always just fork a repo instead.

Github has search functionality and grouping of repos by topic, etc. So you can browse repos related to a specific topic. Or you can click on someone's profile and see the projects they've worked on and maybe one of them is interesting.

You got pretty much none of the names right.

Tangle: the appview server of the tangled network.

Knot: the git server that holds an arbitrary quantity of git repos.

Spindle: CI servers/runners/nodes.

Each one is the name of a component and the name for those components is pretty arbitrary.

The jargon is just naming the free-standing components after rope/string related things. i.e. tangle, knot, spindle, etc.

For what it's worth, under the hood tangled is extremely similar to this approach.

Personally as just a random person in the community I've been building an appview for tangled that lets you interact with it as if you were just using git format-patch + git send-email + some MUA.

You can conceptually treat the tangled lexicon as a schema for encoding a git patchset based mailing list into IPLD/atproto records and vice versa. Doing this is slightly lossy but only barely. Otherwise it's pretty seamless.

Well as an example: Lets say I maintain a hypothetical appview for an atproto service and we support SVGs. Users can upload SVGs via our appview or directly to their PDS and we pick them up when the network propagates record updates.

So users can view SVGs embedded in our site and they are regular vanilla SVG images. But say the user copies a link to this image (which we serve via our site or a CDN).

They share the image to a friend via URL and their friend clicks the link opening it directly in firefox or chrome. Now all the scripts in the SVG can execute and the image can rewrite the DOM to present itself as a fake website prompting them to log into their bluesky/atproto account to view the content. So said friend types their credentials in and the script in the SVG sends that back to their C&C server.

In this case the VC in question is funding various atproto projects as they are one of the primary backing VCs for Bluesky.

So even if they don't expect returns from a given atproto project, they are investing money (and therefore funding FTEs) in the ecosystem at large.

The investment isn't necessarily in any one of these projects in isolation. It's in the AT protocol at large.

Exactly. I'm personally slowly working on my own parallel "appview" of tangled that is accessible exclusively via SMTP, IMAP, JMAP, and eventually integration with a Lore + Patchwork frontend.

> who will be there to fix bugs and maintain it?

Those of us who use it. Tangled is a neat project and architecturally it makes a lot of interesting choices but code-wise it's relatively simple and from my personal forays in it I'd say pretty easy to maintain.

The majority of the codebase is loosely related go modules. Then some static HTML+CSS. And finally a small sprinkle of typescript to tie things together. And of course a bit of Nix for orchestration.

IIRC it all runs on a pretty trivial amount of hardware that a single person could currently host by themself.

Users' knots, spindles, and PDS (plus atproto at large) do the real heavy lifting infra-wise.

That's a fair point.

That's not particularly true?

A malformed JPEG or PNG might have potential vulnerabilities but they are considered a failure of the browser or parser lib to mitigate.

An SVG however has vulnerabilities and those are directly built into the spec of well formed SVGs.

If you control the domain then yes you could. But if I want to put a link on my website to some SVG hosted elsewhere and I want it to be safe for you to open that link in a new tab then there's not really a way for CSP to protect you the user from the host deploying a malicious SVG.

Like opening a PNG in a new tab is harmless but opening an SVG in a new tab is opening a pretty substantial can of worms.

it'd be nice if there was a way to declare in the URL that a given SVG could only be treated as an image so that you could safely open SVG urls, etc without exposing yourself to the dangers of embed/inline.

A vulnerability is distinct from unintended behavior.

Unintended identification is less than ideal but frankly is just the nature of doing business and any number of niceties are lost by aggressively avoiding fingerprinting.

In software intentionally optimized to avoid any fingerprinting however it is a vulnerability.

The distinction being that fingerprinting in general is a less than ideal side effect that gives you a minor loss in privacy but in something like Tor Browser that fingerprinting can be life or death for a whistleblower, etc. It's the distinction between an annoyance and an execution.

> Why? Voyager 2 has more power to spare, per the prior quote.

Because Voyager 2 has different equipment active. It still has the Cosmic Ray Subsystem active.

> It's really not uncommon, I find it hard to believe that you've never run into shit/barf, usually when a car pulls up that has nobody in it, that's what's in there.

NGL this isn't surprising on Japanese trains either. Especially around last train. It's not super common but you see it from time to time and you just use a different car and report it to the staff next time you see someone.

> All the random busker type nonsense, the petty crime and the “mugger wallet” type jokes.

Most of this is stories. Yeah there are buskers but tbh I like buskers. Music in the public square is a plus not a minus even if it's not my personal preference of music.

Subway crime rates are around 2-4 incidents per million rides. There was a spike during covid and it started to rapidly trend down afterwards. That corresponds with economic desperation during that period pretty cleanly.

But that 2-4 incidents per million rides is roughly comparable to the crime rates at gas stations, etc. The difference is that density is lower so you just see it less often. It happens just about as frequently but you are less likely to witness it because you are less likely to be present when it happens to somebody else at a gas station.

> I’d still rather not deal with the expected culturally imposed insanity that the Japanese curiously seem to lack.

Trust me Japan has just as much of an issue with crime on rail. Arguably they have higher rates but the Japanese police often just don't consider sexual harassment or sexual assault a serious crime and would rather brush it under the rug or otherwise deal with it outside the criminal system to avoid harming the abuser. (ex: an incident that I'm familiar with: "oh we gave the guy who assaulted you on the train your address so they could mail you a hand written apology note instead of charging them with assault")

And the "wacky in your face" crime (intoxicated, mental illness, etc) is still very much an issue in Japan but it's cracked down on by police in places that tourists frequently visit during the day and otherwise everyone just expects it so people who live there don't really mention it to tourists.

I mean hell look at Shibuya Meltdown for some of the more mild "funny" examples.

The only real difference between the NYC metro and the Japanese metro is that it's louder because there's not a social norm to limit talking on the train (until people are drunk ofc). Otherwise it's all the same shit and you see it all when you start commuting.