Web developer. Lead developer of PieFed

  • 611 Posts
  • 2.99K Comments
Joined 3 years ago
cake
Cake day: January 4th, 2024

help-circle






  • The testing instance is not a source of traffic so the quota would have no direct effect on it. The savings there are a result of what’s happening on other instances.

    I’m showing that the vote quota reduced federation traffic for the whole threadiverse by 30% to 50%. What’s happening there is lemmy.world, etc, where all the communities are, are sending less votes to everywhere (including to my testing instance). It’s the community hosters that send copies of the votes to everyone, not the instance hosting the voter.

    This is a huge win, especially for instances that host a lot of communities like lemmy.world, sh.itjust.works, etc.










  • Good question.

    A GUI will be easier to get into - you can use a gui file browser app to learn the layout of the file system, you can use a GUI text editor to change config files, that sort of thing. It’ll mean you can do a few basic things intuitively which will be less intimidating. So from a maintaining momentum and morale point of view it might be best to have a GUI initially even though you have to learn all the cli stuff eventually anyway and you’ll most likely be running a headless server on real hardware eventually.


  • Self-hosting is a very individual journey - everyone wants different things and finds they own way to meet their own requirements. So there isn’t really one guide that covers everything.

    Anyway, as a general road map:

    1. Create a Virtual Machine on your PC. Install Linux inside the VM.

    2. Play around in the VM to learn Linux basics. When you break the OS you can just wipe the VM and reinstall.

    3. In the VM, try some docker containers until you’re comfortable-ish with docker.

    4. Maybe try Yunohost in the VM. You might find Yunohost saves you a lot of time and hassle.

    5. Get hardware suitable for your goals.

    6. Install Linux, configure networking and docker containers on real hardware.






  • If you’ve ever spent 10 minutes using an AI agent, you’d know that there’s no way to predict how many tokens it’s going to use before you give it a task. It can be $0.20 worth sometimes or $20 other times. Or anything, really.

    It’s only after watching it churn away for a few minutes that you can assume it’s gotten stuck and have the option of pulling the plug before the bill gets run up too high. But you need to watch it like a hawk and you need to be the one paying the bill otherwise you’re not going to care (e.g. workers using AI at work aren’t paying for it, their company is).

    Taken in aggregate across a month, that unpredictability might average out or it might explode.


  • Thanks for your kind words, despite our differences on this.

    I get that people want to show support and encourage each other. There’s a point, though, where it gets indiscriminate and wasteful.

    In my analysis of voting patterns I think it’s pretty clear that this intervention only impacts a tiny number of people and that the quota level is set so that 99.98% of people (or 98% if you ignore the less-engaged users (why, tho?)) will almost never use up their quota.

    You’re in that 0.02% so it feels different for you.

    There are a ton of other ways to support the fediverse. Find interesting content to post, write nice comments, moderate some communities, improve the docs for Lemmy, translate the UI, report a bug in the issue tracker, report spammers, spread the word on mainstream social media, donate money, and so on. Get creative.