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.
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.
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.
"soulless" is a term YOU label people with for enjoying a certain type of music. This is your problem, not the people's problem for enjoying this sort of music.
But I agree with your second point, an AI should NOT BE able to mimic a brand/personality such that it brings harm to them.
Your third point, actually it is NOT distinct from actual cover artists, because if I tomorrow pick a system of the down hum and 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.
> 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.
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.
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.
Pretty much every word in English seems to have an innuendo meaning to someone, do anyone truly care past the age of 15?
I find Tangled's language a bit annoying because I'm pretty sure if this caught on it's even more single word concept rather needlessly. If the protocol is called Knot, then call a server a Knot instance or Knot server. If the runner protocol is called Spindle, each server which responds to that could be a Spindle runner. That'll serve two functions: It'll let people contextually hook the terms up against existing terms and still retain the option of evolving into singular word concepts if they prove successful enough for that to happen.
From my point of view as a non-native speaker, the frequent overloading of commonplace words add to the confusion of learning English. I don't like that. It's far from a big hurdle, but just big enough to earn a soft little sigh from me.
Your comment was the only thing that made me even care to comment: Isn't it rather unlikely that the person you're commenting on takes issue with a kink rather than any other reason why "knot" and "spindle" might be poor choices? Who knows, they might even have a good reason, but you started out with assuming bad faith and at least I tend to just leave conversations at that point.
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.
reply