KIM_JONG_JUICEBOX

joined 1 year ago
[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago (1 children)

I’m confused. Is it 650 rounds per minute or 100 rounds per minute?

[–] KIM_JONG_JUICEBOX@lemmy.ml 2 points 1 year ago

It’s like a roast. His friends give him sick burns all evening one night a year.

[–] KIM_JONG_JUICEBOX@lemmy.ml 10 points 1 year ago (1 children)
[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago

Pepsi makes the dogs gay.

[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago

Deserts of Siberia

[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago

Or you set a flag that says something like “incomplete image” and then only once user completes whatever operation by hitting “submit” do you then set it to complete.

And maybe while an image is not yet complete, only the uploading user can view the image.

[–] KIM_JONG_JUICEBOX@lemmy.ml 2 points 1 year ago

Course it doesn’t stop the CSAM spammers ☹️

[–] KIM_JONG_JUICEBOX@lemmy.ml 10 points 1 year ago

You’ve got to be fucking kidding me.

[–] KIM_JONG_JUICEBOX@lemmy.ml 2 points 1 year ago (1 children)

Good to see this has made it over to the fediverse.

[–] KIM_JONG_JUICEBOX@lemmy.ml 2 points 1 year ago

Or on the seat with the window down.

[–] KIM_JONG_JUICEBOX@lemmy.ml 4 points 1 year ago (1 children)

I graduated in 1998 and it’s in my vermicelli.

[–] KIM_JONG_JUICEBOX@lemmy.ml 1 points 1 year ago

This guy maybe onions.

 

I'm trying this on Ubuntu 22.04 Rust's cargo install seems to keep creating permission problems between what I have to install, compile and what gets published in the cargo "registry", which causes issues at runtime when I run as lemmy:lemmy through systemctl.

If I run: cargo install lemmy_server --target-dir /usr/bin/ --locked --features embed-pictrs as a non-root user, I get permission denied issues with /usr/bin/.future-incompat-report.json and /usr/bin/release

If I run the build as a root user, and then manually copy the binaries to /usr/bin and chmod them to lemmy:lemmy, then try to run as lemmy:lemmy, it appears the binary is trying to access some "registry" files in /root/.cargo/registry (for which of course it does not have permissions.)

How do I fix this?

view more: next ›