Which aspects are you questioning? It's not my favorite piece I've seen published — I don't think it covers some areas in enough detail and leaves room for insinuation (e.g. Yarima was young when they met, but it wasn't until years had gone by that a relationship occurred. They (David's parents) have spoken as recently as ~7 months ago on a satellite phone, and Yarima has expressed interested on returning to America to visit on multiple occasions. She misses David's father and the relationship they had.)
David's relationship with his Dad is still strained from when he was young, there's no denying that (from my perspective). But as David's interest in Anthropology has grown, so has their ability to find common ground as individuals. I've seen him on the phone talking with Dad for hours, just like any other son.
Is this the right place to divulge information about a third party? I realize there is an article about him posted here and that it already contains lots of details that would normally be considered private, however I feel that somehow if you have questions about this it might be better to take it off-line. Especially parts about his father and mother's relationship in the present, it has absolutely no business being in a public forum like this. We're not exactly discussing people that have been dead for 50 years.
'jameswburke claims to be his friend. I think we can leave the question of what to reveal to his discretion. What he's said so far doesn't seem to me to be particularly sensitive, nor any more private than what was in the article.
no one can downvote submissions, regardless of karma. The reason this is on the front page is that at time of writing, 32 people found it interesting enough to vote up. If you don't like the article, don't read it. Your post is not useful to anyone.
I'm curious about your choices here, I would not really trust MongoDB with my data for a few reasons, but at the same time, building on Google's services seems even more risky - if they shut down those services (which is not inconceivable), you'd be facing a pretty nasty rewrite + migration to a new platform.
This sounds like you never actually bought the domain in the first place. No one likes issuing refunds - namecheap would be flat out crazy to implement such an automated system. Not saying it's impossible, it's just improbable.
eBay was likely one of the largest AdWord buyers. They seemed to have spamming landing pages in Google for a long time but were never penalized. They stopped being a huge AdWord buyer. Soon after they were penalized in Google's search engine rankings. Coincidence? When there is that much money involved, and a possible exodus of Wallgreens and Amazon away from Adwords, I am not completely buying it. Google would be stupid to allow that to occur.
This. Can't be said enough. There's almost certainly not a concerted effort in Google to de-rank eBay, and you'd immediately hear it leak from one of the many people who would have to be involved if there were.
It doesn't have to specifically target eBay to have the effect one wants. One just has to go after characteristics of spamminess that they didn't prioritize before. Like i said in another post, eBay has been spammy for a while, but it was not penalized.
Think this was one of those cases where doing what's right by user also happened to be a crafty business move. They might have had it coming a while and decided to time it right.
Its not really odd, its a natural way to convert a quantity stated in three units that have no obvious relation even to each other to someone unfamiliar with the pre-decimal system into a quantity stated in a single unit.
Its so trivial to set up a shell company that we can assume the trolls are running one per patent. If a shell goes bankrupt they only lose that one patent, which has been shown to be worthless anyway
The markdown parser should be able to do it in an ideal world. Htmlpurifier is very slow.
edit:
To whoever downvoted me, I'm sorry, was I wrong? The markdown parser has to look at every input byte, obviously it's better to do the HTML sanitation at this level because the HTML parser must also look at every input byte, so, combine them into one pass...
Running HTMLPurifier on the output of the markdown parser is inefficient - it's sanitizing known good elements not just the potentially bad ones, so you're giving it more work to do.
it's going to be computationally difficult but not impossible to break an individual password, but breaking all of them is unlikely in our (solar system's) lifetime.
However, if you were targeting a specific user and they didn't use a particularly strong password, it's possible that you could brute force it.