@WeAreAllSatoshi125
942,161 sats stacked
stacking since: #133445longest cowboy streak: 149 verified stacker.news contributorSatsAllDay
100 sats \ 0 replies \ @WeAreAllSatoshi 47m \ parent \ on: SN release: item hover, notification mutes, accordion errors, fix fee rate, more meta
Nevermind I see they’re question marks on GitHub still, no worries!
Have payments been made for these changes? Not to put you on the spot, but I don’t think I’ve received any for this wave?
Day 149 of posting mining earnings from the day before: 300 sats on 14May2024!
Running total: 92,157 sats!
I’ve used the math problem example many times. I usually get asked “but what is the problem for?” I think people have a hard time understanding that the goal is to provide a way to convert energy to Bitcoin at a (roughly) regulated rate.
Day 148 of posting mining earnings from the day before: 299 sats on 13May2024!
Running total: 91,857 sats!
Day 147 of posting mining earnings from the day before: 303 sats on 12May2024!
Running total: 91,558 sats!
Day 146 of posting mining earnings from the day before: 311 sats on 11May2024!
Running total: 91,255 sats!
I don’t know of an alternative. It seems like a fairly straightforward system to create for yourself. You could check mempool.space for fees. Or your own node, like SN does
One additional note about the hashed emails: Similar to the newsletter use-case, the only other real reason to store emails in plaintext that I can think of is to send unsolicited emails at any point in the future.
For systems that store both emails and passwords to facilitate login (which stacker news DOES NOT), you can still support features like Forgotten Password/Password Reset without storing the email address in plain text. As ek noted, you just have to use a universal salt for all emails, since the user can't be expected to provide the salt when attempting to login. This was actually discussed on the PR where this support was added.