Those who make holocaust tabulation machines belong in prison.
3,643 karma · joined June 2, 2016
Those who make holocaust tabulation machines belong in prison.
--- Ghosting starts here ---
until it capitulates.Or perhaps you can trick it into thinking it's been ghosted for gradually escalating time gaps:
[No message sent in more than 1 week]
[No message sent in more than 1 month]
[No message sent in more than 1 year]
[No message sent in more than 10 years]
[No message sent in more than 100 years]
[No message sent in more than 1000 years]This is exactly what most dark net markets do.
The chance that he was using one the whole damn time? 100%
I'm sorry, but this is the exact same insight that MSN Explorer had. And everyone in retrospect sees that as an absolute spamfest. Ironically, in a very similar way as AI features are seen today.
Now you're getting it
- Probably thousands of large chatrooms, and hundreds of millions of small chatrooms
- Probably hundreds of millions of messages that include a media upload like an image or video, including countless re-posts of random memes
- Overhead from ratchet algorithm cryptography, as well as additional message metadata that is likely in JSON format
- Huge excesses of messages from bridge bots, spam bots, and malfunctioning utility bots. To give a sense of scale... the entirety of Libera.chat (formerly Freenode IRC) used to be bridged to matrix.org, meaning almost every single message from Libera would be copied to matrix.org automatically.
- Everything from other homeservers that federate with matrix.org and have been joined by at least one matrix.org user, including homeservers that no longer exist
- A "Key messages" graphic with 2-4 bullet points about what is going on, what is predicted to happen, and specific dangers to look out for. The tone of the text is carefully adjusted for how life-threatening the situation is. This graphic also includes a copy of the two most important visualizations on the right. (Example: https://www.nhc.noaa.gov/archive/2024/HELENE_graphics.php?pr...)
- A peak storm surge graphic showing predicted coastal inundation and destructive wave action (Example: https://www.nhc.noaa.gov/archive/2024/HELENE_graphics.php?pr...)
- A cone to depict the range of predictions for where the hurricane could go, ideally without a confusing line drawn in the center prediction (Example: https://www.nhc.noaa.gov/archive/2024/HELENE_graphics.php?pr...) Arguably this could be replaced with a spaghetti model map, but these can be just as confusing for those unaware of how predictions are depicted.
- A map of the most likely arrival time for hurricane force winds (Example: https://www.nhc.noaa.gov/archive/2024/HELENE_graphics.php?pr...)
- After the main risks are over, a map of continued flash flood and river flooding risk (Example: https://www.usatoday.com/gcdn/authoring/authoring-images/202...)
- A no-frills ad-free weather report livestreamed to social media, so you can gauge how much the pros at the very top level of hurricane meteorology are freaking out about it (Example: https://www.youtube.com/watch?v=GFL-nbFs2Xs)
- A few other graphics and data dumps primarily intended for meteorologists, local officials, and nerds
And solutions that try to fix this (custom templating engines, runtimes that run the whole thing inside a continuous PHP process) are simply putting lipstick on a pig.
The solution is to use a language that wasn't originally called "Personal HomePage"
2^0 = 1
So the logic might make sense in people's heads if they never encounter 6 or 12 core CPUs that are common these days.
...No. Giving them the loud protest they deserve is the bare minimum