Because lots of people I talk to where I live (eastern Canada) don’t seem to realize this: the forcible “transfer” (i.e. deportation) of children is an act of genocide according to international law.

Most recently, KeyWe and modded Keep Talking with friends. Solo, still ol’ reliable slay the spire.

I have a plan to teach someone how to play schnapsen and crazyhouse chess tomorrow so that’s exciting.

I find there’s a lot less variety in my monster train runs. Most classes have a distinctly best strategy and the artifacts generally also funnel you towards that strategy. For example, I can’t remember the last time I played an Umbra run that didn’t set up a morsel engine behind a warden or alloyed construct - as far as I’m concerned, those are the same strategy, it doesn’t feel different. The only other build I think is viable is just “play Shadowsiege,” which rarely happens early enough to build for it.

Every class in STS has at least three viable archetypes and almost every run within those archetypes still feels different to me.

I almost exclusively play for A20 heart kills. I play all 4 classes but in a “whichever I feel like today” way. I tried rotating between the characters for a while and really didn’t enjoy playing silent or watcher while in the wrong mood for those classes.

My favorite deck in recent memory was probably a silent discard combo with Grand Finale as the only damage-dealing card in the deck. My favorite archetype in general is probably ice defect. A good all-you-can-eat ironclad run is great too.

I don’t think I agree that STS is especially well balanced - some regular hallway combats do irrationally more damage on average even to players much better than me (for example, floor one jaw worms or any act 3 darklings). In general, the game could be quite a bit harder on A20 and still be fun for players who want a challenge. It’s also weird to me that A1 makes the game easier compared to A0. Between the classes, there is a class which is clearly stronger than the others. However I also don’t think this is a bad thing. Imbalances create more opportunities for new experiences, and for different kinds of players to have different kinds of fun. And that certainly agrees with “infinite replayability.” I’m sure in 5 years’ time I will still be seeing interactions I’ve never seen before.

Some of these depend on dialect - where my family is from, gaunt and aunt rhyme, for example.

Of course, that makes it worse, not better :P

I’m a computer scientist mainly but with a heavy focus/interest in computer architecture. My plan is to teach at a university at this point - but it seems to me like that would be a good place to create completely open standards technology from.^1Specifically because if the point isn’t to make money, there’s no reason to create walled gardens.

There’s certainly enough interest from people who want to be able to build their own systems. What would actually worry me isn’t the ability to make a new open standard or any of that. It’s that AMD64 is very hard to compete with in this space, because the processors are just faster, and there is so much x86 software that people who build PCs usually want access to.

AMD64’s performance is the result of years and years of optimizations and patenting new hardware techniques, followed by aggressively litigating people trying to compete. ARM performance is catching up but ARM prefers licensing their core IP over making their own systems, making it harder for them to break into the PC space even if they want to.

A new player would be in for a long, long time of unprofitable work just to compete with AMD64 - which most people are still happy with anyway.

^1 some others and I are actually working on some new ISA / open soft processors for it. However it is focused at an educational setting and unlikely to ever be used outside of embedded devices at most.

Invidious does use a YouTube API. FreeTube uses Invidious, so probably same story there. I don’t know about the others.

I recently had a back and forth with one of invidious’s developers. Judge for yourself.

Yeah i think you found the boss on accident if that’s the quest name you were seeing.

But so did I, so this can’t be that uncommon. I question the design of having some mid-game content in the same (surface) place as the end-game because it becomes unclear what you’re being pointed at. Put simply, tell me to walk towards the giant chasm; I’m jumping in.

I realized I wasn’t supposed to be there yet when I recognized a typical pre-boss pattern that Zelda games use a lot. Trying to avoid spoilers there.

Patrick’s parabox?

Yeah, these are examples of the bad gameplay patterns I was referring to. One of them in particular (trying to be spoiler-light) provides you a ranged power… But you have to go to melee range to activate it. Whose idea was that?

Casually, I enjoyed it a lot. It felt like better BOTW, with much more new stuff to explore than I expected. My only gripes where the delay on quick menus (botw did not have that, and it feels awful) and I generally think the sage mechanic leads to bad play patterns. But overall, it’s amazing.

I’ve been involved in speedrunning both games. Versioning issues in TOTK are way worse. Movement tech in botw was a lot more interesting and varied, until windbombs were found anyway. The menu lag feels even worse while speedrunning. The stuff we’ve got for inside shrines is pretty cool, and there’s some very cool out-of-bounds stuff found already. So it’ll probably stay fresh for a while. I’m not sure if it’ll hold me for as long as botw did though.

To his credit, Ohanian hasn’t been involved with reddit for a while. He and u/spez sold the company years ago, then spez came back.

I totally agree. Just want to point out you mean “raze.” I was confused for a bit.

But that feels terrible if you want to follow them without stopping (or in the case of obstacles, are able to).

Even Ocarina of Time, in 1998, got this right. The Dampe race, which isn’t technically an escort, would feel weird if Dampe was too much faster or slower than you, because it would feel unfair. But not everyone moves as fast while playing - some people like rolling, which is a different speed from walking, etc. Also, he throws fireballs at you, and players who are less good at dodging them will end up being slower. So Dampe doesn’t “follow you,” (in fact, he spends most of the thing in front of you), but he has a rubber band effect. If you get too far behind, he slows down. If you get too far ahead, he speeds up. This does a good job of keeping him in view, which helps give the feeling that you’re going at an intended pace, whatever reasonable pace you take. If you’re too slow, you will fail, but… it pretty much requires standing still or getting hit by lots of fireballs.

In contrast, the Yunobo escort in BOTW feels terrible casually and even worse to speedrun. He’s faster than you walk, but much, MUCH slower than you run. And if you get too far ahead of him? He stops.

“Valid” and “disingenuous” mean very different things. How would you feel about editing that README point to be explicit that you use an undocumented YouTube API?

For the record, I don’t think “InnerTube” would be considered unofficial, legally. It’s authorized by YouTube, since they made and use it internally. That’s the definition of “official.” This is a small part of why I think the wording in the TOS makes the TOS apply to “InnerTube.” What makes you think that it doesn’t?

I’ve replied to that, I’m not satisfied. It’s a bit of a wall of text though.

TL;DR: “clean room reverse engineering” has a specific definition and I don’t believe it applies here. I do believe that the cited TOS applies to an internal API endpoint which is publicly accessible. Both things spell trouble.

I also take issue with the phrase “does not use official YouTube APIs” in the readme, but maybe that’s pedantry between “official” and “documented.”

That makes Invidious’ readme (which claims no YouTube APIs at all) disingenuous at the very least.

More likely, you need a lawyer. I read that TOS, and I think it applies to any YouTube API endpoint, internal or otherwise. Best of luck, because I agree with Invidious’ goals…

Side note: a browser communicating with YouTube would be communicating with youtube. Not with com.google.android.youtube.api or whatever. What I’m seeing is that Invidious tries to act like the youtube service itself, which is very different from acting like a browser.

Edit: I’ve spent about 5 minutes looking for EU case law about this but haven’t been able to find anything except un-cited references to an exception for “producing interoperable devices.” Do you have sources? In the United States, at least, “clean room reverse engineering” has a pretty specific definition that follows four steps:

1. A (team of) engineers reverse-engineers an existing product, in this case, the YouTube internal API.
2. Those engineers write a specification of the product’s (outwardly-visible) behavior.
3. A lawyer reviews that specification to ensure that it does not contain anything infringing on any copyrights relevant to the product.
4. A separate (team of) engineers re-implement the product according to the specification.

I don’t think what you’re doing meets that definition. You achieved step 1, and possibly step 2, and then didn’t attempt the others. You reverse engineered something for the purpose of using it - but you haven’t actually reimplemented it, which is the “clean room” part of “clean room reverse engineering.” Re-implementing it would presumably require building your own server for actually hosting videos on Invidious instances.

There’s quite a history of this term in the US, going back to even before Intel vs. NEC, when it was very much in the public eye. As part of arguing that case, NEC, following this procedure, produced a clean-room re-implementation of Intel’s popular 8008 microprocessor’s microcode. To do that, they had to re-write all of the microcode from scratch. Not figure out how to inject the 8008’s microcode into their own hardware design.

Anyway, all that aside, even if what you’re doing did meet the conditions of clean-room reverse engineering, I don’t think it would fall under the (again, un-cited, so maybe we’re talking about different things) interoperability exception in the EU. You’re not producing a device/service that needs to be interoperable with other devices/services. You’re producing a service with an explicit goal of operating differently.

To be clear, IANAL, but your reasoning seems shaky.

It’s certainly possible to scrape data from interactions with a site directly, without using its API. This is even legal - there were no gymnastics in my response there. However, that decision has since been remanded, then re-affirmed, then challenged, and then LinkedIn obtained an injuction against HiQ which the two of them are still fighting over. So it could get properly overturned.

I definitely thought it seemed like it would be difficult to do this to offer a youtube frontend, but plausible enough that I didn’t look into it. Thank you for this. I’m looking more closely now :)

If they are using undocumented internal APIs, do YouTube’s API TOS apply to those? I checked the text of the TOS and it seems to me like it should apply; they say “The YouTube API services … made available by YouTube including …”. That seems broad enough to me to cover internal APIs as well, if their endpoints are accessible, but IANAL.

Also, the open response to the C&D seems to throw shade at the TOS saying “The “YouTube API Services” means (i) the YouTube API services” but ignores that this is immediately followed by parenthetical examples and qualifiers. The TOS is defining the term so that it doesn’t have to repeatedly add the qualifiers. Nothing weird about that. That’s uh… pretty bad-faith arguing, if I’m interpreting it correctly.

Edit: assuming you refer to the same reverse engineering points that they made above… yeah.

I used gbf-dtb’s fork. It seems like they’ve updated it to be easier to install since then as well. I used it by manually updating the URL to grab the script from in j0be’s bookmarklet, but gbf-dtb appears to have re-linked to a codepen with a corrected one for easy installation now.

They’ve (convincingly) followed up above. I’m hoping the contributors to Invidious can clear this up. If no one replies here, I’ll open an issue on Invidious’ GitHub page asking that clarification be added to the readme on how their YoutubeAPI wrapper is not using an official YouTube API.