"I'd like to return my companion-bot, serial code JX99031."
"Sure; and could you describe the fault you encountered?"
"Fault? Nah, it's perfect. Never been so well taken care of. Hate having to send it back honestly."
"Then... why are you returning it?"
"This will sound really weird."
"It misses it's mum."
"Oh! That's a rare glitch. No return necessary, it can visit the factory any time during business hours."
I have been notified by an Admin here that they are getting 60 reports a day about my account. As far as I can tell, I'm not breaking any rules, and I've done my best to be a good person here. But this admin is going to suspend my account.
It's the Admin's instance, so I fully support their choice to eliminate a source of frustration, but something to consider: a person who is doing nothing wrong can be run off one instance by a mob from another instance. That seems ... not cool. 1/x
Ich habe mir für meine Bachelorarbeit einen post-update #git-hook eingerichtet, der nach einem Commit das erzeugte PDF in die ownCloud kopieren soll.
Wenn ich das Skript von Hand ausführe, funktioniert alles. Leider tut es das nicht bei einem Commit (und Push).
Es beinhaltet nicht mehr als das:
exec cp -u src/bachelorarbeit.pdf ~/Documents/HAW/.
Unter src liegen dabei die LaTeX-Dateien und auch das erzeugte PDF.
Jemand ne Idee, was ich verkehrt mache? 🤔
I tend to stay away from politics on Mastodon, but this is some really great background on the whole Russian hacking hysteria in the US:
But anyone who sees the Russian activity as an antidemocratic outrage should be condemning the United States just as loudly, and treating the Russia story as some kind of unprecedented act of covert control is laughable.
@InspectorCaracal In case that whole post doesn’t come through without logging in
Bosch's War on Self Repair
Husband, father of two, software developer and creator of some Bitmessage stuff.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!