#techhell — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #techhell, aggregated by home.social.
-
Erin Brockovich, the environmental activist whose name and work you may recognize from the Oscar-winning movie Erin Brockovich, has created a tool to map data centers across the country, along with a form for people to report data centers and their impacts in their community
#FuckAI #FuckDataCenters #DataCenter #ErinBrockovich #uspol #TechHell #AI
-
Erin Brockovich, the environmental activist whose name and work you may recognize from the Oscar-winning movie Erin Brockovich, has created a tool to map data centers across the country, along with a form for people to report data centers and their impacts in their community
#FuckAI #FuckDataCenters #DataCenter #ErinBrockovich #uspol #TechHell #AI
-
Erin Brockovich, the environmental activist whose name and work you may recognize from the Oscar-winning movie Erin Brockovich, has created a tool to map data centers across the country, along with a form for people to report data centers and their impacts in their community
#FuckAI #FuckDataCenters #DataCenter #ErinBrockovich #uspol #TechHell #AI
-
Erin Brockovich, the environmental activist whose name and work you may recognize from the Oscar-winning movie Erin Brockovich, has created a tool to map data centers across the country, along with a form for people to report data centers and their impacts in their community
#FuckAI #FuckDataCenters #DataCenter #ErinBrockovich #uspol #TechHell #AI
-
Erin Brockovich, the environmental activist whose name and work you may recognize from the Oscar-winning movie Erin Brockovich, has created a tool to map data centers across the country, along with a form for people to report data centers and their impacts in their community
#FuckAI #FuckDataCenters #DataCenter #ErinBrockovich #uspol #TechHell #AI
-
AI software that can create digital clones of employees unveiled at CES 2026
#TechHell #FuckAI #workersRights #caminoAlaDistopia #distopia #AIethos
-
AI software that can create digital clones of employees unveiled at CES 2026
#TechHell #FuckAI #workersRights #caminoAlaDistopia #distopia #AIethos
-
AI software that can create digital clones of employees unveiled at CES 2026
#TechHell #FuckAI #workersRights #caminoAlaDistopia #distopia #AIethos
-
AI software that can create digital clones of employees unveiled at CES 2026
#TechHell #FuckAI #workersRights #caminoAlaDistopia #distopia #AIethos
-
AI software that can create digital clones of employees unveiled at CES 2026
#TechHell #FuckAI #workersRights #caminoAlaDistopia #distopia #AIethos
-
It's either the CPU or the socket that has short circuited. Joy of fucking joys. Considering it was working the best it ever has for a day, I'm guessing the CPU. Especially since I searched Intel i9 and what the actual fuck.
#intel
#cpu
#shortcircuit
#i9
#techhell -
It's either the CPU or the socket that has short circuited. Joy of fucking joys. Considering it was working the best it ever has for a day, I'm guessing the CPU. Especially since I searched Intel i9 and what the actual fuck.
#intel
#cpu
#shortcircuit
#i9
#techhell -
It's either the CPU or the socket that has short circuited. Joy of fucking joys. Considering it was working the best it ever has for a day, I'm guessing the CPU. Especially since I searched Intel i9 and what the actual fuck.
#intel
#cpu
#shortcircuit
#i9
#techhell -
Well, I've narrowed it down rather quickly to the secondary set of CPU power supply points on the motherboard. I'm pretty sure that an impedance of 0.6𝛀 between 12V and GND is not a good sign. At least the power supply is a good one and doing its job.
#techhell
#electrogirl
#troubleshooting
#computer -
Well, I've narrowed it down rather quickly to the secondary set of CPU power supply points on the motherboard. I'm pretty sure that an impedance of 0.6𝛀 between 12V and GND is not a good sign. At least the power supply is a good one and doing its job.
#techhell
#electrogirl
#troubleshooting
#computer -
Well, I've narrowed it down rather quickly to the secondary set of CPU power supply points on the motherboard. I'm pretty sure that an impedance of 0.6𝛀 between 12V and GND is not a good sign. At least the power supply is a good one and doing its job.
#techhell
#electrogirl
#troubleshooting
#computer -
today i learned that when #systemd gets restarted on my headless ubuntu 24.04 server, as it did with a recent update, this apparently also restarts systemd-networkd, and that kills ethernet connectivity until a reboot. since it's headless and doesn't currently have any other management options, that's never fun.
i saw that systemd-networkd was integrated with #netplan. i tried bypassing netplan and using a systemd-networkd configuration alone - which was an interesting challenge - but still, every time systemd-networkd restarts, networking is donezo. so i also tried switching to #networkmanager and ditching systemd-networkd, but then, somehow boot is delayed significantly and udisks2 fails to start (...why?!).
i have had to resort to setting up the watchdog package to reboot when network activity stops or pings fail. i don't like it, but i don't know what else to do in this distro.
also, kudos to anyone who can manage to use the term "systemd-networkd" in a post more than i did here.
-
today i learned that when #systemd gets restarted on my headless ubuntu 24.04 server, as it did with a recent update, this apparently also restarts systemd-networkd, and that kills ethernet connectivity until a reboot. since it's headless and doesn't currently have any other management options, that's never fun.
i saw that systemd-networkd was integrated with #netplan. i tried bypassing netplan and using a systemd-networkd configuration alone - which was an interesting challenge - but still, every time systemd-networkd restarts, networking is donezo. so i also tried switching to #networkmanager and ditching systemd-networkd, but then, somehow boot is delayed significantly and udisks2 fails to start (...why?!).
i have had to resort to setting up the watchdog package to reboot when network activity stops or pings fail. i don't like it, but i don't know what else to do in this distro.
also, kudos to anyone who can manage to use the term "systemd-networkd" in a post more than i did here.
-
today i learned that when #systemd gets restarted on my headless ubuntu 24.04 server, as it did with a recent update, this apparently also restarts systemd-networkd, and that kills ethernet connectivity until a reboot. since it's headless and doesn't currently have any other management options, that's never fun.
i saw that systemd-networkd was integrated with #netplan. i tried bypassing netplan and using a systemd-networkd configuration alone - which was an interesting challenge - but still, every time systemd-networkd restarts, networking is donezo. so i also tried switching to #networkmanager and ditching systemd-networkd, but then, somehow boot is delayed significantly and udisks2 fails to start (...why?!).
i have had to resort to setting up the watchdog package to reboot when network activity stops or pings fail. i don't like it, but i don't know what else to do in this distro.
also, kudos to anyone who can manage to use the term "systemd-networkd" in a post more than i did here.
-
today i learned that when #systemd gets restarted on my headless ubuntu 24.04 server, as it did with a recent update, this apparently also restarts systemd-networkd, and that kills ethernet connectivity until a reboot. since it's headless and doesn't currently have any other management options, that's never fun.
i saw that systemd-networkd was integrated with #netplan. i tried bypassing netplan and using a systemd-networkd configuration alone - which was an interesting challenge - but still, every time systemd-networkd restarts, networking is donezo. so i also tried switching to #networkmanager and ditching systemd-networkd, but then, somehow boot is delayed significantly and udisks2 fails to start (...why?!).
i have had to resort to setting up the watchdog package to reboot when network activity stops or pings fail. i don't like it, but i don't know what else to do in this distro.
also, kudos to anyone who can manage to use the term "systemd-networkd" in a post more than i did here.
-
I'm getting very tired of losing dozens of hours of my life getting #nextcloud to work about 3 times a year. More or less with every major upgrade.
This time I'm getting failed checks to sync my desktop app ("CSRF check failed"), along with sudden errors in the online web page that were resolved in past versions.
Wrinkle (always): shared hosting (#opalstack FTW) b/c I want my data stored offsite.
Returning errors:
1. Trusted_proxy incorrect. These were fine until the upgrade. Now I can't get anything to work (so far). It's not a warning, it's an error, in angry red.
2. memory limit not at least 512 MB. Except it is. It's set in the app's .user.ini file, which has no effect (this time, since upgrade).
3. set strict-transport-security... yes, that is set in .htaccess. No effect this time (worked fine before this upgrade)
About 4 more warnings that have lower priority. Basically, #sync stopped working, and that's a 100% bottleneck. Without sync of files, there's no point in having Nextcloud.
Ugh. I do not want to pay for Dropbox or whatever, but I might end up doing that; I seriously lose at least 30 hours a year on this, and there are many, many other things I'd rather do with that time.
I'll try to learn more, but if I have to basically take sysadmin classes to make Nextcloud work... no. I'll just pay for a commercial service.
*EDIT*: Thanks for the words, @pa
Note:
"Made Easy" - fuck, no"On premises or cloud" - good luck on shared hosting, sucker
"Regain control over your data" - If "control" means "it stays on my laptop and never syncs to my Nextcloud instance," then I guess this is accurate.
-
I'm getting very tired of losing dozens of hours of my life getting #nextcloud to work about 3 times a year. More or less with every major upgrade.
This time I'm getting failed checks to sync my desktop app ("CSRF check failed"), along with sudden errors in the online web page that were resolved in past versions.
Wrinkle (always): shared hosting (#opalstack FTW) b/c I want my data stored offsite.
Returning errors:
1. Trusted_proxy incorrect. These were fine until the upgrade. Now I can't get anything to work (so far). It's not a warning, it's an error, in angry red.
2. memory limit not at least 512 MB. Except it is. It's set in the app's .user.ini file, which has no effect (this time, since upgrade).
3. set strict-transport-security... yes, that is set in .htaccess. No effect this time (worked fine before this upgrade)
About 4 more warnings that have lower priority. Basically, #sync stopped working, and that's a 100% bottleneck. Without sync of files, there's no point in having Nextcloud.
Ugh. I do not want to pay for Dropbox or whatever, but I might end up doing that; I seriously lose at least 30 hours a year on this, and there are many, many other things I'd rather do with that time.
I'll try to learn more, but if I have to basically take sysadmin classes to make Nextcloud work... no. I'll just pay for a commercial service.
*EDIT*: Thanks for the words, @pa
Note:
"Made Easy" - fuck, no"On premises or cloud" - good luck on shared hosting, sucker
"Regain control over your data" - If "control" means "it stays on my laptop and never syncs to my Nextcloud instance," then I guess this is accurate.
-
I'm getting very tired of losing dozens of hours of my life getting #nextcloud to work about 3 times a year. More or less with every major upgrade.
This time I'm getting failed checks to sync my desktop app ("CSRF check failed"), along with sudden errors in the online web page that were resolved in past versions.
Wrinkle (always): shared hosting (#opalstack FTW) b/c I want my data stored offsite.
Returning errors:
1. Trusted_proxy incorrect. These were fine until the upgrade. Now I can't get anything to work (so far). It's not a warning, it's an error, in angry red.
2. memory limit not at least 512 MB. Except it is. It's set in the app's .user.ini file, which has no effect (this time, since upgrade).
3. set strict-transport-security... yes, that is set in .htaccess. No effect this time (worked fine before this upgrade)
About 4 more warnings that have lower priority. Basically, #sync stopped working, and that's a 100% bottleneck. Without sync of files, there's no point in having Nextcloud.
Ugh. I do not want to pay for Dropbox or whatever, but I might end up doing that; I seriously lose at least 30 hours a year on this, and there are many, many other things I'd rather do with that time.
I'll try to learn more, but if I have to basically take sysadmin classes to make Nextcloud work... no. I'll just pay for a commercial service.
*EDIT*: Thanks for the words, @pa
Note:
"Made Easy" - fuck, no"On premises or cloud" - good luck on shared hosting, sucker
"Regain control over your data" - If "control" means "it stays on my laptop and never syncs to my Nextcloud instance," then I guess this is accurate.
-
I'm getting very tired of losing dozens of hours of my life getting #nextcloud to work about 3 times a year. More or less with every major upgrade.
This time I'm getting failed checks to sync my desktop app ("CSRF check failed"), along with sudden errors in the online web page that were resolved in past versions.
Wrinkle (always): shared hosting (#opalstack FTW) b/c I want my data stored offsite.
Returning errors:
1. Trusted_proxy incorrect. These were fine until the upgrade. Now I can't get anything to work (so far). It's not a warning, it's an error, in angry red.
2. memory limit not at least 512 MB. Except it is. It's set in the app's .user.ini file, which has no effect (this time, since upgrade).
3. set strict-transport-security... yes, that is set in .htaccess. No effect this time (worked fine before this upgrade)
About 4 more warnings that have lower priority. Basically, #sync stopped working, and that's a 100% bottleneck. Without sync of files, there's no point in having Nextcloud.
Ugh. I do not want to pay for Dropbox or whatever, but I might end up doing that; I seriously lose at least 30 hours a year on this, and there are many, many other things I'd rather do with that time.
I'll try to learn more, but if I have to basically take sysadmin classes to make Nextcloud work... no. I'll just pay for a commercial service.
*EDIT*: Thanks for the words, @pa
Note:
"Made Easy" - fuck, no"On premises or cloud" - good luck on shared hosting, sucker
"Regain control over your data" - If "control" means "it stays on my laptop and never syncs to my Nextcloud instance," then I guess this is accurate.
-
I'm getting very tired of losing dozens of hours of my life getting #nextcloud to work about 3 times a year. More or less with every major upgrade.
This time I'm getting failed checks to sync my desktop app, along with sudden errors in the online web page that were resolved in past versions.
Wrinkle (always): shared hosting (#opalstack FTW) b/c I want my data stored offsite.
Returning errors:
1. Trusted_proxy incorrect. These were fine until the upgrade. Now I can't get anything to work (so far). It's not a warning, it's an error, in angry red.
2. memory limit not at least 512 MB. Except it is. It's set in the app's .user.ini file, which has no effect (this time, since upgrade).
3. set strict-transport-security... yes, that is set in .htaccess. No effect this time (worked fine before this upgrade)
About 4 more warnings that have lower priority. Basically, #sync stopped working, and that's a 100% bottleneck. Without sync of files, there's no point in having Nextcloud.
Ugh. I do not want to pay for Dropbox or whatever, but I might end up doing that; I seriously lose at least 30 hours a year on this, and there are many, many other things I'd rather do with that time.
I'll try to learn more, but if I have to basically take sysadmin classes to make Nextcloud work... no. I'll just pay for a commercial service.
-
"...an important distinction between overt #racism – the systems rarely directly say stuff like “Black people are bad” – and covert racism: how the system treated queries about consequential matters, given an African American English prompt. On overt measures, the systems were fine. On covert measures, they were a disaster:"
-
"...an important distinction between overt #racism – the systems rarely directly say stuff like “Black people are bad” – and covert racism: how the system treated queries about consequential matters, given an African American English prompt. On overt measures, the systems were fine. On covert measures, they were a disaster:"
-
"...an important distinction between overt #racism – the systems rarely directly say stuff like “Black people are bad” – and covert racism: how the system treated queries about consequential matters, given an African American English prompt. On overt measures, the systems were fine. On covert measures, they were a disaster:"
-
"...an important distinction between overt #racism – the systems rarely directly say stuff like “Black people are bad” – and covert racism: how the system treated queries about consequential matters, given an African American English prompt. On overt measures, the systems were fine. On covert measures, they were a disaster:"
-
"...an important distinction between overt #racism – the systems rarely directly say stuff like “Black people are bad” – and covert racism: how the system treated queries about consequential matters, given an African American English prompt. On overt measures, the systems were fine. On covert measures, they were a disaster:"