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.

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)

Seems more like a genuine feature to me.

I don’t know how many requests I’ve seen for Lemmy apps to be able to swipe between posts in the feed.

Seems that’s basically what they’re doing here.

But also, gesture navigation is terrible, I hate it, and always turn on 3-button navigation when I get a new phone anyway.

I shouldn’t say this, but whatever: It’s a “troll” tactic to do that since mods/admins can’t ban with content removal if the account is deleted (unless that’s fixed in .13?) . Admins can remove the deleted flag in the DB for the user and then do so, but mods can only remove items individually. Not that any of these necessarily warrant removal on their own, but not doing so in this case encourages this kind of “hit it and quit it” behavior, and this user is clearly ban evading.

I’m not saying this as an instruction manual but merely as a statement of fact about how stupid Lemmy’s behavior is with regard to deleted accounts.

They’ve had many, many alts over the last 6+ months with the same posting pattern. Not one has been marked as a bot.

Ok, I just gotta ask: what is your motive here?

You get banned every other day for spamming out a massive number of posts. And you just make a new account the next day, start the exact same thing again like…you’ve learned nothing?

I’m tired of my feed being an entire page of just you, and I’m tired of blocking you. Can you not just post things at a normal rate?

Email on your own domain: Yep, super easy.

Email from home IP or from the IPv4 you get assigned with a VPS: Super difficult

Good points.

I don’t have a full plan yet (just the general idea of a plan), but when I start the journey to Piefed, it’ll probably be from the ground up or very close to that. I already need to update the codebase from Svelte 4 to Svelte 5 which is a pretty big job due to the fundamental and breaking changes between those two versions.

The components that make up Tesseract (posts, comments, sidebars, everything) are also all heavily tied to Lemmy’s type definitions. To support Piefed, I’d have to de-couple the components in the code from Lemmy’s type def and add in an abstraction layer (both for future-proofing and to make it possible to support both if I wanted to).

Yeah…I’ve had to do a LOT of work client-side in Tesseract to give Lemmy half the features Piefed has. Eventually I’m gonna start targeting Piefed, but there’s some under the hood stuff I’m waiting to be resolved before I embark on that voyage. Mainly, I’ve heard that the main Piefed experience and the API are not 1:1 and not everything is exposed in the API. :(

It doesn’t now, but I’d be willing to add that to Tesseract. Seems easy enough to implement.

Edit: It’s not fully plumbed in yet, but the settings to configure it have been added to the filter policy framework. Will probably also do a similar setting for comments. Shown enabled here, but disabled by default, naturally.

Edit 2: Plumbed in and working now in the dev build. Can also completely hide those, but that doesn’t exactly work for a screenshot.

Lemmy’s API doesn’t have a direct way to do that, unfortunately.

Tesseract (web-based lemmy app) used to have that before I took it out. After the ranking metrics were removed from the API, it was hard to sort them other than by new/old or by score. When you have a mix of active and inactive communities, it didn’t work great without the ranking metrics being there.

You can still group communities, but only for organizing them or (in the dev branch/next version) applying filter policies to communities in that group.

I may revisit the idea if I can figure out a better way to generate/sort the custom feeds.

What they lack in quality they make up for in quantity.

Wish I’d have thought of that before I started cleaning up the codebase 😆. Several releases were technically Oberth class haha.

I like it. Might just take you up on your suggestion.

All apps should sprinkle a little Trek in when they can:

Haven’t decided what I’m gonna call 1.5 series. I want to do Defiant class, but I already wasted that on the short-lived 1.3 series.

The discussion you’re chiming in on wasn’t even about this article; it was about one from a week ago. And now you’re butting in with the wrong context, making unfounded accusations, jumping to conclusions, and throwing out personal attacks… Keep up or keep out.

Mod removals should link to this automatically and be more transparent for why comments were removed in the first place

I linked to the modlog through Lemmy World’s instance of Tesseract. I’m the dev of that UI, and I agree with you that removal reasons should be more accessible.

A version or two ago I built in a feature to automatically resolve the removal reason and append it where the comment would be, right there in the comment section. If that’s disabled, there’s a button to take you to the modlog for that item.

If Tesseract isn’t your cup of tea, maybe ask the dev of your client to add a similar feature.