• 0 Posts
  • 130 Comments
Joined 1 year ago
cake
Cake day: August 2nd, 2023

help-circle
    • I can’t simultaneously play a third MMO (already got FFXI and FFXIV)
    • X4 custom start allows me to jump to the parts I want to play instantly, no matter if it’s starting wars, flooding the market, dogfighting, etc
    • My X4 save is a gzip file: no need to worry about latency after moving to another country etc (my EVE account is locked to a region halfway across the world)
    • I don’t have to wait for irl people to do something fun in X4
    • The gziped save file is in xml format. If something breaks I can just fix it
    • X4 has a huge modding scene for whatever features you want
    • X4’s modding tools are super easy to learn: it’s all xml and lua. Took me only 2 hours to figure out how to modify the UI from scratch.






  • An alternative definition: a real-time system is a system where the correctness of the computation depends on a deadline. For example, if I have a drone checking “with my current location + velocity will I crash into the wall in 5 seconds?”, the answer will be worthless if the system responds 10 seconds later.

    A real-time kernel is an operating system that makes it easier to build such systems. The main difference is that they offer lower latency than a usual OS for your one critical program. The OS will try to give that program as much priority as it wants (to the detriment of everything else) and immediately handle all signals ASAP (instead of coalescing/combining them to reduce overhead)

    Linux has real-time priority scheduling as an optional feature. Lowering latency does not always result in reduced overhead or higher throughout. This allows system builders to design RT systems (such as audio processing systems, robots, drones, etc) to utilize these features without annoying the hell out of everyone else.






  • StarDreamer@lemmy.blahaj.zonetolinuxmemes@lemmy.worldsystemdeez nuts
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    7 months ago

    systemd tries to unify a Wild West situation where everyone, their crazy uncle, and their shotgun-dual-wielding Grandma has a different set of boot-time scripts. Instead of custom 200-line shell scripts now you have a standard simple syntax that takes 5 minutes to learn.

    Downside is now certain complicated stuff that was 1 line need multiple files worth of workarounds to work. Additionally, any custom scripts need to be rewritten as a systemd service (assuming you don’t use the compat mode).

    People are angry that it’s not the same as before and they need to rewrite any custom tweaks they have. It’s like learning to drive manual for years, wonder why the heck there is a need for auto, then realizing nobody is producing manual cars anymore.




  • Pretty sure expiry is handled by the local crowdsec daemon, so it should automatically revoke rules once a set time is reached.

    At least that’s the case with the iptables and nginx bouncers (4 hour ban for probing). I would assume that it’s the same for the cloudflare one.

    Alternatively, maybe look into running two bouncers (1 local, 1 CF)? The CF one filters out most bot traffic, and if some still get through then you block them locally?


  • I’ve recently moved from fail2ban to crowdsec. It’s nice and modular and seems to fit your use case: set up a http 404/rate-limit filter and a cloudflare bouncer to ban the IP address at the cloudflare level (instead of IPtables). Though I’m not sure if the cloudflare tunnel would complicate things.

    Another good thing about it is it has a crowd sourced IP reputation list. Too many blocks from other users = preemptive ban.



  • Iirc the specific reason behind this is

    • sudo by default requires a tty to run
    • vim’s bang spawns a tty to execute commands
    • nvim’s bang executes the command directly, then pipes the output to nvim

    As a result, sudo (without args) can’t work in nvim as it doesn’t have a tty to prompt the user for passwords. Nvim also used to do what vim did, but they found out spawning the tty was causing other issues (still present in vim) so they changed it.