I don't think they specifically target people who tend to go to sleep. But, having worked in the ad engineering, I can imagine they do know how often specific users skip ads and target ads based on that property.
One can also use the Facebook website. It's almost usable on the Firefox mobile to the extent that you can check the news feed or notifications and reply to a comment, but anything more involved is very annoying (so you end up not doing this and long-term using Facebook less, which is a good thing)
LLM would help with this immensely, if only it was allowed (not sure how though... make the ruleset available as a single text field for export/import, maybe?)
Having clocks synchronized between your servers is extremely useful. For example, having a guarantee that the timestamp of arrival of a packet (measured by the clock on the destination) is ALWAYS bigger than the timestamp recorded by the sender is a huge win, especially for things like database scaling.
For this though you need to go beyond NTP into PTP which is still usually based on GPS time and atomic clocks
Actually interesting to think about what UTC actually means and there is seems to be no absolute source of truth [0]. I guess the worry is not that much about the NTP servers (for which people anyways should configure fail overs) but the clocks themselves.
Could you define an absolute source of truth based on extrinsic features. Something like taking an intrinsic time from atomic sources, pegged to an astronomic or celestial event; then a predicted astronomic event that would allow us to reconcile time in the future.
It might be difficult to generate enough resolution in measurable events that we can predict accurately enough? Like, I'm guessing the start of a transit or alignment event? Maybe something like predicting the time at which a laser pulse will be returnable from a lunar reflector -- if we can do the prediction accurately enough then we can re-establish time back to the current fixed scale.
I think I'm addressing an event that won't ever happen (all precise and accurate time sources are lost/perturbed), and if it does it won't be important to re-sync in this way. But you know...
Getting from 95% compatible to 100% compatible may not only take a lot of time, but also result in worsening the performance. Sometimes it's good to drop some off the less frequently used features in order to make the tool better (or allow for making the tool better)
> I'm more curious how/why the author ended up with a $500 gift card. That's a large amount, and the author never shares how this was obtained, which seems like a key missing detail. Did the author buy the gift card for himself (why?) or did someone give him a very large gift (why not mention that?)
The author mentions a big store (names it similar to Walmart for US based readers).
I would assume this was an accepted form of "return a product without a receipt" or "we want to accept your complain about this product we sold going crazy 1 day after it's warranty but we cannot give you cash back" etc
I don't understand. Gift cards typically cannot be returned, at least in the US. And the author said the gift card was redeemed "to pay for my 6TB iCloud+ storage plan", which also cannot be returned I'd imagine.
But gift cards aren't supposed to work that, right? If it wasn't "legal" or "okay" to have a 500 dollar card, they shouldn't be sold. They are available, therefore they should be perfectly usable.
I don't want to speculate more, but one of the use cases for them is for people that choose to not use cards online (or even don't have credit cards at all) to be able to buy digital goods with cash.
Either way, if we're questioning buying/using the gift card, we're blaming the victim
I'm not blaming anyone; I just find it surprising that this detail wasn't mentioned or explained. Its omission makes the article less trustworthy to me.
People are fast to pull out pitchforks in response to outrage-bait posts like this, but (generally speaking) a nontrivial percentage of such posts are intentionally omitting details which can help explain the other side's actions.
Also I genuinely wasn't familiar with this specific use-case for gift cards. At least in the US, you can buy general-purpose prepaid debit cards for this type of thing instead, or use various services which generate virtual cards e.g. privacy.com. To me that seems infinitely more normal than buying a large-value "gift card" for yourself, but I'm admittedly not familiar with the options in other countries.
1. The prepaid Visa or Mastercard come with an extra fee (like 5-6 dollars per card if I recall correctly?)
2. I didn't see the prepaid cards in stores outside the US, so they are probably not that popular outside.
Sometimes you also want to shift your spending, like if you spend 500 USD this month at this store, you'll get some good % cashback. So you end up buying a gift card that you know you'll definitely use next month.
privacy.com even if it was available in some country just means you give transactions of your identity to some other company. Cash (and so gift cards if they don't accept cash) is the most private way.
The file operations on macOS are rather slow too. I needed to invest in some rsync-based syncing for an in-docker application build as accessing the mounted volume from a Docker container was around 20 times slower than on Linux :O
That’s another issue. The access from macOS/windows to the Linux filesystem (docker volume) is over the loopback network. Also the other way around docker bind mounts to windows/macos filesystem.
reply