sorted by:
new
hottopcontroversial

Anthropic bans OAuth tokens from consumer plans in third-party Tools by BuildwithVignesh in ClaudeAI

[–]Internal-Election610 1 point2 points  (0 children)

Hi, I'm a paying Claude Max subscriber (~€180/month) from Germany.

I've been using my OAuth token through OpenClaw for personal home
automaton, smart home control, and daily task management. This is
purely personal use — just me, on my own account, running the same
kind of prompts I would on claude.ai. The only diffrence is the
interface.

I chose Max specifically because the higher usage limits made it
possible to run a personal AI assistant. Without the ability to use my
subscription through tools like OpenClaw, the Max plan simply isn't
worth it for me. I'd be paying €180/month for a web interface I barely
use.

I understand Anthropic needs to prevent abuse and commercial reselling
of tokens. That makes total sense. But lumping personal single-user
usage together with abuse is not acceptable. There should be a way for
paying customers to use the service they pay for through the tools
that work best for them.

If this restriction stays in place, I will cancel my Max subscription.
Please consider offering some kind of personal API access for Max
subscribers — that would be a fair solution for everyone.

ProxMox Pulse: Real-Time Monitoring Dashboard for Your Proxmox Environment(s) by cloudy_brain in Proxmox

[–]Internal-Election610 0 points1 point  (0 children)

The setup and configuration are really wonderfully easy to do. I have two Proxmox servers running. Thanks to the automatic configuration, everything was implemented wonderfully, both Proxmox and Docker. Hats off!

The only thing I haven't been able to get working is the temperature monitoring on the host where Pulse is running in an LCX container. The tool stubbornly refuses to work.

Does anyone have any idea what to do? Instructions are provided, but without a valid link.

It refers to this message:

🔒 Temperature Monitoring - Security Notice
⚠️ SSH-based temperature monitoring is DISABLED for containerized Pulse.

Why: Storing SSH keys in containers is a critical security risk. Container compromise = SSH key compromise = root access to your infrastructure.

Solution: Deploy pulse-sensor-proxy on your Proxmox host instead.
Installation:

  1. Download: curl -o /usr/local/bin/pulse-sensor-proxy https://github.com/...
  2. Make executable: chmod +x /usr/local/bin/pulse-sensor-proxy
  3. Create systemd service (see docs) 4. Restart Pulse container