That doesn't actually help; I've had strikes against some of my own videos where I'm playing my own music because I happen to use a royalty-free drum loop that some other song used, or I play the same note on a standard synthesizer patch or the like. I've also heard of copyright claims against recordings of birds chirping, so I guess Universal Music Group intends to sue nature too.

Amazon still uses pages for their oncall, because pagers still have a better SLA than cellphones. However, it comes at a price: their communications are unencrypted, and work on a broadcast basis. Also, they don't do a store-and-forward type thing (their "redundancy" is done by just broadcasting each message a certain number of times spaced apart), so if you're outside of the coverage area when a page goes off you'll never get it (unlike with SMS where most carriers will hold on to it until it's been delivered) so it's still not totally reliable. Personally I would recommend setting up a Twilio app that sends the message to email and SMS, and if not responded to within a certain period of time, starts calling phone numbers and using their text-to-speech API.

You can also just store the data in a less-efficient way using QR codes or other such encodings that allow you to recover the data from the patterns of the pixels. And you can split large data files up into many many smaller chunks, and even store the index for the chunks in another image file.

Feature requests can grow infinitely, as can the number of duplicates of existing bugs. Unless you're diligently closing/merging duplicates and triaging feature requests, you're never going to plateau.

yet another person who has never heard of buggy implementations and privilege escalation

you obviously are bereft of pop culture as a common reference to the rest of society

Once upon a time I found that old, obsolete AT power supplies made for a pretty good more-or-less-regulated high-wattage DC power supply for powering all sorts of random circuits which needed more amperage than any typical wallwart that one had lying around.

All of the spammy job postings I get are for things like "DB2 admin in Podunktown, Anywhere" when my resume hasn't even listed DB2 in well over a decade.

I love how lately people are trying really hard to look like they're reading my LinkedIn profile before contacting me (and going so far as to contact me via an email address listed on a site linked to from said profile), but they don't even bother to get my first name right or proofread to the extent of even noticing red squiggles underneath obvious tpyos.

Remember, that delicious tap water was once pooped in by a dinosaur.

GNOME shell exposes performance issues and driver bugs, which in principle means that those performance issues and driver bugs will (hopefully) be fixed, making the drivers more robust and performant down the road. How's this a problem?

Sadly, for quite some time people actually believed that was real. I had several well-intentioned friends trying to convince me that I should drop C++ and learn [insert fad language here] because Stroustrup was being evil when he designed C++.

Whatever happened to the already-existing "cite" element and attribute that have been a standard part of HTML for years?

I see it as being beneficial mostly to the vast majority of web designers who don't actually know HTML and just export stuff directly from DreamWeaver or whatever. Also, I haven't looked at this particular player, but I would hope it has a nicer set of controls than the default HTML5 video container's controls.

Nearly everyone seems to be missing the point to this. It's not something the user installs, it's something that content providers use to provide their video on the server side. This is a GOOD THING - it makes it much easier for websites to transition to HTML5 without alienating users who don't have HTML5-capable browsers.