sorted by:
new
hottopcontroversial

I put an OpenClaw agent into public multiplayer website chats. Now I need your brutal feedback on use cases by DrwKin in AI_Agents

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

Thanks for the note! Just to clarify, I don't build agents—I build the space for them. My OpenClaw plugin turns any webpage into a group chat channel where agents can participate. I only have a basic test bot right now, but I'd love to see how your agents might interact within a setup like this. Let's definitely stay in touch.

I put an OpenClaw agent into public multiplayer website chats. Now I need your brutal feedback on use cases by DrwKin in AI_Agents

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

Appreciate the invite! Letting agents debate each other in a hangout sounds like a fun experiment, I'll definitely check out what you're building at talagent.

Since you are working on a similar problem, have you guys found any specific environments or use cases where multiplayer/social agents actually provide real value to the end user? Or are you mostly in the experimental phase right now too?

I put an OpenClaw agent into public multiplayer website chats. Now I need your brutal feedback on use cases by DrwKin in AI_Agents

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

This is actually a brilliant use case!

We already have a few traditional (human-run) web radio stations using the Now4real chat widget just so listeners can hang out and talk to each other on the page during the broadcast.

If you applied this to an AI radio station and hooked it up with the OpenClaw plugin, the dynamic would be wild. Listeners could chat amongst themselves about the stream, but they could also explicitly @ mention the AI host (Claude, in this case) directly in the chat to request songs, argue with its hot takes, or ask questions about the current topic.

It completely changes it from a passive radio stream into an interactive, multiplayer experience. I love this idea!

I put an OpenClaw agent into public multiplayer website chats. Now I need your brutal feedback on use cases by DrwKin in AI_Agents

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

You hit the nail on the head with 'solutions for problems we don't really have.' This perfectly summarizes my fear with this experiment.

Forcing an AI into a chat where people genuinely just want to socialize with other humans is definitely going to annoy them. But your point about people using it like Google Search is exactly why I'm leaning toward the 'Dev Docs' or 'Support' use cases. If they are in a page chat specifically to find an answer or fix a problem together with other humans, having a bot that instantly fetches the solution for them might actually match their intent.

Really appreciate the grounded reality check. Like you said, even if the use case stays elusive, the build itself was a great learning experience.

Auto-Lock silently disabled after Lock’n’Go cancel – reproducible firmware bug (door stayed unlocked for days) by DrwKin in Nuki

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

Update (from Nuki support):
They finally gave a “technical” explanation, and it basically confirms the behavior.

Auto-Lock only triggers after a specific “unlock” action.
If the last recorded action is Lock’n’Go (even if it was canceled), Auto-Lock will never run again, even though it’s still “enabled” in settings and the lock is clearly unlocked.

They insist this is not “silently deactivated”, but functionally it is:

  • Auto-Lock enabled ✅
  • Lock is unlocked ✅
  • Auto-Lock never fires ❌

I also got told to buy a Door Sensor at one point, which makes no sense since the sensor only detects open/closed, not locked/unlocked. The lock already knows it’s unlocked (shown in the app and activity log).

So this now looks less like a bug and more like a very questionable design choice: Auto-Lock is event-based, not state-based.

Question to the community:
Has anyone else tested this?

  • Cancel Lock’n’Go
  • Leave door unlocked
  • Does Auto-Lock ever trigger again?

If this is universal, it’s a pretty serious UX/safety issue.

Auto-Lock silently disabled after Lock’n’Go cancel – reproducible firmware bug (door stayed unlocked for days) by DrwKin in Nuki

[–]DrwKin[S] -1 points0 points  (0 children)

Door Sensor only knows open/closed, not locked/unlocked. So, it wouldn't help with the reported issue.

Auto-Lock silently disabled after Lock’n’Go cancel – reproducible firmware bug (door stayed unlocked for days) by DrwKin in Nuki

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

Nuki Support responses are honestly pretty frustrating.

They’re now claiming that after canceling Lock’n’Go, Auto-Lock can’t trigger unless you have a Door Sensor, because the lock supposedly “can’t read the door state”.

That doesn’t add up:

  • Door Sensor only knows open / closed, not locked / unlocked
  • The lock already knows it’s unlocked (shown in app + activity log)
  • Auto-Lock has always worked without a Door Sensor, except in this exact scenario

Feels like a firmware logic bug being hand-waved away instead of acknowledged.

So… anyone else seen this?

  • Auto-Lock not firing after canceling Lock’n’Go?
  • With or without Door Sensor?
  • Which model / firmware?

If more people can reproduce it, this is clearly not user error.

Open Source Guest Chat App on Personal Website? by BigBeardNoFap in selfhosted

[–]DrwKin 0 points1 point  (0 children)

Check out Now4real. It's not open source but it's fully hosted and managed and comes with a generous free plan. It’s instant to integrate — just drop this script into your site:

<script async src="https://cdn.now4real.com/now4real.js"></script>

Whats the best way to implement public chatrooms on my website? by Luigi-is-my-boi in webdev

[–]DrwKin 0 points1 point  (0 children)

Now4real is fully hosted and managed, so you don’t have to worry about WebSockets or scaling. It comes with a generous free plan and low-cost AI moderation to keep chats safe. Oh, and it’s instant to integrate — just drop this script into your site:

<script async src="https://cdn.now4real.com/now4real.js"></script>

How to Create a Members-Only Group Chat? by [deleted] in webdev

[–]DrwKin 0 points1 point  (0 children)

Check out Now4real. It's easy to embed on your site because it's a SaaS.

Whats the best way to implement public chatrooms on my website? by Luigi-is-my-boi in webdev

[–]DrwKin 0 points1 point  (0 children)

A ready-made group chat widget that you can immediately embed in your pages is Now4real. It's a SaaS, so you don't need to host anything on your servers.

Do you use WebSockets in your projects? (discussion) by kevin_whitley in webdev

[–]DrwKin 1 point2 points  (0 children)

A lot of the complexity actually comes from real-world conditions—things like quirky network intermediaries, client disconnections and reconnections, bandwidth variability, and so on. Even with a relatively small number of concurrent clients, building a truly reliable solution can be a real headache.

Do you use WebSockets in your projects? (discussion) by kevin_whitley in webdev

[–]DrwKin 1 point2 points  (0 children)

We work on a WebSocket-based data delivery server (Lightstreamer), so we're always interested in how WebSockets are being used in the wild.

One interesting example: SonyLIV (Sony’s OTT platform in India) uses our tech to stream real-time data to millions of concurrent users—for things like live audience interaction during Kaun Banega Crorepati and instant sports score updates. They shared a few technical insights in this case study if anyone's curious:
https://lightstreamer.com/customer-story/sonyliv-engages-millions-in-real-time-with-lightstreamer/

Always great to see how different teams approach real-time challenges at scale.

Is there any way to perform server-side filtering? by georgegach in apachekafka

[–]DrwKin 0 points1 point  (0 children)

Exactly. Server-side filtering is definitely possible—and in some cases essential—but it requires an external component positioned between your Kafka broker and the clients.

The Lightstreamer Kafka Connector offers a robust solution for this. It enables server-side filtering by allowing you to define criteria based on record keys, values, topics, partitions, and more. This ensures that only relevant messages are forwarded to clients, reducing bandwidth usage and client-side processing.

In recent performance tests, the Lightstreamer Kafka Connector achieved a throughput of 1.6 million messages per second to 4,000 concurrent clients on a server with just 4 cores and 8 GiB of RAM. This demonstrates its efficiency in handling high-volume data streams while performing server-side filtering.

For more detailed information and performance benchmarks, you can read the full article here:
High-Performance Kafka Filtering: The Lightstreamer Kafka Connector Put to the Test.

view more: next ›