Accurate. Are you a summarization bot?
dparticiple
joined 1 year ago
Perhaps it's time to bring back the amenity that Singapore Airlines devised to handle this situation on their ultra-long-haul flights in the Airbus 340-500 -- the corpse cupboard: https://simpleflying.com/singapore-airlines-airbus-a340-500-corpse-cupboards-history/
Thank you for saving me a click. Undersea data center operation and seawater cooling is not new; Microsoft has been pursuing such efforts for a decade or so now, under the auspices of Project Natick: https://natick.research.microsoft.com/
Kagi user chiming in here. Have been incredibly happy with the service in terms of search quality and overall usefulness since subscribing. Feels like Google in the early, early days (I was there) before they lost their soul. Their changelog page is instructive; -- https://kagi.com/changelog
There is also a reputed new cat-to/from-human transmission vector for H5N1, which was briefly noted in a CDC report last week before being redacted: https://www.nytimes.com/2025/02/06/health/cdc-bird-flu-cats-people.html . NYT article may be paywalled, but details can be found in other media sources as well.
Hi HellsBelle,
Firstly, sorry for my overly snarky response. I know that the "don't change the headline" rule was strictly enforced in many subreddits, but I wasn't aware that this applied here as well. Is this a rule for this particular community or the entire Lemmy instance it's on? Would you be kind enough to share a pointer to the rule list?
You don't have to repeat the clickbait headline. Write your own!
Ah, very likely. I'm a literalist at heart, which is often at odds with posts of this nature. Thank you.
The screenshot shown references nothing about a payment plan or a 69% APR. What am I missing?
Thank you, Slatlun. It's a pet peeve of mine. I read somewhere that not rewriting article headlines is a holdover from some subreddits who prohibited the practice.
view more: next ›
Thank you! Even if this is harmless, the handling doesn't seem to be very elegant, so I'll have a go at filing a bug report. I've changed the notification type to "persistent" for messages going forward, so if this happens again I'll be able to capture the phone number of the message.