#cursed — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cursed, aggregated by home.social.
-
I was just reminded of Dancer's shell for no apparent reason. What it would do is log you in to any number of machines via ssh simultaneously, give you a new xterm for each session, but give you a SINGLE input line.
So you could run the same interactive shell on dozens of machines at the same time. Useful, for instance, to migrate a machine TO puppet/Ansible/cfengine.
Also one of the most deeply #cursed pieces of software available, and I love it.
-
Please show me that genius so I could slap him right in the face with a spoon full of rotten potatoes.
Really. Idk how much hatred and disgust a designer or a product manager must have for all of the humanity to do so.
-
Please show me that genius so I could slap him right in the face with a spoon full of rotten potatoes.
Really. Idk how much hatred and disgust a designer or a product manager must have for all of the humanity to do so.
-
-
Are these the interesting times that ancient Chinese curse threatened? #cursed #curses #interesting
-
Rocznice i urodziny:
»60 urodziny Polly Walker«19 maja 1966 roku przyszła na świat angielska aktorka telewizyjna i filmowa Polly Walker.
https://www.fahrenheit.net.pl/rocznice-urodziny/60-urodziny-polly-walker/
#Fahrenheit_zin #Bandyta #Bastard #Caprica #ClashoftheTitans #Cursed #Czaspatriotów #Emma #JohnCarter #PatriotGames #PollyWalker #Przeklęta #RobinsonCrusoe #Rome #Rzym #Starcietytanów #WakingtheDead #ŻyweTrupy
-
-
https://www.wacoca.com/videos/3217014/voice-actor/ 【Cursed Companions】久々のタコス屋コラボ！禁止ワードを使うと即4するホラゲ【花江夏樹 / 叶 / 狂蘭メロコ / 如月れん】 #Companions久々のタコス屋コラボ禁止ワードを使うと即4するホラゲ花江夏樹 #cursed #CursedCompanions #Vlog #VoiceActor #にじさんじ #ぶいすぽ #叶 #声優 #如月れん #実況プレイ #狂蘭メロコ #男性声優 #花江夏樹
-
if there was a geneva convention for computers i'd probably be considered a war criminal :neobot_3c:
#slabtop #repurpose #reuse #tech #technology #laptop #usb #mod #modding #cursed
-
if there was a geneva convention for computers i'd probably be considered a war criminal :neobot_3c:
#slabtop #repurpose #reuse #tech #technology #laptop #usb #mod #modding #cursed
-
if there was a geneva convention for computers i'd probably be considered a war criminal :neobot_3c:
#slabtop #repurpose #reuse #tech #technology #laptop #usb #mod #modding #cursed
-
if there was a geneva convention for computers i'd probably be considered a war criminal :neobot_3c:
#slabtop #repurpose #reuse #tech #technology #laptop #usb #mod #modding #cursed
-
if there was a geneva convention for computers i'd probably be considered a war criminal :neobot_3c:
#slabtop #repurpose #reuse #tech #technology #laptop #usb #mod #modding #cursed
-
CW: very cursed LLM stuff
One of the major downsides of vibecoding is that once the code has been written by the AI it is deterministically right or wrong and also cannot be improved (e.g. by switching to a new frontier model) without manually prompting an AI to rewrite it.
Therefore, I have decided to address these issues by developing a new and revolutionary file system:
llmfs!Simply point it to an API, mount it somewhere, and start following "everything is a file"! Even your LLM prompts!
With this amazing new, never-before-seen technology, you can simply include prompts into your C(++) code using the well-known
#includekeyword:#include <string.h> #include <stdio.h> #include <stdlib.h> #include "llm/openai/gpt-oss-20b/prompt/Write a C function called 'void replace(char* text, const char* needle, const char* replacement)' \ that replaces all occurences of needle with replacement. Only include the function and no markdown or explanation." int main() { const char* str = "Hello World!"; char* s = strdup(str); replace(s, "Hello", "Goodbye"); printf("%s\n", s); return 0; }Will your code compile? Maybe.
Will your code work? Who knows!
Will your code have the same behavior every time you compile it? Abso-fucking-lutely not!
Will your code burn through tons and tons of tokens? Abso-fucking-lutely yes, so you can finally hit those CEO-mandated token goals.
Can you see your code? No.
Does the compiler show your code if there are warnings or errors? No, it generates an entirely new version for diagnosis!
Is this real? Yes, it exists and runs on my machine!
Does it actually work? Sometimes!
#AI #LLM #FUSE3 #cursed #I-am-so-sorry-for-creating-this #include #include #include #include #include -
CW: very cursed LLM stuff
One of the major downsides of vibecoding is that once the code has been written by the AI it is deterministically right or wrong and also cannot be improved (e.g. by switching to a new frontier model) without manually prompting an AI to rewrite it.
Therefore, I have decided to address these issues by developing a new and revolutionary file system:
llmfs!Simply point it to an API, mount it somewhere, and start following "everything is a file"! Even your LLM prompts!
With this amazing new, never-before-seen technology, you can simply include prompts into your C(++) code using the well-known
#includekeyword:#include <string.h> #include <stdio.h> #include <stdlib.h> #include "llm/openai/gpt-oss-20b/prompt/Write a C function called 'void replace(char* text, const char* needle, const char* replacement)' \ that replaces all occurences of needle with replacement. Only include the function and no markdown or explanation." int main() { const char* str = "Hello World!"; char* s = strdup(str); replace(s, "Hello", "Goodbye"); printf("%s\n", s); return 0; }Will your code compile? Maybe.
Will your code work? Who knows!
Will your code have the same behavior every time you compile it? Abso-fucking-lutely not!
Will your code burn through tons and tons of tokens? Abso-fucking-lutely yes, so you can finally hit those CEO-mandated token goals.
Can you see your code? No.
Does the compiler show your code if there are warnings or errors? No, it generates an entirely new version for diagnosis!
Is this real? Yes, it exists and runs on my machine!
Does it actually work? Sometimes!
#AI #LLM #FUSE3 #cursed #I-am-so-sorry-for-creating-this #include #include #include #include #include -
CW: very cursed LLM stuff
One of the major downsides of vibecoding is that once the code has been written by the AI it is deterministically right or wrong and also cannot be improved (e.g. by switching to a new frontier model) without manually prompting an AI to rewrite it.
Therefore, I have decided to address these issues by developing a new and revolutionary file system:
llmfs!Simply point it to an API, mount it somewhere, and start following "everything is a file"! Even your LLM prompts!
With this amazing new, never-before-seen technology, you can simply include prompts into your C(++) code using the well-known
#includekeyword:#include <string.h> #include <stdio.h> #include <stdlib.h> #include "llm/openai/gpt-oss-20b/prompt/Write a C function called 'void replace(char* text, const char* needle, const char* replacement)' \ that replaces all occurences of needle with replacement. Only include the function and no markdown or explanation." int main() { const char* str = "Hello World!"; char* s = strdup(str); replace(s, "Hello", "Goodbye"); printf("%s\n", s); return 0; }Will your code compile? Maybe.
Will your code work? Who knows!
Will your code have the same behavior every time you compile it? Abso-fucking-lutely not!
Will your code burn through tons and tons of tokens? Abso-fucking-lutely yes, so you can finally hit those CEO-mandated token goals.
Can you see your code? No.
Does the compiler show your code if there are warnings or errors? No, it generates an entirely new version for diagnosis!
Is this real? Yes, it exists and runs on my machine!
Does it actually work? Sometimes!
#AI #LLM #FUSE3 #cursed #I-am-so-sorry-for-creating-this #include #include #include #include #include -
CW: very cursed LLM stuff
One of the major downsides of vibecoding is that once the code has been written by the AI it is deterministically right or wrong and also cannot be improved (e.g. by switching to a new frontier model) without manually prompting an AI to rewrite it.
Therefore, I have decided to address these issues by developing a new and revolutionary file system:
llmfs!Simply point it to an API, mount it somewhere, and start following "everything is a file"! Even your LLM prompts!
With this amazing new, never-before-seen technology, you can simply include prompts into your C(++) code using the well-known
#includekeyword:#include <string.h> #include <stdio.h> #include <stdlib.h> #include "llm/openai/gpt-oss-20b/prompt/Write a C function called 'void replace(char* text, const char* needle, const char* replacement)' \ that replaces all occurences of needle with replacement. Only include the function and no markdown or explanation." int main() { const char* str = "Hello World!"; char* s = strdup(str); replace(s, "Hello", "Goodbye"); printf("%s\n", s); return 0; }Will your code compile? Maybe.
Will your code work? Who knows!
Will your code have the same behavior every time you compile it? Abso-fucking-lutely not!
Will your code burn through tons and tons of tokens? Abso-fucking-lutely yes, so you can finally hit those CEO-mandated token goals.
Can you see your code? No.
Does the compiler show your code if there are warnings or errors? No, it generates an entirely new version for diagnosis!
Is this real? Yes, it exists and runs on my machine!
Does it actually work? Sometimes!
#AI #LLM #FUSE3 #cursed #I-am-so-sorry-for-creating-this #include #include #include #include #include -
CW: very cursed LLM stuff
One of the major downsides of vibecoding is that once the code has been written by the AI it is deterministically right or wrong and also cannot be improved (e.g. by switching to a new frontier model) without manually prompting an AI to rewrite it.
Therefore, I have decided to address these issues by developing a new and revolutionary file system:
llmfs!Simply point it to an API, mount it somewhere, and start following "everything is a file"! Even your LLM prompts!
With this amazing new, never-before-seen technology, you can simply include prompts into your C(++) code using the well-known
#includekeyword:#include <string.h> #include <stdio.h> #include <stdlib.h> #include "llm/openai/gpt-oss-20b/prompt/Write a C function called 'void replace(char* text, const char* needle, const char* replacement)' \ that replaces all occurences of needle with replacement. Only include the function and no markdown or explanation." int main() { const char* str = "Hello World!"; char* s = strdup(str); replace(s, "Hello", "Goodbye"); printf("%s\n", s); return 0; }Will your code compile? Maybe.
Will your code work? Who knows!
Will your code have the same behavior every time you compile it? Abso-fucking-lutely not!
Will your code burn through tons and tons of tokens? Abso-fucking-lutely yes, so you can finally hit those CEO-mandated token goals.
Can you see your code? No.
Does the compiler show your code if there are warnings or errors? No, it generates an entirely new version for diagnosis!
Is this real? Yes, it exists and runs on my machine!
Does it actually work? Sometimes!
#AI #LLM #FUSE3 #cursed #I-am-so-sorry-for-creating-this #include #include #include #include #include -
-
Movie TV Tech Geeks #TV #Netflix #Between #Cursed 8 Ambitious Netflix Shows Nobody Remembers http://dlvr.it/TS97YL
-
We have a cursed toilet door lock in the office.
It works fine for most people but if you try to use your left hand it jams solid almost every time you try to operate it. As I'm the only left handed person here it drives me insane!
-
We have a cursed toilet door lock in the office.
It works fine for most people but if you try to use your left hand it jams solid almost every time you try to operate it. As I'm the only left handed person here it drives me insane!
-
We have a cursed toilet door lock in the office.
It works fine for most people but if you try to use your left hand it jams solid almost every time you try to operate it. As I'm the only left handed person here it drives me insane!
-
We have a cursed toilet door lock in the office.
It works fine for most people but if you try to use your left hand it jams solid almost every time you try to operate it. As I'm the only left handed person here it drives me insane!
-
We have a cursed toilet door lock in the office.
It works fine for most people but if you try to use your left hand it jams solid almost every time you try to operate it. As I'm the only left handed person here it drives me insane!
-
🤔 so I tried synθesizing ðe Vowel Cuboid^tm for a parallel universe where ðe 3rd formant makes as many distinctions as ðe first 2 😳
#cursed #linguistics #sounddesign #worldbuilding #conlang #surreal
-
they think they found the issue.
here is their reply:
"The Problem: In many Qualcomm-based (QCA) drivers, the Multicast Snooping (MCS) module is programmed to ignore "well-known" or "permanent" multicast addresses (reserved by IANA) for snooping purposes. It floods them to all ports to ensure compatibility with network protocols that rely on these addresses. Like the one that you are choosing here is just the permanent multicast address "ff05::1234".
The Consequence: Because the system doesn't "snoop" these addresses, it never learns which specific client wants the traffic. Without this "MDB" entry, the Access Point cannot perform Multicast-to-Unicast (M2U) conversion, which is essential for stable video/data streaming over Wi-Fi.
The Solution: Moving to the ff3x::/16 range (often used for SSM - Source-Specific Multicast) or other non-permanent ranges allows the MCS to intercept the join requests and create the necessary entries for optimization."
I then tried ff35::1234 and it did not work #IPv6 #multicast #cursed
-
they think they found the issue.
here is their reply:
"The Problem: In many Qualcomm-based (QCA) drivers, the Multicast Snooping (MCS) module is programmed to ignore "well-known" or "permanent" multicast addresses (reserved by IANA) for snooping purposes. It floods them to all ports to ensure compatibility with network protocols that rely on these addresses. Like the one that you are choosing here is just the permanent multicast address "ff05::1234".
The Consequence: Because the system doesn't "snoop" these addresses, it never learns which specific client wants the traffic. Without this "MDB" entry, the Access Point cannot perform Multicast-to-Unicast (M2U) conversion, which is essential for stable video/data streaming over Wi-Fi.
The Solution: Moving to the ff3x::/16 range (often used for SSM - Source-Specific Multicast) or other non-permanent ranges allows the MCS to intercept the join requests and create the necessary entries for optimization."
I then tried ff35::1234 and it did not work #IPv6 #multicast #cursed
-
they think they found the issue.
here is their reply:
"The Problem: In many Qualcomm-based (QCA) drivers, the Multicast Snooping (MCS) module is programmed to ignore "well-known" or "permanent" multicast addresses (reserved by IANA) for snooping purposes. It floods them to all ports to ensure compatibility with network protocols that rely on these addresses. Like the one that you are choosing here is just the permanent multicast address "ff05::1234".
The Consequence: Because the system doesn't "snoop" these addresses, it never learns which specific client wants the traffic. Without this "MDB" entry, the Access Point cannot perform Multicast-to-Unicast (M2U) conversion, which is essential for stable video/data streaming over Wi-Fi.
The Solution: Moving to the ff3x::/16 range (often used for SSM - Source-Specific Multicast) or other non-permanent ranges allows the MCS to intercept the join requests and create the necessary entries for optimization."
I then tried ff35::1234 and it did not work #IPv6 #multicast #cursed
-
they think they found the issue.
here is their reply:
"The Problem: In many Qualcomm-based (QCA) drivers, the Multicast Snooping (MCS) module is programmed to ignore "well-known" or "permanent" multicast addresses (reserved by IANA) for snooping purposes. It floods them to all ports to ensure compatibility with network protocols that rely on these addresses. Like the one that you are choosing here is just the permanent multicast address "ff05::1234".
The Consequence: Because the system doesn't "snoop" these addresses, it never learns which specific client wants the traffic. Without this "MDB" entry, the Access Point cannot perform Multicast-to-Unicast (M2U) conversion, which is essential for stable video/data streaming over Wi-Fi.
The Solution: Moving to the ff3x::/16 range (often used for SSM - Source-Specific Multicast) or other non-permanent ranges allows the MCS to intercept the join requests and create the necessary entries for optimization."
I then tried ff35::1234 and it did not work #IPv6 #multicast #cursed
-
-
@NanoRaptor want to make it cursed?
Change each touchbar to a display-bar with a sliding marker.
Then you have to slide all of the markers to a "other" location except in the display-bar you are using (eg, you want Q, then that bar's slider points to Q and all the others point to "other") - and then add one big plate to the right of the mouse-pad with a "commit" printed on it.
back to basics!
-
I must say, though,
Seeing Amazon in the header credits of a movie is freaking #CURSED.
-
Cursed Available March 24
#horror – #horrormovies – #Cursed – #LeomarkStudios – @LeomarkStudios – Six lives spiral into unspeakable nightmares, all linked by a cursed doll, Molly. Haunted orphanages, ancient evils, brutal invasions, and flesh-hungry monstrosities converge as Molly’s sinister presence weaves their doom. No one escapes her curse only darkness and death remain. STARRING: Daniela Casas, Davi
https://horrornerdonline.com/2026/03/cursed-available-march-24/
-
So Matt (AKA @Woodmachinist )'s next video for his Traditional Tool Chest build series has been posted, and honestly...I think this series might be cursed. Just watch for yourselves, and you'll see what I mean.
Also: Shout-out to his editor for trying her damnedest to make this work.
#Woodworking #Carpentry #ToolChest #TheAnarchistsToolChest #LostArtPress #Haunted #Maybe #Cursed #AlsoMaybe
-
CW: oh god please no, http, brainfuck, plan9
Webserver in Brainfuck: a simple shell script sets up a listening tcp connection and then starts the bf program with standard input and standard output both pointing to the `data` file.
-
CW: 🔞 mind control, cursed, references AI but not AI generated
good news! someone wants to drain your brain and have your mind under his total control.
bad news. it's Sam Altman :(
#MindControl #BrainDrain #cursed #OpenAI #SamAltman #AI #ChatGPT #kink #nsfw
-
Players when you give them an obviously cursed item be like:
-
Players when you give them an obviously cursed item be like:
-
☢️ 30▶️10hz + 20khz + 22khz + 17▶️22khz ☢️
at over 100% volume- 🤨 except apparently mastodon compresses wavs which breaks ðe effect so here's a recording of ðat instead & just trust me bro ðis sound is actually entirely made from inaudible frequencies 🌿 -
🤔🫥 2→ 1s (using ðe same 6 color channels)🤔🤔🤔
-
🤔🫥 2→ 1s (using ðe same 6 color channels)🤔🤔🤔
-
🤔🫥 2→ 1s (using ðe same 6 color channels)🤔🤔🤔
-
🤔🫥 2→ 1s (using ðe same 6 color channels)🤔🤔🤔
-
@GayDeceiver @Binder my brain is singing this and it sound so weird going between the 2 sings #cursed!
-
All magic swords are cursed.
A powerful mage gave the sword special abilities to make it better at killing people.
Cursed!
-
Does it count as doing the Apollo meme if the EPP are the most predictable [redacted] in Europe?
#ApolloTag #ChancellorLizzieGrant #SexyBateman #HeTellsMeToShutUpIGOTThis #IShouldHaveTakenTheInitialAdvice #CURSED
-
Does it count as doing the Apollo meme if the EPP are the most predictable [redacted] in Europe?
#ApolloTag #ChancellorLizzieGrant #SexyBateman #HeTellsMeToShutUpIGOTThis #IShouldHaveTakenTheInitialAdvice #CURSED
