What I don't understand: if you look at the lab reports posted by the vendor, it will mention that it contains no alkaloids:

a) Why the hell would you buy this stuff, from a company callef "Shruumz", if it does not contain, e. g. psilocybin / psilocin? Best case, the product does absolutely nothing and you have been duped. Worst case, it does something, but based on a completely different substance / synthetic compound that you know nothing about.

b) If you get a lab report and test for amanita analytes, why is the test profile so narrow? Obviously, a different lab found something after the edibles turned out to be a huge health risk.

Even better, when I opened the lab report for a random product, all it had was results for cannabinoid testing, finding absolutely none - incredibly surprising for a product marketed as shroom edible. Why would a consumer expect or even be interested in cannabinoids in such a product?

Just a shitty company with highly shady business practices. People, don't buy edibles with research chemicals or analogs.

• Thr questions posed here are somewhat rhetorical - I know they're exploiting a legal loophole. But, still: why endanger your health and ruin the experience like that?

How do you mention you can play multiple audio streams at the same time and then claim the OS is designed to let only one app access an audio channel / device? Which one is it now? Let's dig a bit deeper into this:

Also, let's not blame everything on the OS vendor being malicious. In most cases, playing multiple audio streams simultaneously would be annoying. In android, you can absolutely play multiple sources simultaneously, and Android will mix everything together and play it.

That being said, starting with API level 31, Android actually started to enforce a concept called audio focus at the system level. That would be around Android version 12. Audio focus is basically a token that can be requested and handed from app to app, and only the app holding the token gets to talk, everything else is faded out.

I'll agree that enforcing this and not making it configurable for the end user was a pretty dumb move, but that was simply a UX decision, not certainly malicious.

If your phone is rooted, you can work around it, e. g. via an xposed module.

Yeah, pick any random video and you can already tell the gameplay won't be great. For the warrior, it's mostly spamming, the priestess has some AoE magic that basically is all identical but dressed up differently.

Good on the guy to wrap his project up, but other than that... meh.

People often believe they are hearing ultrasound, but instead are hearing clicking noise or sub-frequencies emitted from the capsule that are not actually part of the ultrasound.

Pixel 6 Pro worked marvelous for me all the time. I have the 8 Pro now, and now the fingerprint reader is a real mess.

But yeah, the reader on the back was perfect.

That girl's face on the bottom right is a rectangle.

https://streamable.com/emqc0v

Hey, much appreciated!

Is anyone speaking Chinese able to tell me what the guy in the first scene of the video is crying out? The one where the rocket falls horizontally. I mean, I have a general idea what is being said there conceptually, but I'd love to get an actual, accurate translation.

Yes, targeted attacks like that definitely exist, most famously maybe the most recent social pressure to merge a vulnerability to the xz library by actor "Jia Tan":

https://arstechnica.com/security/2024/04/what-we-know-about-the-xz-utils-backdoor-that-almost-infected-the-world/

This started a whole discussion about relying on (often unpaid) volunteer work for critical systems and the pressure and negativity these people face, which is a discussion that was absolutely needed, and which we are still lightyears away from fixing.

Currently, open source is still treated like this: https://trac.ffmpeg.org/ticket/10341

(I can only recommend reading the whole story around this issue, which boils down to Microsoft admitting they rely on an open source project for something they consider critical to their customers, but not willing to pay the maintainer a bounty for fixing the issue)

That's why there is a huge market for 0-day exploits.

Surely not. But also many employees won't even ask for it, and change will only happen if people care about it.

So first, raise awareness, and naturally, implement those things at any companies you manage or own.

I'm not saying quit your job and become homeless if your employer won't corporate with you on the issue. Everyone should think about how this could potentially affect them and what they can do within the constraints they operate in, though.

As someone else in this thread said, a separate (VLAN, guest) network for work devices, reasonable access rules etc. can go a long way. Eventually, I would like this to become unacceptable though.