SinTan1729
@SinTan1729@programming.dev
- Comment on Cloudfare outage post mortem 2 days ago:
Ah that makes sense. To be fair tho, there’s a lot of unwarranted hate towards Rust so it can be hard to tell.
- Comment on Cloudfare outage post mortem 3 days ago:
I hope you’re joking. If anything, Rust makes error handling easier by returning them as values using the
Resultmonad. As someone else pointed out, they literally usedunwrapin their code, which basically means “panic if this ever returns error”. You don’t do this unless it’s impossible to handle the error inside the program, or if panicking is the behavior you want due to e.g. security reasons.Even as an absolute amateur, whenever I post any Rust to the public, the first thing I do is to get rid of
unwrapas much as possible, unless I intentionally want the application to crash. Even then, I useexpectinstead ofunwrapto have better error logging. This is definitely the work of some underpaid intern. - Comment on Assign privileged port to caddy running with rootless podman 5 weeks ago:
I’m confused. What do you even mean?
- Comment on Assign privileged port to caddy running with rootless podman 5 weeks ago:
It seems that I’d still need to modify
net.ipv4.ip_unprivileged_port_start=80in sysctl, which I don’t want to do. If I do it, the socket isn’t even strictly necessary. - Comment on Assign privileged port to caddy running with rootless podman 5 weeks ago:
This is interesting. I need to figure out how it works for
podmanand it’ll be the perfect setup. - Comment on Assign privileged port to caddy running with rootless podman 5 weeks ago:
I think it’s the masquerade that’s causing problems for me. I have to keep it enabled since I’m running a
tailscaleexit node. But maybe I can selectively disable it here. - Comment on Assign privileged port to caddy running with rootless podman 5 weeks ago:
I mentioned in the post that it seems to make the client IP opaque to
caddy. - Submitted 5 weeks ago to selfhosted@lemmy.world | 16 comments
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
বাঙালী প্রোগ্রামার খুব বেশি দেখি না। শুনে ভালো লাগলো।
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
I’m happy that you like it. Any kind of analytics or logging is decidedly against my stated policy for this project, so I won’t be adding it. But I understand that some might need it, and in that case, one should look at more comprehensive solutions like YOURLS.
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
It’s just a way to advertise, I think. I’ve found myself putting more trust in projects written in Rust or Go, than say, JavaScript.
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
Hmm, so that might be out of scope here. But I can try to do some kind of 2FA, shouldn’t be much of an issue, really. It’s just that I never thought a link shortener needed that kind of protection since the links will be shared anyway.
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
I don’t understand much about OIDC either. But I’ll keep it in mind. Thanks.
And thanks for your concern. I’m doing fine for the time being.
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
Unnecessary to me, I guess.
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
Thank you for the kind words.
Won’t lie, the main reason that I stuck to a vanilla frontend approach is because I didn’t know what else to do. I’ve never been a frontend dev, and never wish to be either. So I looked at an older project, and started by trying to replicate it. In hindsight, it was probably a good decision. The backend is more intentional though, and I do try to keep things simple and neat.
- Comment on Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 2 months ago:
I’m already aware of a few small UI bugs. There were quite a few changes in the frontend, so I kind of expect these. Please let me know if you see anything weird. You can comment here, or open a bug report. I expect to do a patch release by tomorrow.
- Chhoto URL v6.3.0 is out now: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust.github.com ↗Submitted 2 months ago to selfhosted@lemmy.world | 36 comments
- Comment on GitHub - SinTan1729/chhoto-url: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 4 months ago:
It was just a matter of setting the correct user. In most cases,
user: 1000:1000should fix it. - Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
Hey, that looks awesome. I’ll try it out when I get back from work.
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
That’s a pretty good idea, actually. I’ll try that out. Thanks.
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
I took a look. It’s very close to what I want, but it still doesn’t support uploads in shared directories. It seems to be a pretty highly requested feature though. So maybe it’ll happen at some point.
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
I prefer not to have such a large piece of software running for no reason. It might seem silly, but I hate using resources for no reason. I’ll rather have 5 lightweight apps running instead of a huge one, of which I’ll only use a few parts.
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
I’m strictly against Nextcloud or something similar. I prefer to run a bunch of lightweight apps, rather than one big one.
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
I don’t care too much about security, since I’ll delete everything in a few days after copying them to my gallery. Then, I usually share a link with them to an album on my PhotoPrism instance. So, per share password is fine by me.
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
Yeah, but that’s already possible with my current setup using Fileshelter. I’d like them to be able to upload as well.
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
This looks pretty promising. Do you know if it’s possible to add per-share passwords, so that I don’t need everyone to open an account?
- Comment on Suggestion request: Self-hosted app for shared directories like google drive 6 months ago:
Yeah, it’s a bit too much I think.
- Submitted 6 months ago to selfhosted@lemmy.world | 42 comments
- Comment on GitHub - SinTan1729/chhoto-url: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 7 months ago:
On further testing, this does actually work. You may set both
read_only: true, andcap_drop: alland it will work as long as you have a named volume. I had it mount a database file from the host system for my test config, which is why I was getting the errors. I don’t know how to make that work though i.e. when the db is bind mounted from the host system. Setting the mount:rwdoesn’t seem to fix it. - Comment on GitHub - SinTan1729/chhoto-url: A simple, blazingly fast, selfhosted URL shortener with no unnecessary features; written in Rust. 7 months ago:
That’s great to know. Btw, you don’t actually need to specify the url path for it to work. That’s just for convenience of copying the link from the UI. It’ll just work as long as the server is reachable at that address.