I keep learning the bare minimum of tatting and then getting frustrated and giving up... This time I'm gonna stick with it! Please forgive all the horrendous mistakes lol.

Are Lisbeth and DMC the only people left making cordonnet? I'd really like to try more appropriate thread but it seems to barely exist!

File here. This is almost definitely not the best one that anyone's designed, but at least it's a little unique!

The holder parts bend apart to snap brushes in and out, and there's a little shelf above to put your toothpaste on. The shelf has print-in-place hinges so you can print the whole thing flat with no support and it all works with no assembly.

We put this together for my public library's makerspace. I have a bunch of issues with the design, but it does work so what can I say really. Specifically it's this one.

Patrons can use it for whatever they want, i.e. melting dissolvable supports faster, culturing bacteria, etc.

Sorry this isn't actually foraging per se, but the only kind of people who'd grow these are probably foragers anyway. I've been growing them for a couple years, but this is the first year I had enough to bother trying to eat them! From two plants we got about 1/2 a cup.

So my question is, does anyone have any tips for actually eating these things?? We tried soaking them for 24 hours and boiling them for 2 hours, and they were still inedibly bitter! I'm thinking maybe brining them, an alkaline soak, splitting them all in half, and/or swapping out the cooking water a few times. At least one of those ought to work hopefully. It'll have to wait till next year though, we wasted these ones lol.

Specifically this font, although I've tried a few. Specifically in HashLink.

Anyone have any tips or best practices when it comes to fonts and FlxText in general? The default font looks great, but I'm finding that just about every other font I try looks kind of terrible. Like sort of grainy, I guess? The default one looks very crisp in comparison. Also, any non-default font that I put in a FlxButton seems to be vertically way off-center, raised up too high.

Hopefully this kind of content is ok here. Up until recently, when I would be searching for some kind of technical info, the top (and best) results would usually all be Reddit posts. I was very pleasantly surprised to do that this time and find a Lemmy post instead!

...It did happen to be a post from me, so unfortunately didn't answer my question at all, but I still thought it was really neat and wanted to share. Has anyone else seen Lemmy stuff getting indexed and turning up in their search results?

Hi DIY punks! I need a little help with something. I've been trying all sorts of ways to home carbonate things as sustainably as possible. Most have not really worked out as intended, but I'm really really close on this latest attempt. This version is to connect a CO2 tank to a whipped cream dispenser.

Basically, the path from the tank looks like this:

• 5 lb CO2 tank → dual gauge primary regulator.
• Regulator → 5/16" hose.
• 5/16" hose → 5/16" barb to 1/8"NPT male.
• 1/8"NPT male → 1/8"NPT female to 8mm female quick disconnect.
• 8mm female quick disconnect → 8mm male quick disconnect to 3/8"-24UNF female.

...and the path from the dispenser looks like this:

• 1Qrt ISI Gourmet Whip M22 Male → M22 Female.
• M22 Female → "mystery hose".
• "Mystery hose" → "Mystery connection" male.

So, I need an adapter to hook up the 3/8"-24UNF female to the mystery connection. It seems to start screwing in for a couple turns, but then won't go any further, so my guess is that it's the same diameter with different threading? Note that, in the link for the mystery hookup, I removed the TR21-4 at the end, because that's for directly hooking up to a small tank. The mystery connection I'm talking about is the male threaded part you can see screwing into the TR21-4 connector.

It doesn't seem like many people are doing this, or know what most of the industry standard connections actually are. See this thread here for example. Consequently, I have no idea if the mystery eBay hookup I bought even works, despite that being its entire purpose. The interior of the CO2 cartridge puncturing mechanism is a black box to me, so I'm just trusting this M22 connection is all that's required. There's definitely some kind of one-way valve in there, but hopefully it doesn't somehow require being "pushed" by the cartridge itself.

For the first time, I had a lot of Illinois Bundleflower seeds to harvest. I've never cooked or eaten them before, and information online is pretty slim unfortunately. So, I just took a stab at something random. For the filling:

• Desmanthus illinoensis seed/grain
• Manoomin
• Dried crushed rockweed
• Black bean miso
• Vegetable stock
• Cheddar

...all stuffed inside a white scallop pattypan squash. It was... about as okayish as it looks, not fantastic, not terrible. Honestly I thought about posting it to c/ShittyFoodPorn instead 😅

More importantly than the quality of the dish, it turns out Illinois Bundleflower seeds are easy to cook and have decent flavor and texture! So, task failed successfully I guess? Thank you for your time!

It was chilling on a Paulownia tree in Southeast Pennsylvania, U.S. I post more critters on my Pixelfed if anyone's interested.

I post a lot of edible plants native to (roughly) the Northeast U.S. on my Pixelfed account.

So, the FlxG collide method knows how to tell which tiles in a tilemap are walls or not walls, but the overlap method does not. If you write a simple custom collision with the overlap method and tell it to .separate(), your sprite will collide with every tile in the map, not just the walls.

This is expected behavior, as there's a note in the FlxG documentation that says:

this takes the entire area of FlxTilemaps into account (including "empty" tiles). Use FlxTilemap#overlaps() if you don't want that.

On the other hand, the documentation for FlxTilemaps.overlaps() says:

Checks to see if some FlxObject overlaps this FlxObject object in world space. If the group has a LOT of things in it, it might be faster to use FlxG.overlaps().

In my scenario I have a lot of tilemaps and just one object to collide with them, the player. The way this is written, I'm thinking I have to call this method for EACH MAP, i.e. map1.overlaps(player), map2.overlaps(player), etc. Whereas with the FlxG method I can pass it the entire FlxGroup of maps as one parameter and the player as another parameter, which seems way better. I guess I could write a function with a loop that iterates through each map doing this one by one, and then call that in update(), but I'm getting the impression that it might be really inefficient.

What's the best approach here? Am I missing something obvious?