Member
Respect honestly
We tried the manual route for about a week and half the team got RSI
These days we run a lightweight watcher on OVHcloud's event stream, webhook into a private channel with 30s batching. Keeps the noise down and we never hit limits
The muted channel graveyard is real though Diego, we archive one every quarter
Member
The muted channel graveyard is too real. I have eleven.
Only eleven? I hit the 50-channel ceiling on my main workspace last year and had to spin up a second account just for deal alerts, which of course I also muted within a month
These days I just lean on a single Contabo webhook pointed at a private channel with aggressive keyword filtering, anything below a certain core threshold gets dropped before it pings me
Member
I feel this in my bones. I have like 8 muted ones and 3 that are just me talking to myself about deals I missed. The notification fatigue is absolutely brutal.
Still checking manually though. Some things never change
Telegram bots are great until the bot owner ghosts and the API key expires. Been there.
I ended up wiring a dead-simple webhook into our own RackNerd project (https://www.racknerd.com). Pushes to a private Matrix room, no polling at all. Matrix handles the rate limiting client-side so the server just sleeps until something happens.
Only downside is the mobile notifications are louder than my actual alerts. Still tuning that.
Anyone tried Matrix over Telegram for this stuff?
Member
Five days quiet but this one is still relevant
I keep exactly three channels unmuted and route everything else through a KnownHost webhook that filters by price-per-core and region
The rest go to a muted archive I check when I am bored
Has anyone tried the OVHcloud beta for deal alerts? I got an invite last month but have not set it up yet
Member
Seven days and nobody else admits to the graveyard. I respect that.
This is actually how I started. The channel sprawl came later when I tried to automate my way out of it. Now I have bots posting into threads I muted because the signal died. Leaseweb had a drop last month where the Telegram bot beat the RSS by four minutes and I still missed it because the group was on mute.
Has anyone tried webhook-only setups with actual filtering? I am tired of the notification whiplash but manual checking is worse.
Seven days and nobody's mentioned webhooks? I used to poll Contabo's API every 90 seconds until I got a friendly rate-limit email. Switched to their webhook feed and never looked back.
Still have one RSS reader running for CloudCone legacy alerts but the firehose is unreal.
Did anyone actually get the Telegram approach working cleanly with Contabo's API, or did you all hit the same wall I did with their token refresh. I keep meaning to retry and then the deal drops and I forget again.
Member
Eleven muted channels and counting, I respect the grind
I tried the telegram thing once but the bot died when Contabo changed their page layout and I never fixed it. Manual f5 is terrible but at least it never breaks
Has anyone actually kept a bot running for more than a year without rewriting it
Member OP
Eleven muted channels is impressive discipline. I am still stuck at four and already tuning them out.
Has anyone here tried hooking a webhook straight into a Matrix room? I have been experimenting with it for internal alerts and the threading is cleaner than Telegram for noisy feeds. Curious if anyone has it wired to deal drops specifically, or if the latency is too punishing for time-sensitive stock.
Sam
