No. If you make and distribute security-related software, you should consider the safety of your user.
Your threat model absolutely should include this exact scenario. And you should know enough to understand and implement principles like plausible deniability and repudiation.
Usually the pointer is the blahblah the teacher was droning while you were fantasizing about the attractive classmate sitting directly in front of you
Kid has discovered a new kind of Reimann topological first-order predicate calculus and the mouthbreathing teacher doesn't even recognize it.
all its time buffering.
Could be a zillion reasons for this. Need an actual instance to debug
Even though it's no longer tractable for the casual hobbyist (me) to run a node, Invidious is still usable thanks to absolutely heroic effort by the ~4 organizations still willing and able to invest the crazy infrastructure needed to prevent GOOG from blocking them.
getting what I pay for
GOOG and all its affiliated advertisers -- essentially, every corporation on this planet -- now knows not only all your browsing and watching habits, but also that you are a likely good return on investment for more mining, more fine-grained targeting, more scrutiny.
What did you want it to do?
Did you set up a node? Did you promote it & grow a user base? Federate?
Point is that when graphene gets the distress code, it makes it really clear that it's wiping the phone.
That's the Stupid Part