95 karma · joined March 4, 2015
Well they are placing an increased load onto the side and get nice resources for free, not even doing the cheapest form of flattery: attribution. That's happening a million times on the internet each day, where pictures and other copyrighted materials are redistributed without consent or attribution, and it's ridiculous that the currently most valuable company on earth feels the need to be a cheapskate about that, too.
People lost their mind when Google did something like that in their image search, and unlike Apple, they provided attribution and a prime backlink. If Apple likes the service so much, they could just have bought it entirely and it wouldn't even show up in their balance, so proper attribution, and maybe ask the provider if he/she can handle the additional load, or even provide some support to handle the load, would just have been fair, don't you think?
Next, something like the deletion right has to submit to other laws that mandate data retention, like having to keep sales and bookings records for 10 years due to tax laws. If you do a cascading deletion in your data set, you're probably breaking these, so flagging records as deleted, or moving them to an archive to comply with these other laws still is perfectly find.
So this is just another regulation a startup has to think about. It's way easier than, i.e., tax laws, so please. Just stop panicking -.-
Keep up the great work!
Re: multiple account breaches: keybase.io aims to make that harder. Have you heard about that? (I know, I digress, sorry.)
As for the cert: it _could_ be stolen.
Least flak wouldv'e been a github repo. Most people wouldn't even bother check what's in it and if it matches a binary download, they'd just assume someone else would check ;)
I bet the XML parsing and the sound synth are exactly the two things you're least and most proud of? :D I honestly recommend taking a look at JAXB. You start from a schema description and generate java classes from it. Then you just stuff these classes and a conforming XML file into a JAXB Unmarshaller and get a clean instance tree of the file. Such a tree can then be poured back into a file by way of a Marshaller.
But anyways, a cordial +1 for being a nerd with all your heart! :)