jtheory

I especially appreciate this on the assumption that it will be pulled in as input for AI training.

Fathom takes privacy pretty seriously - they're still somewhat early stage in terms of functionality, but a great place to start.

My company relies on DynamoDB, so we're totally down.

edit: partly down; it's sporadically failing

Nah.

Java applets involved running an actual JVM on every client computer, which meant basically doubling the risk surface of the browser... plus you had a completely different UI (that couldn't match the browser UI) sitting inside a web page.

I confess I wrote a bunch of Java applets back in the day; but I can't say I'm surprised they died, and I don't think they'll be back.

100% yes.

It's also about the entire internet & its users, not just threat models on specific sites.

We can't ask the general public to consider threat models and evaluate what sites should need HTTPS or just HTTP. General, non-technical intuition is basically useless for this eval; it's not a good path.

It's much smarter to just make HTTPS the default, make it easy & free for any site to provide it, and then let browsers show big warnings for any site that's not secured.

(Browsers are moving this way already)

I did not get the sense that this is a balanced perspective.

The author does have a point that not sterilizing your pet will likely lead to criticism, even though it's a more nuanced situation.

But still — the solution to all of the sourcing problems is "do your research, and get an individual, not a breed".

If there's an actual shortage of adoptable dogs in your area, talk to the shelters about it, and also consider _not getting a pet quite yet_, rather then taking random advice from the internet and telling people to breed their pets.

Personally I'm in France: much less neutering here, but also there's a serious feral cat problem in my village, and also too many puppies. And toxoplasmosis infection rates are massive... it seems like a much more obvious choice to sterilize free-roaming pets, but still many don't.

Both using LetsEncrypt.

A few maybe-useful thoughts:

* setting up LE & an auto-renewing cert isn't too hard, and it feels smarter than paying for a cert the old way, but if you're super-busy with everything else, it may not be worth it, yet.

* setting up LE in a rush is bad. You'll make some minor error, you won't double-check in 3 months that yes, the renewal happened, and you will find out that your site has been hacked from your customers or potential customers (except that no, it hasn't been hacked)

* whether you buy a 2 year cert ("now I have 2 years to set up LE") or do set up LE, sign up for SSL cert monitoring. You can have something like DownNotifier.com ping you directly in Slack when expiration is coming up.

This is the reason.

It's abstractly difficult to inform a person that their close family member has died, potentially from violent causes, possibly very suddenly.

But come down this hallway, now, to tell this woman that her child is dead; this is what it will be like. You'll need to change your clothes first; you'll need to practice first; and this is what it will do to her, and what it will do to you.

I (obviously) found this very powerful, and while there's some compromise involved in adding in these carefully-selected specifics, it's worth it.

TL;DR... so how did they get it?

Hi Emil, apologies, we're due for another dive into applications. We do try to reply to everyone, but at present we're small enough (and busy enough) that we run through applications in cycles... so there can be a significant delay.

I'll try to review yours tomorrow to at least get you an initial response.

For anyone else applying - if you have a time constraint (like "I think we'd really work well together, but I need to have a job lined up in the next 2 weeks") then you can contact me directly at cto@ (company domain).

I started writing Java with no IDE; and mostly just used * imports; that worked pretty well (and I don't remember it being a headache at all). In IDE land (since, uh, I guess the first I used was called Roaster) automatic imports meant I could always use specific imports, which is a tiny bit better in my mind, but not worth ever doing it manually.

I have no trouble believing this of Facebook; that said, I find it frustrating that he could very easily be seriously misrepresenting what triggered this block, and still be "honest" about this report. More direct quotes from his posting history would help a lot.

Note that Facebook isn't saying they blocked him for that most recent post; more likely that something in that comment triggered a human review of his history, and that review concluded that he should be blocked.

Now he's asking us to evaluate that review (ok, good) and consider the repercussions of Facebook's overagressive filtering on free speech (sure) but this is very hard with only a 2-line summary of what he posts about in his account, and no direct quotes.

I do think this is a likely a completely legit complaint; but it's still very open to the risk that his style of posting was much more noxious than he represents.

(Alt: maybe if he posts too much detail, then the conversation veers into discussing those details rather than the free speech issue, which is more important than his single case).