• 0 Posts
  • 37 Comments
Joined 1 year ago
Cake day: July 1st, 2023
  • dust_accelerator@discuss.tchncs.detoTechnology@lemmy.world•A supermarket trip may soon look different, thanks to electronic shelf labelsEnglish
    11·
    5 months ago

    In 2291, in an attempt to control violence among deep space miners the New Earth Government legalized no-holds-bared fighting.

    Liandri Mining Corporation, working with the NEG, established a series of leagues and bloody public exhibitions.

    The fight’s popularity grew with their brutality. Soon, Liandri discovered that the public matches were their most profitable enterprise.

    The professional league was formed; a cabal of the most violent and skilled warriors in known space, selected to fight in a Grand Tournament.

    Now it is 2341, 50 years have passed since founding of DeathMatch. Profits from the Tournament number in the hundreds of billions.

    You have been selected to fight in the professional league by the Liandri Rules Board. Your strength and brutality are legendary.

    The time has come to prove you are the best- to crush your enemies- to win the Tournament.

  • dust_accelerator@discuss.tchncs.detoSelfhosted@lemmy.world•What's wrong with Nextcloud, and why is it slow/clunky?English
    3·
    9 months ago

    PostgreSQL is definitely a boost to performance, especially if you offload the DB to a dedicated server (depending on load, can even be a cluster)

    Nevertheless, it probably has much to do with how it’s deployed and how many proxies are in front of it, and/or VPN. If you have large numbers of containers and small CPU/low memory hardware, and either running everything on one machine or have some other limitations, it’ll be slow.

    Admittedly, I’m not very familiar with the codebase, but I feel Apache isn’t improving the speed either. Not exactly sure how PHP is nowadays with concurrency and async, but generally a microservice type architecture is nice because you can add more workers/instances wherever a bottleneck emerges.

  • dust_accelerator@discuss.tchncs.detolinuxmemes@lemmy.world•That's LTT in the bottom
    11·
    9 months ago

    Beware of the W̷̞̬̍̌͘͜ĭ̴̬̹̟͕̒̆̈́n̸̢̧̙̈́̅̂̆̕͜ͅd̵̟̟̪͎̀̀ő̴̼̺̺́̐̂͘w̵̨͊̀s̵̡͎̭̊ ̸͔̬͔̜̊́̈́̌̈́ͅŬ̴͉͚̳̌̉͘͝p̸̼̅̆͐̃̑d̸̜͂ǎ̵̛̯̏͝ť̷̰é̸͇͝ as it can screw up/overwrite your other bootloader completely.

    Kinda sucks, when you’ve got a meeting/work and you find out that forced update made your system unbootable/partially unbootable and you now get to live boot in and go fixing the EFI partition manually, in the CLI.

    That happened to me once and that’s when I decided feature parity was less important than a reliable system that “just works” for getting things done on a schedule. (I removed windows completely, in case that wasn’t clear)

    Anyhow, make sure you install windows to a separate drive that can’t see any others during the windows install, then will keep the bootloader separate.

  • dust_accelerator@discuss.tchncs.detolinuxmemes@lemmy.world•That's LTT in the bottom
    30·
    9 months ago

    I tend to agree.

    Nevertheless, some unknown implementation can have bugs and things can go wrong and there’s nothing you can do about it, short of “rebooting” or d̷o̶w̸s̸i̷n̴g̸ ̴t̶h̸e̷ ̸h̵a̵r̵d̷ ̵d̷r̶i̴v̶e̷ ̵w̶i̴t̸h̷ ̸̞̺͠h̵̺͙̎̍o̸͔͠ͅḻ̷̀̇y̵͚͍̎ ̷͉̅̅w̸͎̔a̷̧̫̒́t̶̼̉̓ę̵̾͗r̶̫͑͑ ̴̣̿͒(̷͙̎a̸̬̺͝͝n̸̞̓̓d̴̬͌̍ ̸͇͕͌͝s̷̡̯̓͝u̸̡̳̇͝b̴̳͜͠s̷͍̘̽ë̵̜q̷̝͐̄ȕ̵̞̐e̷̲̠̐́ń̴̨̙͝t̸̛̬͝l̶̮̔͠y̴͕̪̑͝ ̵̖̆ḃ̴̪̟u̶̢͓͑̌y̵̜̤͌̏i̵̦̋ň̴̨͚̀g̸͓͑ ̴͍̬̽à̶͜ ̴͇͔̓n̴̬͂͜ì̷̢̛̯c̴̤̖̈́e̶̼̫̐̊ ̵̹̏͝f̸̙̀̑r̷̪̩͆͆e̸̤̫͛͋s̷̢̙̏h̷͇͔́ ̸̭̆͝N̷̰͗͛͜V̶͇͒̚M̸̟̍͜ě̷̛̟ ̸̢̞́͝a̷͙͔͒͒n̷̻͇͝d̸̘̥͌̾ ̴̜͓͑p̷̬͑͊ŭ̸̮̏t̸̲̀t̴̡͚̽í̶͎͓̑n̴͕̘̒̈́g̴͓̰̓͝ ̵͓̎a̴̻̼͗ ̷̦̍̈́s̷̥̅̈l̴̝̂e̴̞̅͊ḛ̴̊̅k̷͚̕ ̵̛̼̬͗D̴̻̾̽e̵̙͂̊b̷̝͘ī̵̢͇ą̵̂n̴͖̑ ̶̼̚h̴̼͂͑e̷̲͆̆a̵̡̋d̸̢͔̈l̶͕̍̍e̸̛͕̙̒s̶̞͔̀͠s̸̯͖̕ ̵͍̦̈́̉ ̸̨̨̓i̸̙͖͗̌ņ̶̯̍s̸̡̖͗̇ṯ̷́̒ä̵̦́̎l̶̼̄l̵̨͊̊ ̴̳͑͗ó̵͎̅ǹ̴͈̚ ̷͖͊͝i̷̠͇̊t̷̼̞͒͘)̵͎̤̔͌