Just a regular Joe.

  • 0 Posts
  • 80 Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle




  • So you want to create a human exploitation / profit maximising system?

    Pretty sure those are proprietary algorithms, with some common knowledge foundations that LLMs will happily tell you about.

    It’s all simple enough at a small scale, but the challenge is optimizing it for your use-cases, and building for scale & reliability in a cost efficient manner.

    Such companies will likely also have top notch software engineers & statisticians, marketing teams, psychologists and lawyers on the payroll, all contributing their part to the perpetuation of human misery in the name of corporate profit.





  • If it helps to accurately fill in the details correctly in the backend system, which are then properly validated or escalated for human review/intervention (and let the human requester choose the escalation path too, as opposed to blindly submitting), then it sounds great.

    Guided experiences, leading to the desired outcome, with less need for confused humans to talk to confused humans.

    I want the same for most financial approvals in my company. Finance folks speak a different language to most employees, but they have an oversized impact on defining business processes, slowing down innovation, frustrating employees, and often driving costs UP.









  • Another technique that helps is to limit the amount of information shared with clients to need to know info. This can be computationally intensive server-side and hard to get right … but it can help in many cases. There are evolving techniques to do this.

    In FPS games, there can also be streaming input validation. eg. Accurate fire requires the right sequence of events and/or is used for cheat detection. At the point where cheats have to emulate human behaviour, with human-like reaction times, the value of cheating drops.

    That’s the advanced stuff. Many games don’t even check whether people are running around out of bounds, flying through the air etc. Known bugs and map exploits don’t get fixed for years.


  • ALSA is lowest level, and is the kernel interface to audio hardware. Pipewire provides a userspace service to share limited hardware.

    Try setting “export PIPEWIRE_LATENCY=2048/48000” before running an audio producing application (from the same shell).

    Distortion can sometimes be related to the audio buffers not getting filled in time, so increasing the buffering as above gives it more time to even out. You can try 1024 instead of 2048 too.

    There is no doubt a way to set it globally, if it helps.

    Good luck!


  • But not Fire tablets (kids profile) or Samsung TV or many others that Plex currently supports.

    JellyFin android phone app’s UI is a little weird at times, but does work pretty well for me.

    What I would adore from any app would be an easy way to upload specific content and metadata via SFTP or to blob storage and accessible with auth (basic, token, or cloud) to more easily share it with friends/family/myself without having to host the whole damn library on the Internet or share my home Internet at inconvenient times.

    Client-side encryption would be a great addition to that (eg. password required, that adds a key to the key ring). And of course native support in the JellyFin/other apps for this. It could even be made to work with a JS & WASM player.


  • And contributions to codebases that have developed with the goal of meeting the team’s own needs, and who similarly don’t have the time or space to refactor or review as needed to enable effective contributions.

    Enabling Innersource will be a priority for management for only two weeks, anyway, before they focus on something else. And if it even makes it into measurable goals, it will probably be gamed so it doesn’t ruin bonuses.

    Do you also work for $GenericMultinationalCompany, per-chance? Do you also know $BillFromFinance?