To be, like, super and needlessly pedantic, lol, Linus looks like her since she’s older.

No, she’s much wittier than I am. Though I did try to write it in her style.

Probably the easiest is to use a different UI.

Both Photon (https://photon.lemmy.world/) and Tesseract (https://t.lemmy.world/) will let you directly edit the mod team from the community settings pages.

Test

If I’m right, this should also mute the comment reply for you since it’s an alt using the same copy of Tesseract since the post ap_id is used as the check.

It did :)

The reply shows up as “read” in the inbox without showing a notification indicator.

Yep :)

I had a “2-3 weeks” ETA about 2 months ago for the initial beta release. Looks like that ship sailed. In the last few days I’m kind of getting back into the swing of development but I’m still behind and can’t devote as much time to it as I’d like.

I think the last thing that’s preventing a beta release is the settings importer is unfinished (had to be re-written). Once that’s done, I can at least get the beta out for use. There’s a few other cosmetic things I need to fix as well but it’s still usable.

I have room in the panel now, that’s not the problem. Was just thinking it would be more economical to run one big circuit from the basement up to the kitchen and do the breakout there versus running 4-6 new individual circuits all that way.

Upgrading to a 200A panel is on the horizon though not right at this moment.

Unfortunately, time and money are factors. Not that I want to cheap out, I just thought maybe a sub panel might be more economical.

They wouldn’t know to check the kitchen has its own sub panel.

I mean, when there’s only a 40 amp breaker labeled “Kitchen S/P” I think they’d figure it out.

The kitchen would be the only room with a subpanel.

As stated in the post, the oven is already on a dedicated 30A circuit, and I’m not going to mess with that. There’s an empty void near the oven, though, and my thought was to run another 30 amp circuit up beside that to feed the subpanel and place it in that “void”. Decorating isn’t a concern for the void as there’s not much that can really go there anyway.

Definitely want to future proof it, yeah. I’m not married to 30 amp delivery to it, just used that as a reference point.

NEC requires 2 different 20 amp circuits for counter top use, 15 amps is not allowed,

That I didn’t know (or rather, haven’t read yet). Current ones are on 15 amp circuits, so I was going by that (not that previous owners seemed too concerned with “code” LOL).

Stove’s already on a dedicated breaker.

This is the US and we only have split-phase (two ‘hot’ legs at 120v on each end of a center-tap transformer)

Not that I dislike the original, but it’s one of the few times I like the cover more.

Tesseract (t.lemmy.world) both badges and lets you filter new accounts. You can configure the number of a days an account is considered “new” from 1 to 30 days. Anything that’s filtered will be shown as a stub/collapsed item in the feed.

In the upcoming release (delayed due to personal issues but in progress), you can completely hide content from new accounts (versus just collapsing it) among other filters.

Additionally, (in the upcoming release) it will automatically hide content from users less than a week old who have deleted their accounts. This feature is a direct response to this “hit it and quit it” nonsense from the accounts you’re describing.

I’ve had the feature request but it’s not implemented.

Have you heard it in Spanish? Lol

https://www.youtube.com/watch?v=JSDB7TH0ULA&start=36

Check your web access logs for these 3 IPs:

• 134.19.178.167
• 213.152.162.5
• 134.19.179.211

And see if they’re making repeated un-scoped (no page paramater) requests to /api/v3/comment/list. If they are, block them in your firewall.

Those used to hit my instance constantly with requests like /api/v3/comment/list?sort=Old&page=16514 (yes, page 16,414). When I blocked those IPs making those requests, problem solved.

Tesseract used to have that same bug. To fix it, I now poll /api/v3/federated_instances at startup and save those to a lookup variable. Before localizing a community, user, post, or comment link, it checks to see if the domain is to a known federated instance by looking for it in the list of federated instances.

There may be other ways to solve that problem, but that was what I went with. Bonus is it doesn’t require any extra network calls beyond the one to fetch the list of federated instances at startup.

Instance blocking is just blocking all communities on that instance, unfortunately.

Like Blaze said, you can try Piefed (LW also operates a Piefed instance) or you can use an alternate UI for Lemmy that does hide users from blocked instances. Not sure which do except Tesseract (https://t.lemmy.world/) since I wanted to be able to do the same thing.

The setting for that is under Settings -> Filtering -> Hide Users From Blocked Instances

deleted by creator