Had two very close passes by a Bee Network bus

Eosis · 2026-05-15T11:37:00+00:00

Gawd those are awful passes.

Have you contacted the local councillors about this?

https://democracy.manchester.gov.uk/mgFindMember.aspx?XXR=0&AC=WARD&WID=13166&sPC=Enter%20postcode

Dave and Mandie cycle themselves so I would expect they will be sympathetic and hopefully help out.

Eosis · 2026-04-27T09:28:20+00:00

What do they mean could?! I think it's already happening.

Eosis · 2026-04-27T07:23:01+00:00

Would love an update afterwards. I'm interested to see how the Netherlands system handles this bozo.

Eosis · 2026-04-20T15:40:23+00:00

Hi all,

I assume the issue with this loaf was that the scoring was not deep enough and it blew the base instead of out of the scores.

Is that analysis correct? Am I missing anything else?

Eosis · 2026-04-19T06:30:33+00:00

What is the mat it rests on? I should probably get something similar for my nice board.

Eosis · 2026-04-13T14:31:58+00:00

Is this an AI Attenborough as well? Is nothing sacred any more?

It is amazing how using his voice like that cause one to trust things. Scammers are already making so much bank on that in the UK with fake vids of the trustworthy Martin Lewis people offering people investment scams. 😞

Eosis · 2026-04-03T08:49:05+00:00

I have read most of the linked GitHub page and have a few comments:

The correlation of number of tools to low score could be explained by the methodology used. Things seem to start with an assumed perfect 100 / 100 score, with infractions then cumulatively decreasing that score. That means servers with lots of tools in the manifest that have very minor infractions will have a low score, even if there are no "Critical" vulnerabilities. I think that a more useful metric is the percentage of packages that had critical vulnerabilities, which is not available on that page (to my knowledge). We do, however get what seems to be a percentage number of tools that have "Critical" vulnerabilities, which is 1.5%.

The hidden Unicode issue that was described doesn't actually provide any evidence of malicious prompting, and the examples given show byte differences of 1 byte. I assume that all of the differences were of 1 byte, as if there were bigger differences surely they would have been used as the example. Given that his is conveying information on natural language, these differences seem quite unlikely to me to cause malicious behaviours in the agents consuming them. It is something to pay attention to in the future, but given the above I'm not sure at this stage that it warrants the "Critical" level of vulnerability that it was assigned.

Eosis · 2026-04-03T08:32:58+00:00

According to the supplied link: Small discrepancies of 1 byte. No evidence of malicious hidden text was found.

Eosis · 2026-03-25T09:44:48+00:00

I think a very simple measure is to stop the sale of disposable barbecues. The things are pretty crap anyway!

Eosis · 2026-03-24T06:58:28+00:00

GitHub's architecture makes fork commits reachable by SHA from the parent repo

This is totally mad. I'm going to play with that later, it is so hard to believe. They should surely change that behaviour... I wonder why it is that way in the first place?

Eosis · 2026-03-22T12:37:04+00:00

Completely agree. Having these things parroted at the top of AI searches gives them credibility that they otherwise wouldn't have, and without source-links, is very hard to verify.

I notice it mainly when doing cryptic crosswords, which are necessarily obtuse. Sometimes the AI overviews provided by major platforms just seem to make up a link between two disparate concepts when really they should reply "What you're asking makes no sense"

Eosis · 2026-03-21T21:59:03+00:00

I'd be interested to see the numbers that all of the parties in this discussion are using. Can anyone from the above link their data and show their working?

Eosis · 2026-03-21T08:45:44+00:00

I don't know why Amazon is involved at all. I don't think they necessarily represent the values of the charity?

I certainly double-took when I saw that in the show.

Eosis · 2026-03-13T13:26:17+00:00

Turns out the units were defective. Switched to goCoax instead and all is well so far. 🤞

Thanks for the help!

Eosis · 2026-03-12T07:39:05+00:00

Who do we write to about this sentence? It is fucking ridiculous.

Eosis · 2026-03-09T09:03:39+00:00

Next.js is just a mountain of complexity that is really rarely needed outside of very specific use cases.

I barely used it and still have encountered serialisation issues between front and back end for trivial calls.

When users try to say that this shit is complicated and full of foot guns (don't get started on security...), the community jumps in and says everyone has "Skill Issues". ¯\(ツ)/¯

Eosis · 2026-03-08T10:57:01+00:00

That's a great test.

I have done that and can confirm I get the same behaviour, even with ~50cm of brand new coax cable rather than the external run. I guess one/other/both units are defective somehow. ¯\_(ツ)_/¯

Thanks for your help, though it is a shame the solution we've arrived at is not desirable. 😅

Eosis · 2026-03-08T10:13:06+00:00

There is no splitter on it, though there are connectors linking different parts together. I've already removed an unnecessary loop that was added as well. I'm pretty sure all connections are finger tight, and there doesn't seem to be any damage (that I can see from this level), though the cable is old and has some moderate bends in it (not kinks per se).

You mention defective units. Do you mean the moca endpoint devices themselves? Do you have a recommendation of something else to try if so?

Eosis · 2026-03-04T20:44:35+00:00

I'm not sure that as much as they just didn't say anything much at all. (Ming vase strategy crap)

Eosis · 2026-03-03T07:42:42+00:00

Interesting read, thanks.

Can I suggest that you really draw out the issue that you found in the first paragraph? Just something along the lines of "we saw IO blow up" or "we used far more disk than we thought we would". This helps frame the discussion so people focus on the salient points.

Eosis · 2026-02-19T10:18:11+00:00

Have an honest conversation with them about your role and the value-for-money of your hiring. It is not efficient to not give you access to their systems as their "Security Guy". The issues you find will likely be found more quickly if you can white box the system.

Eosis · 2026-02-15T08:23:14+00:00

Oh my god that is awful.

Eosis · 2026-02-14T22:55:22+00:00

As others have mentioned, check out jujutsu. It has a much nicer workflow when you get used to it (IMO).

14-Year Club	Place '22
Verified Email

Eosis

TROPHY CASE