Can you copy or screenshot one? Amazon requires login to sort through reviews for some people.
The reviews are on the Scotch site itself, not on Amazon: https://www.scotchbrand.com/3M/en_US/p/d/cbgnhw011057/
Readit NewsDead Comment
jperras commented on A pair of scissors on formica table suddenly bursts into flames old.reddit.com/r/chemistr... · Posted by u/83457
jperras commented on A pair of scissors on formica table suddenly bursts into flames old.reddit.com/r/chemistr... · Posted by u/83457
I find no mention of melting in the reviews. Are you joking?
Sorry, the reviews are actually on the Scotch site itself: https://www.scotchbrand.com/3M/en_US/p/d/cbgnhw011057/
jperras commented on A pair of scissors on formica table suddenly bursts into flames old.reddit.com/r/chemistr... · Posted by u/83457
Those scissors apparently have a habit of the handle melting away (see reviews): https://www.amazon.com/dp/B00SSVNNZC
As one comment pointed out, they could be using nitrocellulose in the handle.
jperras commented on Show HN: I am Building a Producthunt alternative huntlie.com... · Posted by u/heyarviind2
Don't use the term "hunt" in the name, to me it just screams "dupe" instead of something unique. Go the route of improving what PH has and adding things that are missing.
Some ideas: - Users should be able to update their post to some extent.
- There's no "product page" in your app, build something where I can see people commenting, reacting, and maybe even sharing their own screenshots of it because that's something PH does pretty well but can be improved.
- "LAUNCHES WORTH YOUR SCROLL" sounds kinda cringe, change to something like "Find the next best thing" or make it random on load and have a few less in your face versions of it. Reddit has "homepage of the internet" which seems appropriate. You can have "have you launched yet?", "find the next best thing", "what's trending today"...etc
I have more ideas, feel free to message me or drop a way to contact you if you'd like more feedback :)
> Don't use the term "hunt" in the name, to me it just screams "dupe" instead of something unique.
> [...]
> You can have "have you launched yet?", "find the next best thing", "what's trending today"...etc
OP: I may or may not be in possession of hasitlaunched dot com, should you be interested in purchasing it…
My view is that you basically never want exponential backoff.
The only time exponential backoff is useful is if the failure is due to a rate limit and you specifically need a mechanism to reduce the rate at which you are attempting to use it.
In the common case that the thing you're trying to talk is just down, exponential backoff with base N (e.g. wait 2x longer each time) increases your expected downtime by a factor of N (e.g. 2), because by the time your dependency is working again, you may be waiting up to the same amount of time again before you even retry it! Meanwhile, your service is down and your customers can't use it and your program is doing nothing but sleeping for another 30 minutes before it even checks to see if it can work.
And for what? What is the downside to you if your program retries much more frequently?
I much prefer setting a fixed time period to wait between retries (would you call that linear backoff? no backoff?), so for example if the thing fails you just sleep 1 second and try again, forever. And then your service is working again within 1 second of your dependency coming back up.
If you really must use exponential backoff then pick a quite-low upper bound on how long you'll wait between retries. It is extremely frustrating to find out that something wasn't working just because it was sleeping for a long time because the previous handful of attempts failed.
> The only time exponential backoff is useful is if the failure is due to a rate limit and you specifically need a mechanism to reduce the rate at which you are attempting to use it.
That's what you should be using exponential backoff for. In actuality, the new latency introduced by the backoff should be maintained for some time even after a successful request has been received, and gradually over time the interval reduced.
> I much prefer setting a fixed time period to wait between retries (would you call that linear backoff? no backoff?)
I've heard it referred to as truncated exponential backoff.
In the seven years I've been on HN, it has gone through different phases, each with a noticeable change in the quality of the comments.
One big shift came at the beginning of COVID, when everyone went work-from home. Another came when Elon Musk bought X. There have been one or two other events I've noticed, but those are the ones I can recall now. For a short while, many of the comments were from low-grade Russian and Chinese trolls, but almost all of those are long gone. I don't know if it was a technical change at HN, or a strategy change externally.
I don't know if it's internal or external or just fed by internet trends, but while it is resistant, HN is certainly not immune from the ills affecting the rest of the internet.
16 year HN vet here.
This place has both changed a _lot_ and also very little, depending on which axis you want to analyze. One thing that has been pretty consistent, however, is the rather minimal amount of trolls/bots. There are some surges from time to time, but they really don't last that long.
jperras commented on Japan was the future but it's stuck in the past (2023) bbc.com/news/world-asia-6... · Posted by u/amichail
I mostly agree. Still, being a minority from Montreal who left and found life in Japan significantly less alienating, I hesitate to agree wholeheartedly.
Very fair. The line between conscientious preservation and alienation can be (and often is) an easy one to cross.
jperras commented on Japan was the future but it's stuck in the past (2023) bbc.com/news/world-asia-6... · Posted by u/amichail
Came to say the same thing. The supposed backwards parts are seeming charming the longer I live in Canada.
Having a sovereign language has allowed it to avoid so much brainrot in our culture today.
Québecois here. We've been trying to tell the rest of Canada this for _decades_.
“Epoch timestamps are timezone-naive”
Er, not really. Not meaningfully. They can be freely compared with timezone-aware timestamps. They cannot be freely compared with time zone-naive timestamps.
“Timezone naive” is a distinction that applies to datetime objects. It just doesn’t apply to epoch time. The problem with naive timestamps is that you have to somehow remember what the correct time zone is. You don’t have to remember that for epoch time.
The reason you want timezone-aware datetime objects is because you can safely and unambiguously convert them to, say, epoch time.
> Er, not really. Not meaningfully. They can be freely compared with timezone-aware timestamps
Author here. My original post was a little ambiguous on this topic; I've updated it to make it clearer.
The tl;dr is that in Python, `time.time()` calls the c stdlib `time` function (at least in CPython), which follows the POSIX standard. It turns out that POSIX standard does _not_ mention timezones at all: https://pubs.opengroup.org/onlinepubs/9699919799/functions/t...
To wit, you can't actually assume that timestamps are UTC in Python, which is a different kind of insanity:
``` datetime.datetime.utcnow().replace(tzinfo=pytz.timezone("America/Toronto")).timestamp() ```
differs materially from
``` datetime.datetime.utcnow().timestamp() ```