• 0 Posts
  • 87 Comments
Joined 6 years ago
cake
Cake day: January 21st, 2021

help-circle

  • Honestly AI has been used for moderation for decades. The newer models will be quite effective. It could be very useful for limiting lower effort spam. Sure dedicated spammers will figure it out and get by it but as the models get better that will get harder.

    Of course like every use of probabilistic technology like AI it should still go to human review. We shouldn’t be shadowbanning people because computer said no. But holding suspicious posts in a review queue for the moderators seems quite reasonable (much like they already do with their current systems).

    Honestly this sounds more like an investor update showing how innovative we are using modern technology and how it is going to really improve the platform and stonks will go up up up than any meaningful change to their current moderation systems.


  • I also used to read a lot as a kid then stopped for a long while. I have gotten back into it by reading before bed. I try to get to bed at least 30min early on most days—sometimes much earlier if I am having a lazy day or otherwise feeling like I don’t want to stay up—then I get a bunch of reading before bed. As a bonus reading makes me sleepy so I always nod right off when I put the book down (or sometimes have to put the book down because I am falling asleep and can’t keep my eyes open) I’ve managed to finish a good number of books already this year.

    But I think the moral of the story is just find some time that works for you, reserve a bit of time in your day and try to make a bit of a habit out of it.









  • declaring multiple variables is less error-prone than in C. In C, the following declares x to be a pointer, but (surprisingly at first!) y to be a normal integer:

    int* x, y;
    

    Whereas the equivalent in Go does what you’d expect, declaring both to be pointers:

    var x, y *int
    

    I don’t think this is a related at all. C could have easily decided that the definition makes both x and y pointers. They just decided not to so that you can declare more variables on one line by being able to do int x, *y, **z, .... It is more flexible.

    Similarly that Go line could have been parsed like var x, (y*) int if they wanted to. They just made a different choice.


  • I’ve definitely ran into the situation where I fucked something up half-way though installing a new distro, then had to wipe it to go back to an old distro so that I could access the internet and find out what I did wrong so that I could start from scratch.

    I hate doing debugging on my phone, but man sometimes is it better than the alternative.





  • Generally speaking it will be fine. SSH will also refuse keys with open permissions so you would notice if it was wide-open to other users of the device.

    But you know if you are running random code or AI harnesses as that user it can be at risk. Or if you copy around the key all over the place it is more likely to leak. But generally speaking you are secure by default, just don’t do something dumb with the key and you’ll have no problems.


  • It sounds pretty reasonable. As long as you keep SSH patched and keep the key safe it should be quite locked down. Do double-check that password login isn’t allowed (or that all users have a very strong password).

    One non-security note is be careful with rsync backup. Generally rsync isn’t considered a backup as any mistakes made in the source will be propagated to the “backup” on next sync. Although there are ways to use rsync to take good backups (like copying to a new directory for each backup).



  • kevincox@lemmy.mltoSelfhosted@lemmy.worldDawarich 1.9.1
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    I built Chibichange to have a way to conveniently deliver changelogs to Dawarich users

    Have you considered just posting a changelog to your blog? That would be much more convenient than every app I run pinging me in its own way by phoning home to its server.


  • Yes, on one hand every commit to nixpkgs needs review (to some degree) on the other hand there are far too many committers to nixpkgs.

    There are also gaps such as the bots to auto-merge packages with maintainer approval, so a simple attack looks like this:

    1. Submit a package with you as a maintainer.
    2. Create a new GitHub account and send a malicious update to that package.
    3. Use a bot to merge with maintainer approval.

    So nixpkgs is better than the AUR, but it isn’t great and unlike Arch has no separate official repos.