Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
medmunds
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
medmunds
8y ago
Oh interesting. Their two hypotheses (which they will test) are that Send "can drive Firefox Accounts beyond the Firefox Browser" and that it will "will provide a valuable platform to research, communicate with, and market to
62.
▲
Ridding Gmail of 100M more spam messages with TensorFlow
(cloud.google.com)
2 points
by
medmunds
8y ago
|
0 comments
63.
▲
Munchery, Sprig: What went wrong with on-demand, artisanal food
(sfchronicle.com)
1 points
by
medmunds
8y ago
|
0 comments
64.
▲
by
medmunds
8y ago
> recommend Wikivoyage over Wikitravel Seconded. Wikivoyage was a fork of Wikitrsvel. The history is... interesting: https://en.m.wikipedia.org/wiki/Internet_Brands#Wikitravel_a...
65.
▲
by
medmunds
8y ago
[video]
66.
▲
by
medmunds
8y ago
> email tracking links ... domains have nothing in common with the destination URL The tradeoff has been CNAME-ing your own subdomain to your Email Service Provider’s tracking domain, which gets you a recognizable(-ish) URL, but has hist
67.
▲
by
medmunds
8y ago
I’ve been very happy with the Monoprice “SonicSolace” ones. Haven’t done a side-by-side comparison, but I’ve found them perfectly good for airplane use, and they’re definitely cheaper. https://www.monoprice.com/product?p_id=
68.
▲
by
medmunds
8y ago
Ouch indeed. I have a RainMachine irrigation controller that hooks into WU forecasts to be smart about when to water. It can use other data sources (e.g., NOAA), but in our microclimate area, WU’s access to highly-localized personal weather
69.
▲
by
medmunds
8y ago
> support multiple transaction mail providers One potential pitfall is keeping your blocked-email list synced between ESPs. You definitely don't want to repeatedly send to an address that has bounced or reported your email as spam,
70.
▲
by
medmunds
8y ago
Not the OP, but my personal experience has been that it was a mistake to rely on SendGrid. This is based on a 2016 incident [1] where SendGrid made unannounced changes to IP pools, resulting in sent emails being delayed for several hours or
71.
▲
by
medmunds
8y ago
I moved my side project from Mandrill to SendGrid immmediately after the “absorbtion” (Mandrill/MailChimp policy changes). But then I had to scramble to move again after an incident where SendGrid apparently felt it was OK to delay sen
72.
▲
by
medmunds
8y ago
> show slightly different versions of the show to different viewers The 1985 movie Clue was released with three different endings[1]. And if you really wanted to see them all, you had to go to the movie at least three times in differen
73.
▲
SF Homeless Project
(projects.sfchronicle.com)
3 points
by
medmunds
8y ago
|
0 comments
74.
▲
by
medmunds
8y ago
In SF, at least, Sonic has started stringing their own fiber. But it’s not in every neighborhood yet, and even in places where they are installing fiber, some streets may be left dark, (Including, frustratingly, a big swath of Portrero Hill
75.
▲
by
medmunds
9y ago
I’d been in the exact same not-worth-the-hassle-to-change-for-only-$9.95 mindset on one of my side projects. That is, until last year when Comodo engaged in some really shady behavior directed at Let’s Encrypt [1]. At that point, decided th
76.
▲
Building Interactive Visualizations with React, D3, and TypeScript
(blog.lucify.com)
1 points
by
medmunds
9y ago
|
0 comments
77.
▲
by
medmunds
9y ago
The SF elections website allows you to confirm that your ballot was counted. But not how you voted.
78.
▲
by
medmunds
9y ago
I can confirm exactly this. I started with a root catchall on my personal .com (~15 years ago), and it was quickly overwhelmed with dictionary spam. Switched to a subdomain catchall, and haven't seen a dictionary run since. Picking a s
79.
▲
by
medmunds
9y ago
"The malware spread via SMB... used by Windows machines to communicate with file systems over a network. An infected machine would then propagate the infection to other at-risk boxes [that have] not received the critical MS-17-010 secu
80.
▲
by
medmunds
9y ago
You might check into the https://en.m.wikipedia.org/wiki/Open_Financial_Exchange format. Software like Quicken is able to download transactions from several banks and brokerages using it. (I don't know what's
81.
▲
by
medmunds
9y ago
> you should not be mixing transactional email with work email Can't emphasize that enough. Django makes it easy to substitute email backends [1], and there are backends available for most transactional ESPs. I maintain one that cov
82.
▲
The science behind why your shoelace knot is doomed to fail
(pbs.org)
1 points
by
medmunds
10y ago
|
0 comments
83.
▲
by
medmunds
10y ago
This is sourced from https://www.thesslstore.com/blog/lets-encrypt-phishing/ , which comes from a division of "the world’s leading SSL/TLS reseller" ( https://www.thesslstore.com/blog&
84.
▲
by
medmunds
10y ago
Automattic has released their policies under a Creative Commons license: https://github.com/Automattic/legalmattic
85.
▲
by
medmunds
10y ago
Oh, also, another resource if you want to roll your own email verification: https://www.scottbrady91.com/Email-Verification/Python-Email...
86.
▲
by
medmunds
10y ago
There are a handful of (commercial) email address verification services, which could automate some of the logic for you: * https://kickbox.io * https://www.emailhippo.com * http://www.briteverify.com Th
87.
▲
DreamHost Domain Privacy Update
(dreamhost.com)
1 points
by
medmunds
10y ago
|
0 comments
88.
▲
by
medmunds
10y ago
I'm certain you're right, and I'm here to learn. Genuinely curious about the risks to upgrading password algorithms by wrapping the old hashes. (Because at least one major framework seems to suggest this approach.) Is this an
89.
▲
by
medmunds
10y ago
If your db has already been breached, it's too late to upgrade security on those hashes, true. But if you're trying to proactively strengthen your password hashes to make them more resistant in case of a future breach, this lets y
90.
▲
by
medmunds
10y ago
Sorry, I was trying to point out that you can have it both ways. As pixelcort suggested, do a one-time upgrade of all (weak) hashes to newScheme(oldScheme(password). But then as users login, you can upgrade them to just newScheme(password).
More ›