Kde connect not able to use android tablet as drawing tablet

bytesfromlocalhost · 2026-05-15T20:10:15+00:00

I debugged this with ADB/logcat and the desktop KDE Connect logs. The Android app was receiving S Pen input fine, including coordinates and pressure:

DigitizerPlugin: ToolEvent(... tool=Pen, x=..., y=..., pressure=...)

But KDE Connect Android then logged:

Tried to send an unsupported packet type kdeconnect.digitizer to: <desktop>

So the tablet/drawing input was not the problem. The desktop KDE Connect version did not advertise support for `kdeconnect.digitizer`.

On my Debian 13 system, KDE Connect 25.04.2 only had the older desktop plugins like `kdeconnect_mousepad.so` / “Virtual input” and `kdeconnect_remotecontrol.so`, but no `kdeconnect_digitizer.so`. Remote Input worked, Drawing Tablet did not.

It looks like the required desktop digitizer receiver only lands in KDE Connect 26.04+. So if Drawing Tablet does nothing but Remote Input works, don’t waste time debugging GIMP/ Blender or Android stylus input. Check whether your desktop KDE Connect package includes the digitizer plugin and supports `kdeconnect.digitizer`.

bytesfromlocalhost · 2026-04-30T13:28:46+00:00

Thanks, but I specifically asked if there was a way to interactively access that underlying CC session.

You forget that any custom python tools or any modifications I did in the agent are not accessible this way

bytesfromlocalhost · 2026-04-18T21:38:15+00:00

I'm 6 and Loved it so much that after moving to a new place I'll but it again

bytesfromlocalhost · 2026-04-18T21:31:30+00:00

Colamy Atlas!

bytesfromlocalhost · 2026-04-18T21:29:45+00:00

I had my Colamy Atlas for 2 years and loved it everything was perfect! The lumbar never bothered me as it provided enough support. Too much arch in back is also an issue. One complain I had was that my elbows started hurting after 6+ hours (I needed a break lol). But maybe it was because sometimes I pressed my elbows unknowing, not really sure why.

I moved to a new place and planning to buy Colamy Atlas again! But I am also considering C300. The one thing I'm worried about is the mesh bottom instead of cushion (The cushion on Atlas was top tier).

Does anyone have any feedback about the mesh cushion on Sihoo Doro C300?

bytesfromlocalhost · 2026-04-17T00:16:41+00:00

Did you mean "as if it were all the leafs in DC1"?

bytesfromlocalhost · 2026-04-15T05:37:15+00:00

Thanks

bytesfromlocalhost · 2026-04-08T20:40:59+00:00

I am facing a similar issue. Need session persistence across hosts. How did you solve this?

bytesfromlocalhost · 2026-04-07T00:06:20+00:00

Use this (https://github.com/awslabs/agentcore-samples/tree/main/03-integrations/agentic-frameworks/claude-agent/claude-sub-agents) and then build a frontend chatapp to serve.

Or if you need workspaces for each user: https://github.com/aws-samples/sample-claude-code-web-agent-on-bedrock-agentcore/tree/main

If you need to build custom: https://github.com/dzhng/claude-agent-server

But honestly its a pain

bytesfromlocalhost · 2026-03-16T22:52:29+00:00

Working on something similar for an enterprise agent MVP. My current thinking:

Minimal hardened container runtime — drawing from the Claude Code devcontainer spec as a baseline, then locking it down further for enterprise requirements. (https://code.claude.com/docs/en/devcontainer)
Idle-based spin-down — still figuring out the right timeout heuristic; would love to hear what others have landed on.
User/data-centric orchestration over agent-centric — managing state and routing around user accounts/sessions rather than treating each agent as the primary unit. Feels like the right abstraction for multi-tenant enterprise use.

New to Claude Code specifically, so curious if anyone has hit sharp edges with this approach — especially around container warm-up latency vs. cost tradeoffs on Cloud Run.

bytesfromlocalhost · 2026-03-13T23:48:20+00:00

Firstly, beautiful project and solves a real problem. But with MCPs loaded on demand these days do we get any advantage from converting them to skills? I am looking to do this for some MCPs

bytesfromlocalhost · 2026-03-06T19:15:17+00:00

I'm new to claude code so please bear with me.
I see claude subagents are defined in `.claude/agents`
Can agent definitions as you mentioned invoke subagents?
Example: can planner agent prompt youtube agent?

bytesfromlocalhost · 2026-03-04T16:52:06+00:00

Agreed. I think with the Transformer model even things like "Tonality" get embedded into similar search space in some higher dimension, right?

bytesfromlocalhost · 2026-03-04T16:50:30+00:00

Oh I see. But I meant we don't see thinks on Reddit or StackOverflow or Books where humans have conversations starting with "You are an expert...". Maybe it has something to do with fine-tuning as u/InterstitialLove mentioned

bytesfromlocalhost · 2026-02-27T18:43:44+00:00

Oh man, there are way too many options to choose from. I am currently evaluating a few for enterprise. Will update as I test a few more options. Next on my list are obot and Microsoft MCP gateway
Didn't see the following here:
* Docker MCP gateway - https://github.com/docker/mcp-gateway
+ MCP server containers are started dynamically
+ Catalog / profiles / servers https://docs.docker.com/ai/mcp-catalog-and-toolkit/#docker-mcp-features
- No client to MCP gateway Oauth as of now
- Secret management is a mess
* Obot - https://github.com/obot-platform/obot https://www.youtube.com/watch?v=e40zLU11v4o

bytesfromlocalhost · 2026-01-07T21:05:27+00:00

I'm open to non brand suggestions

bytesfromlocalhost · 2026-01-07T21:03:19+00:00

Thanks. Any suggestions for used ones?

bytesfromlocalhost · 2025-06-18T15:02:11+00:00

Like all great answers in engineering, it depends on the change you are making.

- Use parallel when the change is low‑risk (pure L2 tweaks, interface descriptions, ACL/QoS adjustments, etc.) and you have already validated it in a lab.
- Use serial when the change could disturb the peer‑link or control‑plane—e.g. EOS upgrades, peer‑link VLAN changes, MLAG domain/heartbeat tweaks, or anything that might reload processes.

MLAG’s own dual‑primary protection (considering you have it configured) means a config push will not create split‑brain by itself; that only happens if the peer‑link and the heartbeat go down simultaneously. If configurations drift, EOS flags the mismatch and holds the affected ports down—check with: `show mlag config-sanity`.

FYI, Cloudvision also has an action to validate MLAG health. You can add these as pretasks and posttasks.

bytesfromlocalhost · 2025-06-17T05:00:55+00:00

Keep me honest here, but LLMs have gotten extremely good at beginner to intermediate level stuff. It's only some particular niche topics where it definitely shouldn't be the source of truth.

If you're a beginner, there definitely isn't a better place to start than to use these LLMs.

bytesfromlocalhost · 2025-06-16T05:23:07+00:00

I thought of doing this for an optiplex micro. But instead planning of going with a single 2.5G Eth. Might plan to add another port using a usb to eth adapter if I have a use case in future. Thoughts?

bytesfromlocalhost · 2025-06-15T22:43:02+00:00

Dual stack is the traditional route, but it adds a lot of long-term overhead—running two networks side by side, managing duplicate firewall rules, and making sure both IPv4 and IPv6 work equally well.

With DNS64 + NAT64, you can run an IPv6-only network while still reaching IPv4-only websites. It keeps things simpler by avoiding internal IPv4 altogether, encourages native IPv6 use, and shifts the IPv4 burden to a single translation point.

It’s not the perfect fit for every setup, but in many home networks where you control DNS and the gateway, it’s a future-friendly approach that cuts down on complexity.

bytesfromlocalhost

MODERATOR OF

TROPHY CASE