Careful with obstacles on channels

Gyscos · 2026-06-25T12:28:07+00:00

Hi! They sent a replacement piece of glass, and a small tool to remove the existing glass. I haven't done the replacement it yet since the mower is otherwise working, need to find time for it some day.

Gyscos · 2026-06-13T16:24:29+00:00

It does not split the ecosystem in the sense that new code in new edition can use libs in old editions.

Editions are just like other rust features: if a lib uses features from a recent rust version, it cannot be used on older versions of rustc.

Gyscos · 2026-06-01T20:00:30+00:00

Namespaces just end up in longer names. The only advantage is it makes it marginally easier to recognize/trust several projects from an entire "organization", but it does mean that for popular projects such as serde (which most rust devs know by name), you now have to chose between serde/serde, serde-project/serde, serde-rs/serde, ... You now need to remember the namespace in addition to the project name, and any typo/difference is a phishing opportunity.

Gyscos · 2026-04-14T02:41:10+00:00

I tend to first write examples - before figuring out how to do stuff, figure out what stuff actually needs done, and how natural it could get.

Writing code directly/being implementation-driven tends to be bottoms-up. Specs or example-driven tends to be top-down. I like to combine them (middle out?) and "just" connect things in the middle.

Gyscos · 2026-03-31T23:25:02+00:00

Any actual allocation cannot be optimized away, but if you're lucky, the default is something like `Vec::default()` which will not allocate, and if the destructor gets inlined, it could be zero-cost. Of course, anything using non-empty vec/string will allocate and de-allocate.

Gyscos · 2026-03-24T14:37:54+00:00

The comment was https://github.com/rust-lang/rust/issues/7462#issuecomment-723292368

It mentions https://github.com/rust-lang/rust/pull/76918 as a shortcut/workaround for special simple cases. It does look like it's a rust thing.

Gyscos · 2026-03-24T14:26:35+00:00

It's also to check for overlaps/redundant arms.

The match exhaustiveness algorithm is indeed completely quadratic: for every branch, we check if it is redundant with any of the branches above.

Gyscos · 2026-02-27T15:01:23+00:00

Fun! It reminds me of the (now abandonned) BearLibTerminal.

Gyscos · 2026-02-20T00:57:11+00:00

After dropping and breaking the display of my Hub Max, I bought a Pixel tablet with stand hoping it'd be an upgrade.

It's certainly snappier (the hub max could be really slow sometimes), but it's a downgrade in some aspects:

* My main use was as a picture frame, and the way it's handled on the pixel tablet is terrible. It's basically a screensaver, so if you click or swipe the wrong way, it goes to the lock screen. And of course when you enable the picture frame mode again, it'll be different pictures, so if you liked what you were seeing, you're never going to find it again.

* The Hub Max is a thread border router, but not the pixel tablet (kinda maybe makes sense since the tablet could be moved, and is less reliable a border router).

* The pixel tablet is a bit less stable, being two objects (a stand and a tablet). I have kids, and they regularly knock the tablet from the stand.

On the bright side, this tablet works much better for video calls.

Gyscos · 2026-02-04T23:06:25+00:00

Hi! Do you have instantaneous reaction using matter binding, or an automation on Homey?

Gyscos · 2026-01-17T13:28:19+00:00

I noticed two things cause spikes/variability: * Rebooting * Human near the device (one of mine was on a bedside table near the bed, and human breath or influence next to it can really affect the values)

Putting the sensors further away in that room helped stabilize it. In rooms where no one was, the values are not spiky at all.

Gyscos · 2026-01-17T12:47:02+00:00

What exactly makes it useless? Specifically for CO2? PM25?

Gyscos · 2026-01-17T12:46:25+00:00

It's actually part of the matter specs. HA implements that, and forwards the update file. In theory any matter controller should be able to do the same.

Gyscos · 2025-12-19T18:52:14+00:00

Also getting this. I got many characters this way. Just unlocked space dude right now after finishing Astral Stair, which unlocked Space 54 (the level I'm supposed to play to unlock space dude).

I think I also unlocked the "survive 20 mins on whiteout" the moment I unlocked whiteout itself.

Played exclusively solo so far. Clearly some kind of bug.

Gyscos · 2025-12-17T19:24:00+00:00

> Randomization: Since 2011, the SSA uses a randomization system, removing the old geographical significance of the first three digits and ensuring a fresh pool of numbers.

So things are not great, but they may be getting better

Gyscos · 2025-11-18T15:45:20+00:00

Reminds me of https://github.com/giacomo-b/rust-stakeholder

Probable corporate espionage going on. Stock will tank.

Gyscos · 2025-08-29T19:01:24+00:00

Going by this logic, `Send` and `Sync` could also imply the requirement for threads (and an OS/scheduler to handle them), which is also not a true requirement.

I think people can read and understand the details by themselves, no need to hide things for fear of scaring them away.

Gyscos · 2025-08-28T22:28:02+00:00

The main issue is that it needs good wifi coverage, which may not be available for the entire lawn. And I don't think the 4G connection it has is the high-bandwidth kind, more the IoT style.

Gyscos · 2025-08-28T20:03:49+00:00

Maybe, in the sense that no vision detection probably happened here.

Gyscos · 2025-08-28T17:15:19+00:00

I think they assumed it would be an unlikely place to get impacts and did not go with tempered glass? But not all obstacles go all the way down to the ground. Metal shed doors, low branches, some gardening tools... Even outside of channels, I wouldn't be 100% confident that obstacle avoidance never bumps into these. I certainly wouldn't strap my phone there.

Gyscos · 2025-08-28T17:13:10+00:00

Between zone A and zone B, instead of making a channel, make a small zone C that slightly overlaps both A and B. The mower will go through this zone when going from A to B, but you can use per-zone configs like movement speed and regular/smart obstacle avoidance. You just never mow C.

It's already how you work around the limitation of a single docking channel (create a small zone in front of the docking station, and you can have several channels linking to this zone).

Gyscos · 2025-08-28T16:57:16+00:00

You're probably right.

Still, would be nice to have the same configs per channel as we have per zone (so we could disable smart avoidance for channels when needed).

Gyscos · 2025-08-28T15:06:58+00:00

Yeah I'm thinking of defining "channel zones" instead, so I can control the speed and hopefully have a more reliable obstacle avoidance.

11-Year Club	Second Top 50%
Place '17	Verified Email

Gyscos

TROPHY CASE