• 2 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: July 23rd, 2023

help-circle


  • poettering is an absolute good guy here

    Agreed. But he’s also an abrasive know-it-all. A modicum of social skills and respect goes a long way towards making others accept your pet projects.

    pulesaudio protocol is used within pipewire and it works just fine.

    I wasn’t talking about the protocol, I was talking about the implementation: PulseAudio is a crashy, unstable POS. I can’t count the number of hours this turd made me waste, until PipeWire came along.



  • I totally agree. I used to hate systemd for breaking the traditional Unix philosophy, but the reality is that a tight init and service-tracking integration tool really was required. I work with and appreciate systemd every day now. It certainly didn’t make things simplier and easier to debug, but it goes a long way towards making a Linux system predictable and consistent.

    Poettering can go fuck himself though - and for PulseAudio too. I suspect half of the hate systemd attracted over the years was really because of this idiot.







  • Not really. It would only require the new user on the new instance to be able to “own” posts and comments made by the old user on the old instance.

    For example, the old user account could transfers its posting and commenting history to the new account (and the new account would be asked to accept the transfer of course).

    When it’s done, whoever visits the new account, will see posts and comments made from the old account up until the transfer, and the old account’s posting and commenting history would be blank.

    Then If the old account were to continue posting afterwards for some odd reason, it would build a new posting and commenting history from that point on. Or the transfer could become effective only after the old account is deleted permanently.

    I don’t know exactly how any of this is implemented, but it would definitely not require monkeying with the actual past posts and comments.