This only guarantees your WANip:8100 will map to 192.168.0.113:81, and doesn’t address whether or not dns resolution is correct. I would also be weary of using port numbers on wikipedia’s known ports list, as some ISPs will filter those upstream. The last thing is that your router may not want to hairpin that traffic, so if you’re not coming in from the outside it might not be a valid test.
This is likely correct but the browser’s errors should be telling you what the error(s) is/are.
Lol, I think we might be closer than you think. Lemmy and reddit are both basically unusable in web form on mobile, but Ernest took the time to make the layout of kbin in such a way that it compresses down to a PWA/Mobile layout without becoming a complete clusterfuck, something the mbin maintainers have maintained support for and I think is one of the key distinguishing features of the platform. The way it works feels very similar to the old RIF layout, and as such was everything I wanted from a reddit replacement from day one :)
+1 for the kbin >>mbin pipeline. I like that it still has pwa support since I really don’t need a phone app for a text based forum
I would sort of consider web as the other one, since kbin (and now mbin) were designed to play nice with mobile browsers, I use mbin on my phone via PWA and I’m pretty happy with it, aside from mbin UI issues which I keep kicking around the idea of fixing but have been lazy about it.
https://fedia.io is the ‘big’ mbin server, but they appear to have closed registrations at some point
I’m a big mbin stan, but it’s clearly the inferior software platform right now.
I expect something like this to end up being the solution, but I think we’re far from a consensus in that regard.
Generally isn’t even a factor. Hexbears have some nuclear takes, but they are death on transphobia
I unironically think it would be easier to train users that the report button works now than it would to get automated reporting that was worth a damn implemented.
My solution to this was to put the default download folder on an nvme and then move the torrent to a storage hdd after completion
Happily, the costs (server/hypervisor, domain, static IPs, proper firewall) are ones I already needed to spend for work, so the only tricky part will be finding the time and making the effort. Maybe by then the ux issues with low population instances will be sorted lmao.
Used fedia today, and it looks like they never quite nailed down their 504 problem, so I think I’ll give this one a go for a while.
Most people don’t have a RAID to fall back on either, and I would argue most cars’ donuts or spares haven’t been checked since the car was new so I think it holds up better than you’re giving it credit for lol