

A cascade of satellite collisions is called Kessler syndrome and the risk of it happening is rapidly increasing due to megaconstellations like Starlink:
Kessler syndrome could be a solution to the Fermi paradox.
cultural reviewer and dabbler in stylistic premonitions


A cascade of satellite collisions is called Kessler syndrome and the risk of it happening is rapidly increasing due to megaconstellations like Starlink:
Kessler syndrome could be a solution to the Fermi paradox.


Weird this article doesn’t mention Hotmail and RocketMail, which both had email client web apps in 1996.


The “girls FTW” mail in that bluesky post is indeed fake, but the daily beast article linked by this post not include that one.


that screenshot is almost[1] definitely fake; unlike the ones in the dailybeast article, phrases from it do not find anything in the search.
i say only almost because there have been some documents removed from previous batches after they were released, but there are no credible reports about the one in your comment ↩︎


This one is fake
i don’t think so?
Its not one of the few occurrences of the word there
which word? i checked a couple and they’re there. eg, here is Musk planning a visit in January 2014.
daily beast is posting misinfo
it is irritating that they only provided a source link for one of the many mails they quote and have screenshots of, but i checked a few of the others and they do come up in the search.


One group- memes or something is wholly controlled by Chinese state actors.
As one of the moderators of !memes@lemmy.ml i encourage OP to look at the sort of posts i make and tell me - do you really think i’m a “Chinese state actor”?
Do you think all these posts i make in, eg, !hoch@lemmy.ml and !goodnews@lemmy.ml and !badnews@lemmy.ml and !eleven@lemmy.ml… these are all part of a carefully-crafted cover, and I’m actually being paid by China to delete totally-not-racist posts depicting their president as a yellow cartoon bear?
And for this service, to maintain my cover, they also pay me to create memes like this and this and this and this and this and this (and defending that one against less informed nerds) and this and this and this (a small sample of my OC here)?
And do you think China paid for this understandable explanation of asymmetric cryptography using high-school level math, because someone asked, deep in a thread about a service which I’d also already debunked the snake-oil privacy claims of?
Really?


good disclaimer. also, they aren’t open source, and from the tech background of the founder who self-funded it i doubt that he plans for it to ever be. in fact, among other cringe things on Issam Hijazi’s linkedin i see that he’s even worked for, enough to become an expert in the proprietary technology of, (checks notes) the very same zionist billionaire (paywall bypass) who just bought TikTok 😢
Also, one their FAQs is “Where does UpScrolled operate its servers and store data? Does it use Big Tech?”… the answer to which includes:
We do rely on some large-scale cloud providers at this stage — not because it’s our ideal, but because building fully independent infrastructure takes time. We’d rather be transparent about that than claim otherwise. Over time, we plan to reduce reliance on these providers and move toward greater independence.
… but We do rely on some is as far as their attempt at transparency took them - they aren’t actually saying which cloud providers they’re using or for what. (given the founder’s expertise i’d guess it’s probably AWS and/or Oracle.)


A few lists of javascript WTFs:
To anyone who thinks they know JS well and that its quirkiness is not a problem, let me know how you do on these quizzes:


no transcoding quality loss
is jellyfin actually transcoding when people don’t want it to?!
otherwise, “no transcoding” doesn’t sound like a feature. transcoding is very useful when you actually need it, eg watching something remotely which is stored at a higher bitrate than your network connection can stream. one way to do it with mpv is ffmpegfs, btw.
(fellow mpv user here; i’ve only used other people’s jellyfin instances… but i’d be very surprised if they’re always unnecessarily transcoding everything they watch.)


nope.





they were just solid colored without symbols
you are describing a tile-based game other than mahjong


the C and fiber layers should be swapped, fragility-wise


I have to ask: what’s with all the obsession with immutable distro?
I guess the promise of having updates JustWork™? I don’t currently use one but I see the appeal.
However FWIW, unlike its namesake ChromeOS, the “Nixbook OS” this post is about is not actually an immutable distro: the instructions are to install NixOS normally and then clone the nixbook repo into /etc/nixbook and run its install.sh. Among other things it installs an update service which runs git pull on that repo as well as running nixos-rebuild boot --upgrade and flatpak update --noninteractive --assumeyes etc.
Cheers to this guy for what he’s doing, but the name is a little confusing. This approach works but it is not nearly as robust as the immutable distro paradigm people infer from name.





i checked their website to see if these are real; disappointingly they are not. they do actually have a “conductor’s coal” scent, though.
The term “web app” hadn’t been coined yet but, even without AJAX I think in retrospect it’s reasonable to call things like the early versions of Hotmail and RocketMail applications - they were functional replacements for a native application, on the web, even though they did require a new page load for every click (or at least every click that required network interaction).
At some point, though, I’m pretty sure that some clicks didn’t require server connections, and those didn’t require another page load (at least if js was enabled): this is what “DHTML” originally meant: using JavaScript to modify the DOM client-side, in the era before sans-page-reload network connections were technically possible.
The term DHTML definitely predates AJAX and the existence of
XMLHTTP(laterXMLHttpRequest), so it’s also odd that this article writes a lot about the former while not mentioning the latter. (The article actually incorrectly defines DHTML as making possible “websites that could refresh interactive data without the need for a page reload” - that was AJAX, not DHTML.)