Calculator Manipulator

  • 2 Posts
  • 85 Comments
Joined 6 years ago
cake
Cake day: April 16th, 2019

help-circle
  • The problem is running GUI code as root as it’s never been vetted for that. What you want, effectively, is to have EDITOR variable of your session set to kate and open system files using sudoedit. I’m a terminal guy myself, so this exact thing is enough for me. Having said that - I’m sure someone will chime in with a plugin/addon/extension/etc that adds this to the right click context for what I assume is KDE. Or you can try looking for that om your favourite search engine.





  • It is quick and easy. Maintaining any other OS side by side is always a bigger ordeal than not doing it. It breaks the other way around as well - If you were running some linux distro and then tried dual booting by installing windows - no way you’d be able to boot into linux without extra tweaking.








  • If you’re dead set to run lemmy - then just do it! If soam becomes a problem - turn on registration verification. Spam usually comes in waves, so you don’t even have to keep that barrier on all the time. Having said that - if you want some sort of nationality verification - application process could enable it.

    If you’re not set on lemmy - give piefed a shot. That’s what I would run if I were setting up from scratch. Same format social media, but, at least from what I’m hearing - better software.


  • Setting up is easy, but keeping it up to date is often troublesome. Releases are far and few between and as such, whenever there is one, it includes a lot of changes. That leads to some instances having trouble pretty much every time; I’ve been on the unlucky side enough times to be wary.

    Lemmy.cafe runs on 2 dual vcore 4gb ram VMs on digitalocean - one for db, another for lemmy itself.

    Lemmy prides itself in being written in rust, but it leaks memory like a sieve - I’ve had split up the containers into smaller tasks (there’s an official flag you can pass to it), double them up and set memory limits. That way when something gets killed by the kernel it’s not really noticable to the end user.

    Running a public instance of anything is a security concern, let alone alpha-beta software like lemmy. If you do run it on your homelab at home - at least get the cheapest vm in the cloud to hide your home IPs. You’d probably need to set up a wireguard tunnel to ensure outgoing federation does not reveal the IPs to other instances.

    Instance level moderation is up to you. Don’t be too dreamy - nobody will join your instance just because you have it running. Other than spammers and voting bots, that is. Moderation tools are just not there, so you’ll have to fiddle in the db directly.

    Having said all that - if all you want is a personal inatance - go for it! With sign ups disabled it’s a much less stressful experience!






  • Majority of openrc/hardened/selinux binhost setup is done, need to figure out the small things.

    Lemmy was also giving a bit of a headache, fiddled with limits some more.

    I’m fairly certain there’s been an attempt to play with some opnsense config, but there was only time to install the updates. Or maybe this was last week 🤔