• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2025

help-circle
  • They do have a professional offering, but it’s offered in a deeply unprofessional way. Selling to businesses means you need both the technical offering, but also the correct commercial offering. That means presenting yourself in a way that attracts the attention of the decision makers in those businesses, and telling them a compelling story of why your product is the best fit to solce their problem. A .lol domain and a cartoon catgirl doesn’t do that.

    I’d suggest that, for the cost of an extra domain name, and a boring logo, they could probably significantly increase their subscriber base. There’s nothing stopping them keeping the current mascot on the current site at the same time.

    You call it stupid to prejudge a project in such a way, but businesses need a product to buy, not a project.


  • It is a big problem with a number of opensource projects that could get wider adoption and support, especially from businesses, but seem to, almost deliberately, work against that with their naming and/or branding.

    Anubis is a perfect example. In this case the name is ok, and by all means have a cutsey mascot for the basic offering, but if they want businesses to subscribe they need a professional offering. That should be on a separate domain, styled to attract the decision makers in their target market, and that includes having a .com or similar domain name and a more serious logo. Do that, and it becomes a serious contender in the market, rather than a technically good but excessively kooky option.


  • notabot@piefed.socialtolinuxmemes@lemmy.world•Of course
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    6 days ago

    Yes, personally I don’t have a huge problem if someone uses an LLM, that’s been trained only on opensource code, on a project, but that someone has to put their name to the code, documentation, tests or anything elsr produced, and take full responsibility for it. As in, they suffer the same consequences if it causes an issue as if they’d hand coded it, with particular attention paid to whether the result is maintainable, and whether it breaches any licences.

    Of course, most LLMs have, by now, injested a lot of proprietary code that people have mindlessly sent in queries, rendering all of their output tainted.


  • notabot@piefed.socialtolinuxmemes@lemmy.world•Of course
    link
    fedilink
    English
    arrow-up
    15
    ·
    6 days ago

    It’s not really stupid. Things that are unusual are more noticeable, and garner more comment. We’ve grown used to devs tirelessly doing what they do, to the point most people don’t think about where their software comes from, but a machine sort of doing it (poorly, so very poorly) is novel, so people talk about it.

    Currently, software mostly working as it should is the norm, so people don’t talk about it much. When the wave of slopcoded disasters starts to grow, people will talk about it, because software is suddenly not working as it should.



  • Depending on exactly what features you actually need in term of things like commenting, you might want to look into a static site generator. Something like hugo woud probably do what you need in terms of translating the markdown into a blog. It has the advantage that you can them host the pages on a normal web server, rather than running a blogging platform, giving you a much lighter weight server footprint, and a much smaller attack surface too.


  • I’ve found Hetzner to be reasonable for VPSs and even bare metal servers, especially if you keep an eye on their auctions.

    Whether you’re hosting it all at home, all on a remote server, or some combination of the two, it’s worth taking the time to first learn some form of automation tooling, so that your setup is reproducible and you know exactly how everything is set up. From the first time you have to rebuild everything due to a hardware failure trashing your server, or a careless rm -rf, you’ll be glad of it.

    Ansible is a good place to start as it’s pretty straighforward to get going, and your playbook can grow with your requirements. If you’re using a lot of containers, make sure you understand docker, and maybe consider Kubenetes, especially if you want to split your workload across servers.


  • I find that a dedicated RSS reader is a much better experience, as, especially when you’ve got a lot if feeds, organising them and keeping track of what you’ve read becomes quite important. If you take your eye off of a chat based system, you’re going to have so many unread messages it’ll be hard to keep up.


  • Flock has done its part in soaking up public anger at pervasive surveillance, and can now be left to fail. Companies like Axon will step in to the breach, be slightly less obviously awful, and receive much less public pushback.

    This isn’t going away until the very governments that benefit from it pass laws against it. For there to be any chance of that happening there has to be even greater public pushback.





  • Seeing high cache and buffer numbers is usually a good sign, as it means the system is making full use of the memory you have. It’ll automatically deallocate it if something actually needs the memory, but until then it’s using it to store data you might need.

    Swap’s a funny one, and whilst you can tune it to an astonishing degree, the decisions the kernel makes aren’t always what you’d want. With this little actual memory usage, compared to the installed RAM, you might be able to run without swap at all, unless you want something like hibernate. If you want to test that, you can run (as root) swapoff -a, which should disable all swap devices, pushing needed pages back in to RAM, but only until you reboot. If it’s stable, you can consider removing the swap partition(s) later.