Must your climax be fueled by our frustrations? Vibrators are cheap, you know.

Must your climax be fueled by our frustrations?

Maybe that’s exactly what gets him off.

Frankly, this should be implemented with something like a combination of:

https://github.com/QazCetelic/lemmy-know

Lemmy Know (let me know) is a lightweight CLI application / Docker service that monitors Lemmy for reports on posts and comments and sends notification. These can be sent to a Discord channel with a webhook or as MQTT messages (schema), which is useful for more complex setups with e.g., Node-RED.

https://www.home-assistant.io/

Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts.

https://www.home-assistant.io/integrations/mqtt/

MQTT (aka MQ Telemetry Transport) is a machine-to-machine or “Internet of Things” connectivity protocol on top of TCP/IP. It allows extremely lightweight publish/subscribe messaging transport.

https://github.com/DevelopmentalOctopus/ha-buttplug

Buttplug.io Integration for Home Assistant

https://intiface.com/central/

Intiface® Central is an open-source, cross-platform application that acts as a hub for intimate haptics/sensor hardware access

Some collection of hardware devices from:

https://iostindex.com/?filter0Availability=Available,DIY&filter1Connection=Digital&filter2ButtplugSupport=4

That’d permit for, say, having message events drive a state machine to control devices or something like that.

GitHub - QazCetelic/lemmy-know: Send notifications when Lemmy reports are made through Discord, ntfy.sh or as MQTT message

Send notifications when Lemmy reports are made through Discord, ntfy.sh or as MQTT message - QazCetelic/lemmy-know

GitHub
The unix shell pipeline keeps giving
I’m not sure whether I’m more impressed or disturbed by the amount of thought you’ve given this
It’s just not the same
Systemd is the greatest innovation that Linux has ever seen bar none.
Since I started actually doing system administration and actually interacting directly with SystemD all of the hate for it I’d soaked up from enthusiast forums melted away. I’ve never used any of the other init systems so maybe I’m missing out, but I do appreciate SystemD for what it does
pipewire feels close
systemd has been a complete, utter, unmitigated success

Eleven init systems enter, one init system leaves.

Tyblog

I fully agree. I am a user with a bit of technical background, but not a lot of detailled knowledge about the inner workings of an operating system (i know boolean logic and basic programming structures - in Pascal lol - from the 90’s, what a transistor does and stuff, how to build my own PCs and handle filesystems and troubleshooting).

With init scripts, i hit a wall pretty fast.

With Systemd i know how to start, stop and configure services, and the suite built around it uses the same conventions everywhere, making the everyday life with Linux for someone like me so much easier and more transparent than ever before.

Have you considered that just “reaping old process IDs” wasn’t enough responsibility for an init daemon on a secure, robust system? That maybe it should be protecting other parts of the system and tracking the liveness of a desired service?

What is the benefit of specifically doing that in init?

If I see an argument like this then I can only assume the interlocutor doesn’t do software engineering.

Its more likely that the user simply has simple needs like running stuff at startup which any init system can do and doesn’t see as much benefits as poster.

Also who loves systemd-resolved?

What is the benefit of specifically doing that in init?

What’s the alternative?

Also who loves systemd-resolved?

I don’t think I will ever love anything DNS-related, but it’s still the best solution I’ve used for name resolution on a system with many interfaces.

Being able to assign a nameserver per interface with a domain wildcard is a fucking godsend. I use it every day with a hook script because my job uses some private domains but I don’t want to send my entire DNS history through the VPN. Now ~job.com goes to tun0 and that’s the end of it.

systemd-resolved is not perfect but with libnss’s overly rigid nature the only alternative for my use-case would be to recreate similar functionality to resolved with dnsmasq – which is just objectively worse especially when you want to use DHCP sometimes but not always. Why reinvent the wheel? resolved does its job and does it well. I had some issues with it a few years ago but have been using it for the past couple years without complaint.

may i ask you to kindly provide the source of this image?
frenky_hw, here’s the specific image: twitter (hopefully it is, twitter doesn’t work for me rn)
X

X (formerly Twitter)
Tal out here giving solutions
An admirable example of working harder, not smarter
The other day I wrote I like snaps and shot more rope than Spiderman.
Flatpak is amazing especially with storage being so cheap these days.
OK, Satan.
I still remember the bad old days of stale repositories and compiling from scratch. Never again.
There was 25 years between c;m;mi and lennart’s cancer, filled with excellent choices better than either.
Just replying to keep the vibes going.
I just had an issue with the vscodium flatpak, been using it for two months with no issue in an online course, got to learning GUIs, import module, doesn’t exist. I couldn’t figure out why it wasn’t there, installed three different python versions of it three different ways, still nothing. Couldn’t even get vscodium to point to a different interpreter that I knew was there (yet it doesn’t say it’s not there, just that some things won’t work). Still nothing. Three hours later, after trying everything I could think of, I realized that I installed the flatpak version when it clicked that I didn’t have python 3.13 in my repos, yet that was the only one I could see in vscodium.
That sounds like user error.
Vscodium isn’t in the repos for opensuse, but yes, this user should have found a way to install it on bare metal in the first place.
Have you tried butterflies?
From a broad enough perspective, everything is user error
Except when the error is in the chip architecture.
SystemD is that like ntoskrnl.exe?

delete it for free space! (and freedom!)

…i’m not asking. do it.

Systemd is great! The best thing about it is how efficient and minimal it is!
Ok, so, this place IS filled with furries. Cool.
Every online space is filled with furries, especially the most furry-hostile spaces!
That’s disgusting, I prefer furry-hostile tabs!
So the hostility can adapt to your system
Linux wouldn’t work without furries
Is putting phone in ass a furry thing?
The depicted character has a snout and cat ears
maybe she was just born that way
Why cats ears now, I can’t say
Maybe she was just born that waaaaayyyyy
Thought it was more a prison thing.
We’re all shipping the penguin and the wildebeest.

I just like being able to use things I learn across Ubuntu, Debian, Arch and RHEL.

Also prefixing a command with systemd-cat and having the logs go to the journal is pretty nice. Then I don’t have to worry about rotating them.

Well, that’s one way to “use” systemd, I guess.
Please tell me your phone has a flared base?

Rule 34:

If there’s a user base, there’s buttplug.io support…

Error: That number is already picked for a different rule. Please select a different number.
Maybe consider rule 33. ‘Lurk more its never enough’