
InEnduringGrowStrong
@InEnduringGrowStrong@sh.itjust.works
- Comment on SJW - Known issue loading page 2+ 1 week ago:
I’m honestly not sure, but I just did the thing again just in case it helps you out.
Let me know. - Comment on Should I get a b*mbulab printer? + More newbie questions 1 week ago:
If anything is terminally online it’s the Bambu itself lmao
- Comment on SJW - Known issue loading page 2+ 2 weeks ago:
The web UI has pagination by default.
Not sure about Jerboa, I haven’t used it in a while - Comment on SJW - Known issue loading page 2+ 2 weeks ago:
The problem might very well be the same.
Probably, if you browse lemmy.world without being logged in, it’ll work fine, at least that how it was with us.
I’ll reach out to them and point them here. - Comment on SJW - Known issue loading page 2+ 2 weeks ago:
Is this an issue you’re having with your lemmy.world account? And if so, on which feed and which sort type?
- Comment on SJW - Known issue loading page 2+ 2 weeks ago:
Good question. I don’t design these things.
I’m not even an expert on databases.
The way I understand it is that the 50 is a floor.
Makes sense, you probably don’t want to vacuum too often, which might compete with other locked slots and have overall adverse effects.
The work done while vacuuming is proportional to the table size, so vacuuming a small table is small work, while vacuuming a bigger table is more work.
I guess that’s why it’s using a %.Thing is there’s no upper cap.
Or there wasn’t until postgres 18+, and even then it’s likely way above what we’d run into.
I imagine that it can make sense for many tables and the default might be conservative as to avoid the drawbacks of over vacuuming.Even an upper cap would only shorten the amount of time before it fixes itself.
In our case, the issue was mostly due to the database upgrade which basically resets the counters towards the next run.I’ll probably just add a daily job that takes care of this more gracefully without being too agressive.
Regardless, this should probably be added to the upgrade process. - Comment on SJW - Known issue loading page 2+ 2 weeks ago:
Glad to hear, as it was essentially unusable before.
I’ve updated the post with more info. - Submitted 2 weeks ago to main@sh.itjust.works | 41 comments
- Comment on Is sh.itjust.brokenagain? 2 weeks ago:
If anyone can test again loading page 2+
- Comment on What is your self hosted power draw? 5 weeks ago:
I mean, my phone charges at 60W. Granted, it’s not charging 24/7 but 50W is pretty good indeed.
- Comment on Anyone else avoiding gaming consoles past 8th gen? 1 month ago:
Honestly, I’m avoiding most online games these days.
Anything competitive tends to have toxic communities, but really I just like being able to pause whenever. - Comment on I rebuilt the 1996 internet the way you remember it, not the way it was 1 month ago:
And somehow notepad got worse.
- Comment on AI bot hacking/scraping Home Assistant 2 months ago:
and let’s hope that the login page doesn’t have any vulnerabilities…
Home assistant also supports mTLS.
home assistant is something you’d likely ever want to allow from a handful of trusted devices, so deploying a client certificate on them can make sense.
This way a non-onboarded device doesn’t even get to the html part, it’s denied upstream by a reverse proxy before HA is involved. - Comment on What are good (web-)proxy servers? or Using a web-proxy instead of VPN for gatekeeping 2 months ago:
I’m a big fan of mutual TLS, which I just do in nginx reverse proxy.
Client certs get installed on trusted devices and then it’s mostly seamless.
Not every app will support it, but I use Firefox as a fallback for stuff that doesn’t, or my VPN.
TBH, I’m just happy homeassistant supports it as that’s the one thing I’d rather be as seamless as possible.
Other things I don’t mind having to connect a VPN for, like jellyfin, which I don’t currently share with others.
For nextcloud I’m currently not running mTLS as it wasn’t supported back then and I had to share some links with some people where I wouldn’t deal with certs. I think mTLS support has been merged since, so if you just use it for devices under your control, or might be viable - Comment on Help wanted undextrusion and stuck filament 2 months ago:
Not necessarily since the initial layers don’t have the space to be squished properly, subsequent layers can show the same problem, except they’re too close to the previous layer instead of the bed itself.
That said, the picture didn’t load before but now it does.
Qith the picture, this looks kinda like wet filament to me where it’ll kinda bubble here and there.
I’ve also spent way too much time hunting down underextrusion what was ultimately just the filament that had a weird undersized diameter like 1.6mm.
Diameter that’s off but consistent through the roll can be compensated for in the slicer, inconsistent diameter not so much. - Comment on My domain is accessible from external networks but not from my internal network. Might anyone know why? 2 months ago:
All good answers so far.
Basically your internet gateway doesn’t support what’s called NAT hairpin, also called NAT loopback.The DNS solution is better anyway, and that particular setup is called split-horizon DNS, which basically just means your internal DNS requests get different results than ones from outside your network.
- Comment on Help wanted undextrusion and stuck filament 2 months ago:
Nozzle might also just be too close to the bed.
Mine did a kind of of “tock” sound when it struggled to extrude.