I’m running the following SQL, although I’m not actually sure it’s as necessary since 0.18.3. It doesn’t delete any post history or anything.
DELETE FROM activity WHERE published < NOW() - INTERVAL '1 day';
DevOps dude, self-hoster, space nerd.
I’m running the following SQL, although I’m not actually sure it’s as necessary since 0.18.3. It doesn’t delete any post history or anything.
DELETE FROM activity WHERE published < NOW() - INTERVAL '1 day';
I think the Kindle Scribe has a lit screen, if e-ink is what you’re after.
I love my ReMarkable 2! I use it everyday for handwritten notes and for e-reading. It doesn’t support the major stores, but it loads epubs just fine. I’m also self-hosting rmfakecloud cause I’m that kind of nerd. You mentioned night use, so definitely be aware it does not have any lighting built in.
Hugo calls these sorts of things “frontends” and has a list here: https://gohugo.io/tools/frontends/
I haven’t had great luck with any of them personally.
It’s free as in “paying zero money”. It’s still distributed via leanpub. Requires an email address to get to the download page, it doesn’t verify it in any way other than being a valid email format. Links are to DRM-free epub and PDF.
Lemmy 0.18 has resolved most of these for me. As the big instances update, hopefully this gets more stable for you!
Just checked my own Lemmy postgres database, it’s a 12 round Bcrypt 2b hash.
On one hand, this is super cool, but on the other, it gives orcas and robots the chance to team up, and I’m not here for that.
And then you’ll need to convince every instance admin to swap to this fork.
I think the question about “being on Beehaw” is because you’ve been commenting on a post in a Beehaw community.
This update, specifically how funding is happening, helped me understand some of the reasoning behind the narrow focus of the Lemmy developers. I appreciate them foregoing their regular paychecks to work on stability. Hopefully things settle down soon to the point that the extra eyes and hands on the project are more helpful than they are distracting.
There’s no function in lemmy to track reasons in the admin interface, it’s a text box where you pass in a list of blocked instances. The Beehaw admins may maintain a list separately.
bit off more than they could chew
By starting a Lemmy instance a year and a half before Rexxit? I never saw them claim to want to be the next Reddit. The Fediverse had an influx of users and Lemmy doesn’t currently have the mod or admin tools to deal with that situation gracefully. My understanding is that most of the bad actors were external to Beehaw.
They didn’t bite off anything, shit was being shoved into their mouth so they closed it.
Personally, I’m using my very own Lemmy instance so that I can choose who I federate with (including Beehaw). I totally understand why some folks might want to have their home instance elsewhere, and it’s cool that federation gives us that ability.
This wasn’t the impression I got from the Beehaw admins. I believe they felt that blocking lemmy.world users from Beehaw but still being able to have Beehaw users interact with lemmy.world would have been better than full defederation, but I don’t think that was the ideal solution either. Something like an approval process for an external user to interact with Beehaw communities would be preferable.
Also, Beehaw could go fully private today if they wanted to, that definitely doesn’t seem to be their intention.
Couple questions:
I’d start with traceroute and see how far your IPv6 traffic gets before it fails. It could very well be some peering or routing issue between some of the ISPs in between you and wherever that IPv6 address lives. If this ends up identifying where the traffic dies, a lot of the tier 1 ISPs have BGP looking glass servers so you can get an idea of what they know about that subnet.
Oh interesting, it looks like PWA notifications were added in iOS 16.4, I’m not on that yet. So maybe it is a lemmy issue.
I wish notifications worked with the PWA. I’m guessing that’s an Apple restriction 😞
I believe the activity table in Postgres is retained for 6 months (although I’m purging mine daily) and the pict-rs cache is 168 hours (1 week).
You like deploying infrastructure, probably in a cloud environment, but you don’t want to push a bunch of buttons in their web interface, so you use Terraform to declaratively define the things you want, and it goes and builds them for you. Super useful for when you need to build resources often, to detect and correct config drift, and get started down the path of Infrastructure as Code.