Search "YouTube Revanced" on Android. It's a bit of a pain to install, but it lets you customise your YouTube app and add or remove as many features as you want.
These kinds of customisations should be standard for apps people use every day.
You -> Gear icon -> Revanced Settings -> General -> Navigation Buttons -> Hide Shorts.
You need to also hide them from the feed and a few other places. You are not stupid; Revanced has too many options and the settings and large and confusing. It's easier to search "shorts" and toggle everything.
Thank you. I already had that setting enabled, but your comment inspired me to review all the settings again and I have been successful in hiding Shorts from view (for now, until Google changes something again no doubt).
Everything on the internet is fake. That is as true now as it always was.
For every real post, I can make up a fake one that's more agreeable to the hivemind and therefore will be more upvoted. Since you see a limited amount of posts in a session, you will only see fake posts and the real ones will be hidden forever.
The author overlooked an interesting error in the second skull pancake image: the strawberry is on the right eye socket (to the left of the image), and the blackberry is on the left eye socket (to the right of the image)!
This looks like it's caused by 99% of the relative directions in image descriptions describing them from the looker's point of view, and that 99% of the ones that aren't it they refer to a human and not to a skull-shaped pancake.
I am a human, and I would have done the same thing as Nano Banana. If the user had wanted a strawberry in the skull's left eye, they should've said, "Put a strawberry in its left eye socket."
Exactly what I was thinking too. I'm a designer, and I'm used to receiving feedback and instructions. "The left eye socket" would to me refer to what I currently see in front of me, while "its left eye socket" instantly shift the perspective from me to the subject.
I find this interesting. I've always described things from the users point of view. Like the left side of a car, regardless of who is looking at it from what direction, is the driver side. To me, this would include a body.
To be honest this is the sort of thing Nano Bannana is weak at in my experience. It's absolutely amazing - but doesn't understand left/right/up/down/shrink this/move this/rotate this etc.
See below to demonstrate this weakness with the same prompts as the article see the link below, which demonstrates that it is a model weakness and not just a language ambiguity:
Mmh, ime you need to discard the session/rewrite the failing prompt instead of continuing and correcting on failures. Once errors occur you've basically introduced a poison pill which will continuously make things to haywire. Spelling out what it did wrong is the most destructive thing you can do - at least in my experience
I admit I missed this, which is particularly embarrassing because I point out this exact problem with the character JSON later in the post.
For some offline character JSON prompts I ended up adding an additional "any mentions of left and right are from the character's perspective, NOT the camera's perspective" to the prompt, which did seem to improve success.
The lack of proper indentation (which you noted) in the Python fib() examples was even more apparent. The fact that both AIs you tested failed in the same way is interesting. I've not played with image generation, is this type of failure endemic?
Came to make exactly the same comment. It was funny that the author specifically said that Nano Banana got all five edit prompts correct, rather than noting this discrepancy, which could be argued either way (although I think the "right eye" of a skull should be interpreted with respect to the skull's POV.)
Extroverts tend to expect directions from the perspective of the skull. Introverts tend to expect their own perspective for directions. It's a psychology thing, not an error.
Sorry to ruin your fun but in German it's actually just Bürger (capitalized because all nouns are). Though the true etymology might be entirely different.
Bourgeoisie or Burgher in English, Bourgeois in French or in German Bürger, all from old Frankish burg, for town. English has both words, but they now have different meanings, and the term Burgher is mostly obsolete.
The divide (or perception of a divide) between city dwellers and the country is not something the US invented, these divisions predate the colonisation of America.
Runescape tried this back in 2007 along with completely disabling PvP; it was a very unpopular change for the vast majority of players who were not buying items.
I stopped playing the game around that time, so I have to thank Jagex for getting my school grades up.
The grand exchange (auction house) and the trade restrictions that landed at the same time pretty much killed the game for me.
Prior to the G.E., RuneScape had a thriving, complex economy. Players made money transporting goods from harvesting areas, either on behalf of someone or by paying independents for their goods so the independents could avoid going back to town. Players made money buying and selling goods - geographic arbitrage was very much a thing, as well as across time, and also across servers. People made money turning cheaply available goods into more expensive goods.
When the G.E. landed, it basically killed most of the economy. Harvesting stuff could still be profitable, and players could still make money transporting goods from harvesting areas to the nearest bank so people grinding levels wouldn't have to leave, but basically everything else became irrelevant. There's no point in selling anything anywhere yourself when you could take it to the G.E. and get a sale with no effort.
Less of an issue but still sad, the trading restrictions also killed the generosity of veteran players. 'drop parties', where a rich player leads a group around town dropping valuable items, died off as valuable items would no longer appear in the ground for others. Gifting people stuff was no longer possible if it exceeded (fairly low) thresholds. Very sad.
My theory is that Google wants to bake Gemini into Chrome to preempt a future antitrust ruling ordering them to spin the browser out, for the same reason Microsoft made IE an integral part of Windows 98.
Maybe it's a personal preference, but I don't want external programs to ever touch my package manager, even with permission. Besides, this will fail loudly for systems that don't use `apt-get`.
I would just ask the user to install the package, and _maybe_ show the command line to install it (but never run it).
I don't think this should be a personal preference, I think it should be a standard*.
That said, it does at least seem like these recent changes are a large step in the right direction.
---
* in terms of what the standard approach should be, we live in an imperfect world and package management has been done "wrong" in many ecosystems, but in an ideal world I think the "correct" solution here should be:
(1) If it's an end user tool it should be a self contained binary or it should be a system package installed via the package manager (which will manage any ancillary dependencies for you)
(2) If it's a dev tool (which, if you're cloning a cpp repo & building binaries, it is), it should not touch anything systemwide. Whatsoever.
This often results in a README with manual instructions to install deps, but there are many good automated ways to approach this. E.g. for CPP this is a solved problem with Conan Profiles. However that might incur significant maintenace overhead for the Unsloth guys if it's not something the ggml guys support. A dockerised build is another potential option here, though that would still require the user to have some kind of container engine installed, so still not 100% ideal.
I would like to be in (1) but I'm not a packaging person so I'll need to investigate more :(
(2) I might make the message on installing llama.cpp maybe more informative - ie instead of re-directing people to the docs on manual compilation ie https://docs.unsloth.ai/basics/troubleshooting-and-faqs#how-..., I might actually print out a longer message in the Python cell entirely
Hopefully the solution for now is a compromise if that works? It will show the command as well, so if not accepted, typing no will error out and tell the user on how to install the package
reply