reminder that the bcrypt hash function ignores input above a certain length! so if you do bcrypt(username || password) for some reason, a sufficiently long username will make it accept any password. to fix this you can sha256 the input first.
The name makes it kind of hard to find, too. I tried searching for it many times in the past using searches like "replay merge conflict resolution", but since git replay is actually a thing that does something else entirely, I didn't find it
Anyone know why git rerere is not enabled by default? I just learned about it recently, and it could have saved me so much time merging new releases into a long-running fork
If you're looking for a way to cross-post on all of the new social networks popping up these days, check out https://t.co/D1jBfcXsqo
* Includes all of the major networks, plus the up-and-coming platforms
* Customize the message per-platform
* Schedule posts
* Lots of analytics
Been playing around with the Arc browser. It's so beautifully designed and has a great UX to "zap" away elements of a site you don't like! Makes browsing twitter/x so much more pleasant 😊 I had it remove so much from the page it can be kinda jumpy when scrolling the timeline tho
@r00k@shl Hmm this is great food for thought.. I’ve been burning a lot of time building subscription flows and getting very little feedback from folks when they don’t renew after trials. I guess I was afraid of missing customers or looking unprofessional not having a self-serve sign up 🤔
I've been switched over for nearly a month now and am quite happy with the move. I just ran out of hobby plan credits and will officially start paying this month. Looking at the costs from last month, I think I'll end up paying about 1/3 the cost of heroku for similar perf
Valentine’s day is coming up, but I’ve never been a fan of the view American culture has of love or the way we “celebrate” it. It gives us all such a narrow definition of love. This describes a better one that we can all aspire to, if we have the courage: https://t.co/q4XDHLDYOG
I use Following almost exclusively since the algorithm change, but it can get annoying when you follow a high-volume account. I still find the For You feed pretty unusable, but maybe the more you use it the better it gets? I'd love to hear your experience.
NEW @ConsumerReports study offers a rare look into the scope of Meta’s surveillance.
It goes way beyond what most may expect—Meta can know many of the websites you visit and even what you’re doing IRL.
https://t.co/yfVQrwtBUT
A quick summary of glaring problems we've found so far:
1) Apple has introduced an anticompetitive new 27% tax on web purchases. Apple has never done this before, and it kills price competition. Developers can't offer digital items more cheaply on the web after paying a third-party payment processor 3-6% and paying this new 27% Apple Tax.
2) Apple dictates all aspects of these links and doesn't allow them in the app's ordinary payment flow. Rather, links must be separated out into a different section of the app, away from places where users actually buy stuff.
3) Apple requires developers to open a generic web browser session, forcing the user to log in to the developer's web site again, to make a purchase. And because of #2, users will have to search all over again for the digital item they wanted to buy.
4) Apple will front-run competing payment processors with their own "scare screen" to disadvantage them.
Epic will contest Apple's bad-faith compliance plan in District Court.