ArchiveBox is great.

I’m big into retro computing and general old electronics shit, and I archive everything I come across that’s useful.

I just assume anything and everything on some old dude’s blog about a 30 year old whatever is subject to vanishing at any moment, and if it was useful once, it’ll be useful again later probably so fuck it, make a copy of everything.

Not like storage is expensive, anyway.

It’s viable, but when you’re buying a DAS for the drives, figure out what the USB chipset is and make sure it’s not a flaky piece of crap.

Things have gotten better, but some random manufacturers are still using trash bridge chips and you’ll be in for a bad time. (By which I mean your drives will vanish in the middle of a write, and corrupt themselves.)

Okay so you’re able to access it via the IP it’s hosted on, but NOT via the domain name in the tunnel?

Is the working IP a public or private one?

My $5 is that you don’t have the tunnel configured properly and that’s why you’re having issues, but maybe not.

Also, what specifically did you put in the config file? Usually they’re not asking for an IP, but the FQDN of the site.

Am I missing something, or is this just the argo tunnel thing Cloudflare has offered for quite a while?

Are you using Cloudflare as DNS, proxy, or via their argo tunnels? (I know you said tunnel, but then mention accessing via IP address, so I’m not entirely sure what you’ve done.)

Kinda changes what you should be looking at.

10000% this.

Tell me what it does, and SHOW me what it does.

Because guessing what the hell your thing looks like and behaves like is going to get me to bounce pretty much immediately because you’ve now made it where I have to figure out how to deploy your shit if I want to know. And, uh, generally, if you have no screenshots, you have no good documentation and thus it’s going to suuuuck.

It’s because of updates and who owns the support.

The postgres project makes the postgres container, the pict-rs project makes the pict-rs container, and so on.

When you make a monolithic container you’re now responsible for keeping your shit and everyone else’s updated, patched, and secured.

I don’t blame any dev for not wanting to own all that mess, and thus, you end up with seperate containers for each service.

Head to the lemmy github and subscribe to the releases email and you’ll get one when a new version is out.

(And, unlike SOME projects I’m subbed to, they don’t do anything that generates a ton of spam, so it really is just one-email-per-release.)

I’d probably go with getting the ISP equipment into the dumbest mode possible, and putting your own router in it’s place, so option #2?

I know nothing about eero stuff, but can you maybe also put it into a mode that has it doing wifi-only, and no routing/bridging/whatever?

Then you can just leave the ISP router in place, and just use them for wifi (and probably turn off the wifi on the ISP router, while you’re in there).

I’ve become a fan of staying one version behind for a month or two, unless there’s a security issue that is involved in which case I’ll patch.

I like it when someone who isn’t me finds out the catastrophic breaking issues and has to do the cleanup, and I’ll wait for the fixed version. :P

Then the correct answer is ‘the one you won’t screw up’, honestly.

I’m a KISS proponent with security for most things, and uh, the more complicated it gets the more likely you are to either screw up unintentionally, or get annoyed at it, and do something dumb on purpose, even though you totally were going to fix it later.

Pick the one that makes sense, is easy for you to deploy and maintain, and won’t end up being so much of a hinderance you start making edge-case exceptions because those are the things that will 100% bite you in the ass later.

Seen so many people turn off a firewall or enable port forwarding or set a weak password or change permissions to something too permissive and just end up getting owned that have otherwise sane, if maybe over-complicated, security designs and do actually know what they’re doing, but just getting burned by wandering off from standards because what they implemented originally ends up being a pain to deal with in day-to-day use.

So yeah, figure out your concerns, figure out what you’re willing to tolerate in terms of inconvenience and maintenance, and then make sure you don’t ever deviate from there without stopping and taking a good look at what you’re doing, what could happen if you do it, and coming up with a worst-case scenario first.

What’s your concern here?

Like who are you envisioning trying to hack you, and why?

Because frankly, properly configured and permissioned (that is, stop using root for everything you run) container isolation is probably good enough for anything that’s not a nation state (barring some sort of issue with your container platform and it having an escape), and if it is a nation state you’re fucked anyways.

But more to your direct question: I actually use dns scopes and nginx acls to seperate public from private. I have a *.public and a *.private cname which points to either my external or internal IP, and ACLs in the nginx site configuration to scope where access is allowed.

You can’t access a *.private host outside the network, but can access either from inside it, and so (again, barring nginx having an oopsie somewhere) it’s reasonably secure and not accessible, and leaves a very clear set of logs (and I’m pulling those logs in and parsing them for anything suspicious and doing automated alerting if I find anything I would not otherwise expect) so I’m happy enough with the level of security that this is, when paired with the services built-in authentication options.

When you say you ‘can’t access local devices’ is it just via the browser, or can you also not ping/telnet/ssh/whatever?

Are content creators we already know expected to start their own servers? Or will there be a general mega instance for everyone to post to.

Honestly - both?

Good examples are going to be Floatplane and Nebula for the single-content-creator platform and the group of creators platforms.

There’s no real reason you can’t build a platform and require someone to pay you to have access, and it seems to have been successful for both groups.

Video hosting is expensive, but it 's not prohibitive and a group of creators could certainly come up with a useful platform and self-host it and still be profitable.

Now, the question is, of course, if peertube is the right choice for that and if it offers anything they’d need, but that’s a different discussion.

[Edit] I’ll have to see if I can find the video.

I can save you the time there, at least: https://youtu.be/hiwaxlttWow

Everyone loves to hate on Cloudflare, but uh, duh, of course a US company will comply with a request under US law that they have to comply with?

If you don’t want your shit DMCAed, don’t use anything based in the US to provide it.

Go host somewhere that doesn’t have smiliar laws and won’t comply with foreign requests.

There was a recent video from everyone’s favorite youtube Canadians that tested how many USB devices you can jam onto a single controller.

The takeaway they had was that modern AMD doesn’t seem to give a shit and will actually let you exceed the spec until it all crashes and dies, and Intel restricts it to where it’s guaranteed to work.

Different design philosophies, but as long as ‘might explode and die for no clear reason at some point once you have enough stuff connected’ is an acceptable outcome, AMD is the way to go.

I mean not the first time they’ve sued over cheats, and they very much took a sweeping victory last time.

I’d expect the same DMCA circumvention provision along with the always fun “Well, literally everything you did is also a CFAA violation so maybe you want to settle now before we try to get you extradited to the US on federal felony charges” threat would result in pretty much the same outcome here.

Looks like others have provided MOST of the answers.

Radarr/sonarr do the heavy lifting making symlinks where symlinks are required, but there’s still the occasional bit of manual downloading.

I also have a script that’ll check for broken symlinks like once a week and notify me of them and I’ll go through and clean them up occasionally, but that’s not super common and only happens if I’m manually removing content I made manual symlinks for, since I’ll just let radarr/sonarr deal with it otherwise.

(The full stack is jellyseerr -> radarr/sonarr -> qbittorrent/sabnzb -> links for jellyfin)

I just select the files I want from the bigger torrents, and then proceed to not touch it ever again, unless I want to add more stuff to the downloaded files.

I also don’t move things around - I’m on Linux so all the torrents live in one place with symlinks pointing to where I need/want the data to be as I figured out yeeeears ago that trying to manage a couple thousand active torrents while having the data spread everywhere is a quick trip to migrane town.