292 karma · joined January 7, 2010
> Back-end feels so much straightforward.
Well duh! Practice and experience will do that.
However it appears the IAB UID2 README says to only normalize pluses/periods for gmail.com addresses: https://github.com/IABTechLab/uid2docs/blob/main/api/README....
> For example: was Facebook a painkiller? Hardly.
I don’t know. People without pain do take painkillers. And they can have a really hard time stopping. In that sense, I would argue that Facebook is a lot like a painkiller for a lot of people!
I can't find any official data (as usual with eink) but I have heard that an eink pixel's lifetime is around 10 million pixel transitions. Not sure where that number comes from or how accurate it is and how it varies from one display to the next. But if true, you'd get only a couple days with this kind of usage.
Anyone know any more on this?
Edit: I see the ad sidebar now. FYI on my first visit I played for several minutes and this never opened
If simplicity is your main requirement you might find inspiration in this:
> My focus has been on how to adapt the lessons I have learned working in teams at Google to a single programmer building small business work. There are many great engineering practices in Silicon Valley's big companies and well-capitalized VC firms, but one person does not have enough bandwidth to use them all and write software. The exercise for me is: what to keep and what must go.
> If I have been doing it right, the technology and techniques described here will sound easy. I have to fit it all in my head while having enough capacity left over to write software people want. Every extra thing has great cost, especially rarely touched software that comes back to bite in the middle of the night six months later.
https://crawshaw.io/blog/one-process-programming-notes https://news.ycombinator.com/item?id=17701882
I’ll probably get an Apple Watch but I’d prefer something eink and “dumber” with just clock, heartrate, steps, stairs and GPS, no accounts and no forced uploading to their servers would be ideal.
I love the FitBit device though. If there’s some opensource way to keep using it without Google being involved I’ll probably try that.
It sounds like you could press mute, walk away and it could reset unmuting itself in the process without you realizing. You would need to constantly monitor that LED for assurance it is still muted. It’s not clear to me from the article how the SOC is connected to the flipflop reset. i.e. can the flipflop reset be initiated via software?
A mechanical switch that can’t so easily and unexpectedly lose its state would be preferable. There are probably good reasons they didn’t do that (aesthetics, cost, reliability?)
1: https://www.macrumors.com/2020/11/17/apple-silicon-m1-compil...
0: https://godsnotwheregodsnot.blogspot.com/2011/09/weighted-eu...
Wouldn’t the Ring just buffer and send once it rejoined the network?
How long did it take you to build and launch your initial version? How many hours per-week do you spend working on it now?
At first I thought it may have been a second-chance resubmission by a moderator[0], but it has a recent submission id so that's probably not it.
I guess one of the other two points came from someone with a lot of karma, or there's not a lot of new posts right now?
0: https://news.ycombinator.com/item?id=20206120
Edit: And now it's gone entirely from / and /show, but is still on /shownew ...
Your login link now passes through one or more third parties (SMTP servers) which may or may not use TLS, and which may or may not have their certificates validated by each other. So technically a targeted MITM would be possible that would not have been possible with a normal HTTPS password authentication.
Also from a privacy standpoint, your email host and any relays involved now have a detailed record of every time you logged in.