• 4 Posts
  • 187 Comments
Joined 5 years ago
cake
Cake day: May 31st, 2020

help-circle

  • I think, people who say that believe that we’re close to actually-intelligent AI (or artificial general intelligence, AGI). And when we get there, it’s possible that we might suddenly be able to automate lots of complex tasks, possibly even shove it onto robots and have it take on physical labor and things like that.

    It’s the wet dream of capitalists, because they don’t need to employ anyone anymore. And I guess, folks are also afraid that such AI could be used for war.






  • Ephera@lemmy.mltoAsklemmy@lemmy.mlWhat made you join Lemmy?
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 month ago

    I quit Reddit many years ago, because I noticed the toxic culture was fucking with my mental health. Then I was on Mastodon for a few years. Lemmy started to exist in that timeframe and the premise sounded good, so I joined pretty early on, when there were only a handful of posts every week or so. But yeah, these days Mastodon is what I check only occasionally and this place has taken over, as I do like the format a lot more.



  • Oh yeah, I didn’t mean to check in the SQLite database file, just the configuration file and the docker-compose.yml.
    Git cannot diff binary files, so every version of your SQLite database would be checked into the history in full and all of them would get downloaded when you do a git clone. Theoretically, you could get around this with Git LFS, but it just doesn’t make a whole lot of sense to put the SQLite database into Git. You don’t iterate on the database in a way that would warrant commits. In particular, you wouldn’t want to roll back the database, if you’re rolling back something in your configuration file. I also imagine the SQLite database would contain usernames and passwords, so you definitely don’t want that in a potentially public Git repo.

    So, yeah, you want a separate backup mechanism for the SQLite database. You could put the way this backup tool is rolled out into the docker-compose.yml, but yeah, that’s somewhat more advanced than this Luanti deployment.





  • I think, what @muntedcrocodile@lemm.ee means with “integrated”, is that they’re wholly part of the app and don’t depend on Googley software being installed into the OS. And to my knowledge, that is not the case.

    So, there’s a client library which you include into your app code. That talks with the Google Play Services on your phone. And that then talks with some Google server.
    I assume, that client library itself is already proprietary and that’s why the F-Droid team strictly needs to have it removed. Ideally, it would be replaced by an open-source alternative, but the code could also be modified to not include this library and you’d ‘only’ lose e.g. push notifications. Depending on how the app is implemented, you might not get notifications at all then, though.

    But they don’t go lightly about modifying the code of an app. If the developer doesn’t want this, they can pull all kinds of shenanigans to make this more difficult or impossible for the F-Droid team…



  • As a vegetarian, I wouldn’t care much for it. I feel like the plant-based alternatives have got everything covered I could want from meat (and more, if you look beyond Western cuisine). And then I just feel like it’s hard to compete with them in terms of sustainability, efficiency, price etc… In particular, I also really cannot be fucked to put more perishable things into my fridge. I had bought these meatball-like things for Christmas, but didn’t eat the whole load on the first go, so had to cram them in a few days later. Meanwhile my lentils, beans, TVP, peas, nuts etc. just sit there for months, not needing any of my attention.