mojolobo

joined 3 weeks ago
[–] mojolobo@lemmy.jrvs.cc 22 points 3 weeks ago (1 children)

Meditation/mindfulness/breathing exercises

[–] mojolobo@lemmy.jrvs.cc 11 points 3 weeks ago* (last edited 3 weeks ago)

My primary use of AI is for programming and debugging. It's a great way to get boilerplate code blocks, bootstrap scripts, one-liner shell commands, creating regular expressions etc. More often than not, I've also learned new things because it ends up using something new that I didn't know about, or approaches I didn't know were possible.

I also find it's a good tool to learn about new things or topics. It's very flexible in giving you a high level summary, and then digging deeper into the specifics of something that might interest you. Summarizing articles, and long posts is also helpful.

Of course, it's not always accurate, and it doesn't always work. But for me, it works more often than not and I find that valuable.

Like every technology, it will follow the Gartner Hype Cycle. We are definitely in the times of "everything-AI" or AI for everything - but I'm sure things will calm down and people will find it valuable for a number of specific things.

[–] mojolobo@lemmy.jrvs.cc 4 points 3 weeks ago

I just setup my own instance a few days ago, if it interests you, do give it a shot!

IIRC reading about it, all data for posts is set to be deleted automatically on a schedule. The catch is that schedule is every 6 months, and it is not configurable currently. From what I read, textual posts of lemmy doesn't consume that much, many reported anywhere from 1-10 GB of data over 6 months - ofcourse it all depends on what kinds of communities are subscribed to your instance.

Not sure if you can restrict image sizes or numbers - atleast not through the admin UI, maybe it's possible through config. You can set global rate limit on image uploads though to not go too crazy.

You can set it so only admins can create communities, or admin would have to approve new communities, or free for all.

If you already have a server, try it out. It shouldn't be tricky, particularly if you're familiar with docker.

[–] mojolobo@lemmy.jrvs.cc 2 points 3 weeks ago

I would second LET. They usually have a lot of good offers around Black Friday, you can get a pretty decent VPS for like $10-20 / year.

You can keep an eye out for that, and see if this is really what you want to get into: https://lowendtalk.com/categories/offers

It is like a marketplace, so make sure to check reviews of the host provider before buying - which you can find on the same site.

[–] mojolobo@lemmy.jrvs.cc 51 points 3 weeks ago (9 children)

If you have signed up on dubious websites with questionable privacy policy, many of them legally sell this data to "data brokers" who then sell it to anyone willing to pay. This happens more than you'd think, for example in 2019 it was reported California DMV makes $50 million a year selling users information. https://www.caranddriver.com/features/a32035408/dmv-selling-driver-data/

One neat trick is to signup for services with an email like name+website@domain.com, that way if you ever get spam you'll know where you have been compromised.

[–] mojolobo@lemmy.jrvs.cc 1 points 3 weeks ago

This was it, thank you so much!

 

Hello,

I'm new to setting up a lemmy instance. Followed the guide using docker compose. I have everything running for the most part, but I'm noticing this error in the logs.

lemmy-pictrs    | 2024-10-28T01:58:48.048727Z  WARN pict_rs::tmp_file: TmpFolder - Blocking remove of directory "/tmp/pict-rs/0192d0d8-e3ec-7dcd-be4e-d1ef1cc09fca/0192d0d8-e3ed-71d6-a5dc-5dc150e868f1"
lemmy-pictrs    | 2024-10-28T01:58:48.048891Z  WARN pict_rs::tmp_file: TmpDir - Blocking remove of "/tmp/pict-rs/0192d0d8-e3ec-7dcd-be4e-d1ef1cc09fca"
lemmy-pictrs    | Error:
lemmy-pictrs    |    0: Error in database
lemmy-pictrs    |    1: IO error: Permission denied (os error 13)
lemmy-pictrs    |
lemmy-pictrs    | Location:
lemmy-pictrs    |    src/repo/sled.rs:130
lemmy-pictrs    |
lemmy-pictrs    |   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
lemmy-pictrs    |
lemmy-pictrs    |    0: pict_rs::repo::sled::build with path="/mnt/sled-repo" cache_capacity=67108864 export_path="/mnt/exports"
lemmy-pictrs    |       at src/repo/sled.rs:124
lemmy-pictrs    |    1: pict_rs::repo::open
lemmy-pictrs    |       at src/repo.rs:889
lemmy-pictrs    |
lemmy-pictrs    |   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
lemmy-pictrs    |   <empty backtrace>

Any help on how to go about debugging this would be helpful! As I understand the pictrs container isn't able to access the volume for postgres. But not sure why.

[–] mojolobo@lemmy.jrvs.cc 20 points 3 weeks ago (4 children)

After trying a bunch, I'm using Obsidian + now. Good thing with Obsidian is your notes are ultimately a bunch of plaintext files, so you can do whatever you want with them, and it comes with clients for most platforms.

Another option is Trilium, it is pretty powerful, and has a webapp so as long as you can access a browser, you'll be able to access your notes. https://github.com/zadam/trilium