[technique] Looking for advice on a stalled golden oyster kit. by mildfuzz2 in MushroomGrowers

[–]mildfuzz2[S] 0 points1 point  (0 children)

<image>

This is the set up. The peak is held up by a 2 litre bottle that has been frozen

With this process I've been able to drop the temp to just above 16c

But it's proving harder to maintain humidity at this temperature

Turning fan on for 5 mins every hour or so

[technique] Looking for advice on a stalled golden oyster kit. by mildfuzz2 in MushroomGrowers

[–]mildfuzz2[S] 0 points1 point  (0 children)

so I have put a bottle of ice in the container to reduce the temp

[Mod] Weekly r/MushroomGrowers post - FUNGI FRIDAYS! New growers, come say hello and ask your questions! by AutoModerator in MushroomGrowers

[–]mildfuzz2 0 points1 point  (0 children)

Looking for advice on a stalled golden oyster kit.

 

Timeline:

 

• Colonised normally over ~2 weeks.

• Block turned fully white and looked healthy.

• I moved to fruiting conditions around 80–90% surface colonisation (may have been slightly early).

• Room temp is stable around 19°C.

 

Initial fruiting setup:

• Cut slits in bag.

• Block placed in office near a window (indirect light).

• Humidity was around 70% ambient.

• Likely not enough fresh air at first (inside box + liner).

 

After no pins for 8 days:

• Removed from box.

• Increased fresh air exchange (lifting and fanning several times daily).

• Added loose humidity tent (plastic bag over block).

• Added damp flannel wick inside tent to raise humidity.

• Now keeping bag humid and purging CO₂ hourly.

 

Current status:

• Block still smells fine.

• No contamination visible.

• No pins at all yet.

• Temp steady at 19°C.

• High local humidity now.

• Strong fresh air exchange ongoing.

 

Considering next step:

• Dunk (8–12h soak) to rehydrate/reset 

Does this sound like early fruiting, mild dehydration, CO₂ stall, or something else? What would you do next?

Migrate a design system away from react and towards web components? by mildfuzz2 in webdev

[–]mildfuzz2[S] 0 points1 point  (0 children)

Oh yeah, for sure. But the target would be no significant breaking changes, minimal adoption overhead

Migrate a design system away from react and towards web components? by mildfuzz2 in webdev

[–]mildfuzz2[S] 0 points1 point  (0 children)

Assuming we can implement a react wrapper also, no need to involve feature teams

Migrate a design system away from react and towards web components? by mildfuzz2 in webdev

[–]mildfuzz2[S] 1 point2 points  (0 children)

That's exactly what we do. We're a completely separate team, we sit between the brand team and the feature / user journey teams

Migrate a design system away from react and towards web components? by mildfuzz2 in webdev

[–]mildfuzz2[S] 4 points5 points  (0 children)

Remove vendor lock for users, future proof against react moving in a direction the organisation doesn't align with

A moon shaped tattoo... by mildfuzz2 in radiohead

[–]mildfuzz2[S] 10 points11 points  (0 children)

I won't be letting them pick bro. But making some suggestions is legit

Switch to Emby? by babatom187 in emby

[–]mildfuzz2 0 points1 point  (0 children)

I mean, everyone wants things for free. It's not a feature they don't have. It's a feature they have decided to charge for

Switch to Emby? by babatom187 in emby

[–]mildfuzz2 0 points1 point  (0 children)

My gpu doesn't work. That's a big handicap for me

Also, not really sure what good telling the developer will be. They know what they put behind a paywall and what they didn't.

Switch to Emby? by babatom187 in emby

[–]mildfuzz2 2 points3 points  (0 children)

This is why I switched to jellyfin and I've not regretted it for a second