andscape

I'm setting up a self-hosted stack with a bunch of services running on a home device. I'm also tunneling all the traffic through a VPS in order to expose the services without exposing my home IP or opening ports on my local network. Currently all my traffic is HTTP, and its path looks like this:

• Caddy proxy on remote VPS (HTTPS, :80 & :443)
• Wireguard tunnel
• Caddy proxy in Docker on homeserver (HTTP, :80)
• app containers in separate isolated subnets, shared with Caddy

I want to set up qBittorrent and other torrent apps, and I want all their traffic to pass through the proxies. Proxying traffic to the WebUI is easy, there's plenty of tutorials; what I'm struggling with is proxying the torrent leeching and seeding traffic, which is the most important part since I live in a country that's not cool with piracy.

Unless I'm misunderstanding, BitTorrent traffic is TCP or UDP, so I'd need Caddy to act as a Layer 4 proxy. There's a community-maintained plugin that should support this. How would I configure it though? Do I need both instances to listen on a new port? Or can I open a new port on the VPS only, and forward traffic to the homeserver Caddy over the same port as the HTTP traffic (:80)? Are there nuances in proxying TCP traffic that I should be aware of?

I'm involved with an org that needs to set up a public wishlist for supplies for a project. The rough requirements are as follows:

• Public webpage with a static URL
• Can be easily edited by non-technical people
• Editing requires authentication
• Avoiding corporate services, especially avoiding tracking of both users and admins
• As cheap as reasonably possible
• As quick to set up as possible

Nice to have:

• Hosted under a custom domain
• Supports users "reserving" items so multiple people don't all supply the same stuff

One option I considered would be running something like wishthis in a VPS under our own domain, but this is kinda expensive, complex, and I don't trust wishthis' auth. A different option could be just having a static page in something like Notion or Github pages, which would be free but relies on corporate services we don't trust.

Is there a middle ground between the two previous options? Or a better solution that fits most of the requirements?

With debate raging in the Fedi about Threads' federation, I was having a discussion with another user about the recently implemented instance blocks. They pointed out that, blocking an instance simply hides their content from your feed but doesn't prevent your posts from being sent to them. Firstly, is this correct? Is this how instance blocks are implemented in Lemmy? If not, has this been discussed before? I couldn't find such a discussion in Github issues...

It seems that many people have concerns about Meta's use of their data, and would like to opt out of sharing their content with Threads. Is there any way to do this in Lemmy right now, or any plan to implement such a feature?

I'm looking for a way to keep track my recurring subscriptions. I just want a nice overview of recurring payments and where they come from, I don't need a solution to actively go and manage the subscriptions for me. Unfortunately my bank, despite being a trendy digital bank, does not have a good built-in tool for this.

There's a plethora of third party services I found for this (Truebill, TrackMySubs, Hiatus, etc.) but they require you to give them unrestricted access to your bank account activity which seems like a privacy nightmare. I've also found some less invasive apps, such as Subby for Android, but they're basically just nice views over manually entered data. The ones I've found also seem to be single-platform only: even if you can sync your data (not always the case) you can then only view it from the app on the same platform.

Do you have a good solution for this? Something that's a middle ground between giving your entire payment history to some random company and a good-looking local-only spreadsheet?

I wrote this post for a friend, I'm sharing it here for anybody it might help. I got asked multiple times how I download cracked music software so I figured it'd be easier to write it down once. It's meant for people with very low technical skills who just want to start torrenting software without major risks, and it includes a bunch of safety tips that are already known in this community.

If you have feedback, let me know and I'll update the post.