• 5 Posts
  • 52 Comments
Joined 2 years ago
cake
Cake day: January 5th, 2024

help-circle
  • Engie, Gunner, Scout (with single-target focused loadouts) do tend to perform best in dreadnought missions. Driller plays more of a support role, but can do decent chip damage and make pathways to ensure cover for teammates. There are also tactical support strategies such as fully freezing dreadnoughts while weak points are up and having a teammate do a massive burst of damage.

    You can build single-target damage builds as driller with overclocks and they will work decently well, with the caveat that the weapons used for the build will lose a lot of their normal utility.





  • I had written about this in their Discord in a thread:

    using this shim script I made, do the following:

    1. Install Raft with Proton 9.0-# prefix
    2. Place the shim file into the game directory
    3. Mark the shim as executable
    4. Set Steam launch options to: WINEDLLOVERRIDES="winhttp.dll=n,b" ./shim %command%
    5. Launch Raft once
    6. Place RMLLauncher.exe into Raft game directory
    7. Look for a plaintext target file that should be created in the raft directory
    8. Copy the location of the RMLLauncher.exe (exact folder and filename) (right click > Copy Location in KDE / Steam Deck desktop mode)
    9. Paste this location into the target file and save
    10. Launch Raft
    11. Go through RMLLauncher first-time steps
    12. Press Play
    13. Stop the game and add mods into Raft mods folder
    14. Launch the game and load the mods in-game
    15. Play Raft modded through Proton

    (Instructions adapted from both mine and Discord user YumiChi’s)

    This method doesn’t require custom installations, messing with bottles, nor wine runtimes other than Proton.



  • If you’re running an email server for more than a handful of persistent users, I’d probably agree. However, there are self-host solutions that do a decent job of being ‘all-in-one’ (MailU, Mailcow, Docker-Mailserver) that can help perform a lot of input filtering.

    If your small org just needs automation emails (summaries, password resets), it’s definitely feasible to do actually, as long as you have port 25 available in addition to 465, 587 and you can assign PTR records on reverse DNS. Optionally you should use a common TLD for your domain as it will be less likely to be flagged via SpamAssassin. MXToolbox and Mail-Tester together offer free services to help test the reliability of your email functionality.


  • I’m currently going through a similar situation at the moment (OPNSense firewall, Traefik reverse proxy). For my solution, I’m going to be trial running the Crowdsec bouncer as a Traefik middleware, but that shouldn’t discourage you from using Fail2Ban.

    Fail2Ban: you set policies (or use presets) to tempban IPs that match certain heuristic or basic checks.

    Crowdsec Bouncer: does fail2ban checks if allowed. Sends anonymous bad behavior reports to their servers and will also ban/captcha check IPs that are found in the aggregate list of current bad actors. Claims to be able to perform more advanced behavior checks and blacklists locally.

    If you can help it, I don’t necessarily recommend having OPNSense apply the firewall rules via API access from your server. It is technically a vulnerability vector unless you can only allow for creating a certain subset of deny rules. The solution you choose probably shouldn’t be allowed to create allow rules on WAN for instance. In most cases, let the reverse proxy perform the traffic filtering if possible.




  • For desktop/workstation users: the simple answer is just use the flatpak from Flathub or from some other source if you need a user package that doesn’t align to the ethos of your chosen distro. In most cases desktop Linux users have gone beyond self-packaging for specific library versions and just use a separate set of common libraries to power application needs beyond the out of box experience of any given distro. It’s part of why immutable distros are starting to take off and make more sense for desktop/workstation use-cases.

    For servers, it’s in the nature to become part of the technical debt you are expected to maintain, and isn’t unique among RHEL, OpenSUSE Leap, Debian, Ubuntu, or any other flavor of distro being utilized.



  • Ocis/OpenCloud can integrate with Collabora, OnlyOffice but don’t currently have things like CalDAV, CardDAV, E2EE, Forms, Kanban boards, or other extensible features installable as plugins in Nextcloud.

    If you desire a snappy and responsive cloud storage experience and don’t particularly need those things integrated into your cloud storage service, then Ocis or OpenCloud might be something to look into.


  • Under what means? The target is public sector and the OS to replace (Windows 10, Windows 11) would be a relatively compatible release target. Fedora is a competent leading edge (Wayland, Pipewire, BTRFS) distro that runs as a 6 month point release. I wouldn’t see many reasons to not go with Fedora Workstation as a base unless going for an immutable base or a different core distro (OpenSUSE or Debian mainly).

    EDIT: Missed that this is going to be immutabe, so it is likely being based on Fedora Kinoite, meaning there really aren’t many alternatives besides OpenSUSE’s offerings.


  • As I understand it, most of the Pebble’s OS is currently Open Source. Traditionally, you could download updates and applets, watch faces for your Pebble through it’s app, as well has have many phone integrations. Most of the phone integrations can now be done through GadgetBridge and applets downloaded from Rebble.

    Given the minimal need for always-online or really much of a internet connection at all beyond what is needed for third-party applets (weather watch faces, etc.), the older Pebble smart watches are able to be made about as private as one could reasonably expect from a Bluetooth wearable.

    The two upcoming remakes appear to be basing the mobile app and applet repo upon the Rebble community’s work, if not outright using it as the source. If the watches gain GadgetBridge support and/or the companion app is fully open source, I imagine these will be as worthy as the older watches.



  • As far as KDE vs. GNOME is concerned: KDE contains a lot of customizable features as an expectation and thus has great support for a wide array of customization. Both KDE and GNOME are extensible, with third-party extensions to extend or change functionality available. What makes GNOME less customizable, albeit supporting stylesheets and extensions, both are not expected to be used in any form (outside of defaults provided via Adwaita), and neither do many independent apps written in GTK3, GTK4. GNOME offers fairly minimal customization options without resorting to GNOME Tweaks, third-party extensions, and unsupported customized themes: all things that can break GNOME as while the customization does exist, the developers don’t embrace it and have no expectation to not break it with any update.


  • A general checklist for flags that software will enshittify:

    • owned by publicly-traded company
    • backed by VC or other expecting sources of funding
    • product is closed-source
    • company tries to circumvent open-source licensing of product (often for financial gain)
    • product has transferred ownership to a different company (through monetary transaction or similar)
    • product incorporates DRM
    • organization that owns the product has a track record for bad behavior

    On their own, not all of these flags are excellent indicators. Some are better than others in a vacuum. If you see a product start to check several of these flags, it might be time to jump ship early (to a fork or other competing project).



  • It’s funny how EA is attributing their statistic to something can be strongly disproven. When looking at the given statistic they provided, they don’t specify the raw count of cheaters banned, but simply the rate. Even giving the generous assumption that EA’s statistics aren’t significantly flawed, they show an alleged large drop in cheaters bottoming out in the week of Nov. 4, 2024, before starting to rise up again. Does something else coincide with the rate of cheaters dropping in the week of Nov. 4? There is in fact something that does. Season 23 was released the fifth with a large spike of players being brought into the game. Without a more comprehensive statistic graph over several months, it looks like EA is trying to just capitalize on the fact that a large influx of players joining the game will drop the rates of cheaters momentarily, and then passing it off as evidence that Linux cheating was rampant. Quite disingenuous.