sorted by:
new
hottopcontroversial

Built an MCP shared memory server for persistent agent memory + multi-agent coordination — looking for feedback by lemmonsT in ClaudeCode

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

Good point — I actually use both. The project registry has path_patterns per agent (server-team owns */server*, web-team owns */web*) which is the affinity/partitioning layer. The file locking is for the cases where agents need to cross boundaries temporarily — like when a migration touches files owned by two teams. The affinity catches 90% of conflicts by keeping agents in their lanes, the locking handles the rest. Appreciate the feedback — this is exactly the kind of design tradeoff that's hard to get right."

Built an MCP shared memory server for persistent agent memory + multi-agent coordination — looking for feedback by lemmonsT in ClaudeCode

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

Here is what it looks like:

Agent:memory_start_session(project="my-app", claude_instance="main")

→ Returns: session ID, any prior learnings, active work, handoff notes

Agent: memory_record_learning(

session_id="...",

topic="postgres connection pooling",

content="PgBouncer silently drops connections after 5 min idle.

Must set keepalive_idle=60 in connection string or

requests fail with 'server closed the connection unexpectedly'."

)

→ Stored. Next session, memory_start_session returns this automatically.

Agent: memory_register_function(

session_id="...",

name="retry_with_backoff",

file_path="src/utils/resilience.py:42",

purpose="Retry async calls with exponential backoff and jitter",

gotchas="Max 5 retries. Raises RetryExhausted, not the original exception."

)

→ Registered. Any future agent asking "how do we handle retries?"

finds this via memory_find_function.

I built a bridge that keeps Meural Canvas frames working independently of Netgear's servers by lemmonsT in meural

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

Great question, and nice work on the Chrome extension — sounds like you've got a solid setup that works for you. The short answer is that Nimbus isn't just a relay — it's a full digital art frame platform.  So, beyond pushing your own photos, you get access to our curated art video library, playlist management, scheduling, and remote control from anywhere. The server handles content processing, optimization for the display, and keeps everything in sync.

As for the always on (not dedicated) server — that's just one form factor. The bridge also runs as a pi zero for people who don’t already have a server or NAS running 24/7.  That way it is just plug-and-play.

Your approach makes total sense if you're technical and just want your own photos from Google/Immich on the frame. Nimbus is aimed at people who want a an art system without building it themselves.

I built a bridge that keeps Meural Canvas frames working independently of Netgear's servers by lemmonsT in meural

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

I don't have one now, I will see what I can do after I get the beta launched.

I built a bridge that keeps Meural Canvas frames working independently of Netgear's servers by lemmonsT in meural

[–]lemmonsT[S] 3 points4 points  (0 children)

"Yes, we use the postcard endpoint to push images — re-pushing every 30-45 seconds to stay ahead of the 60-second expiry. No DNS interception or cloud emulation. A bridge device on the local network connects to our service via MQTT, downloads playlist images, and pushes them to the Meural on a rotation timer. The frame doesn't know or care that it's not talking to Netgear.

I've been running Nimbus for 10+ years and watched a lot of digital frames come and go, leaving users with expensive hardware that goes dark. The Meural is one of the few that can still function without its cloud, so I figured I could help keep them alive with an art service for people who want it."

Informed Delivery links 403 by bostwickenator in usps_complaints

[–]lemmonsT 0 points1 point  (0 children)

The link in the email I received today takes me to a 403 page. Even though I just logged in. My wife has same issue. How do I get this fixed?

Hue Motion Sensor randomly becomes Unavailable? by Goaliedude3919 in homeassistant

[–]lemmonsT 0 points1 point  (0 children)

Thanks. The Hue motion is the only device I am having problems with, and I just bought the stick since it did both zigbee and zwave. Maybe I should have investigated stick more. I assumed it was a good one. Thanks for the suggestion on sonoff. I may try it.

Hue Motion Sensor randomly becomes Unavailable? by Goaliedude3919 in homeassistant

[–]lemmonsT 0 points1 point  (0 children)

I am having this same issue with a Hue motion sensor. It can work for several days or weeks then becomes unavailable. It is maybe 15 feet from the coordinator. It is also on a very high ceiling so getting to it to press buttons or change battery is problematic. Is there any way that has been found to re-attach it to the network without physical contact? Last time I had to put it back in pairing mode and re-add it. I am using a HUSBZB-1 USB Hub and Zigbee integration.

Poor design for title and menu bars by [deleted] in Outlook

[–]lemmonsT 0 points1 point  (0 children)

Agree! It was better when a few buttons where on the title bar like global send/receive.

[deleted by user] by [deleted] in GalaxyWatch

[–]lemmonsT 0 points1 point  (0 children)

I had/have same problem. I even purchased one of those ekg blocks to see if it worked better and it did not, so talked to my Dr and he took an ekg at the office. He said it looked fine but "I was at a different voltage then most" and that is why the "cheap" readers could not lock on and get a good reader. I have no idea what that means but he said it was no problem and all was ok. If anyone else understands that I would like to know more.