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?

I’m a bit confused by your comment. They say in their post that they will reevaluate when Lemmy’s mod tools improve. More granular control over federation could help too. It’s a temporary measure.

It’s not like they’re taking extreme action because they want to cause schisms. “They will defederate with everyone” only seems to apply if every other huge instance also has high numbers of trolls. Maybe not so unlikely, but mod tools on Lemmy will hopefully improve by then. Note: you sign up for beehaw’s rules when you choose to interact on beehaw, not when you sign up to beehaw. The issue they are dealing with here is that they have had to disproportionately moderate users interacting on beehaw coming from those instances.

And at the end of the day, if beehaw becomes too isolated, it takes like 5 clicks to open a different instance in my browser and sign up there instead.

Lemmy specifically hasn’t implemented less harsh measures yet. This is a stop-gap action to cut off a trolling problem at its source. The beehaw admins say they will reevaluate when less drastic tools are available, e.g. allow beehaw users to interact with lemmy.world but not the other way around.

I’m not sure I 100% agree, personally, but beehaw’s ethos is “be(e) nice” and if trolls are trolling, it can make it very hard for some people to open up and contribute. So I see where it’s coming from.

Shadow of the Colossus and Undertale.

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.

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 unofficial 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?

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 over an hour 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. NEC had designed a microprocessor with the same instruction set as the popular Intel 8080 [same instruction set = interoperability]. Internally, both devices use “microcode” to drive their execution. In the analogy, that microcode is the “InnerTube” API. NEC’s “V20” device was quite different from the 8080, and needed its own microcode. Intel claimed that NEC violated Intel’s copyright by basing NEC’s microcode on the 8080’s. As part of arguing this, NEC rewrote their microcode from scratch following proper cleanroom procedure, and the decision in the case partly relies on this to decide that NEC is in the clear. Had NEC simply injected the 8080 microcode into their NEC-V20 device directly, the case would probably have gone very differently. It would also be a very different case, because the NEC-V20 device would look completely different.

You didn’t re-implement InnerTube. You injected InnerTube into your own service. Had you re-implemented InnerTube as part of Invidious, Invidious would look completely different.

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.

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.

I’ll admit I hadn’t seen that, and that I was just echoing what TheFrenchGhosty said. That sure does look like official API access. They also seem to make calls through that wrapper to access comments and plenty of other things, so it’s not just sitting there unused.

Thankfully, TheFrenchGhosty is on the Fediverse, so let’s ask them: @[email protected] @[email protected] (not sure which one of these to use) How is this not using an official YouTube API?

The README and the refute of YouTube’s C&D letter both claim that Invidious doesn’t use YouTube’s APIs at all - not merely that the response creation/interpretation was reverse-engineered. Obviously, the TOS applies to the fact that you interact with the API, not whether you access it manually or with the help of some code pre-prepared by Google. Yet it seems that other people have vetted you and not raised this issue. So I’m assuming we’re simply misunderstanding here, and hoping you can clear it up.

It’s not dismissible on NSFW content - this includes things that are not actually 18+ such as r/chairsunderwater posts where the chair is… Not Fully Submerged underWater.

I think it is impressive - I am literally impressed.

They managed to take a service that many people considered the single point-of-access to the internet, and killed the site for those people in under a month.

Make sure it actually overwrote all your comments. PowerDeleteSuite doesn’t respect the edit rate limit. I used a fork which runs much slower but respects the limit.

Also, it’s a good idea to wait several days between the editing and deleting your account. Many users on reddit were suggesting that reddit holds on to pre-edit text for a while. Obviously archives hold onto it forever, but if your goal is to deny your content to reddit, that’s orthogonal.

Are you asking who believes that signal is the gold standard? Other encrypted chat services implement “the signal protocol” now, so… if not gold, it’s at least standard.

Well sovereign citizen argument is just plain stupid; “I live on your soil but your laws don’t apply to me because I say so.”

Here, youtube is claiming something specific (that Invidious violates a TOS agreement which Invidious agreed to) which is verifiably false - Invidious never agreed to the TOS for the API, and doesn’t have to, because Invidious doesn’t use the API. Invidious works by communicating with YouTube and scraping data from the responses. There’s legal precedent that this is legal (although, LinkedIn’s ongoing battle with HiQ may overturn that precedent, but it hasn’t yet). That’s one of the reasons that most services like youtube offer an affordable API in the first place - 3rd party tools using web scraping is much more expensive for them.

YouTube could still potentially legally force them to stop by changing the TOS of the service itself, but there could be other implications of that, so we’ll see what happens. As FOSS, it’s unclear what they would even do, there are hundreds of hosts.