I was reminded of this.
"But the plans were on displayā¦ā
"On display? I eventually had to go down to the cellar to find them.ā
"Thatās the display department.ā
"With a flashlight.ā
"Ah, well, the lights had probably gone.ā
āSo had the stairs.ā
"But look, you found the notice, didnāt you?ā
āYes,ā said Arthur, āyes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying āBeware of the Leopard.
Douglas Adams, The Hitchhikerās Guide to the Galaxy
===============
So, thanks for the message but it is just platitudes & excuses.
No one has properly explained why a cloud login is actually necessary. Plenty of waffle. No substance (see hypocrisy further down) The instance knows how many notifications it sends. Because it seems you do? But you said you didnāt? Howā¦odd.
Stats for this have been requested to be put in an admin panelā¦ probably as long as you have mentioned limits (I canāt be bothered to search the bugs as Iām off on a weekend break. Go look yourself). Rocket could have fixed this a long time ago so users could track their usage, but as usual didnāt bother. Or āEnterpriseā.
So donāt blame users for your own failings. They could have helped reduce usage, with the tools.
The cloud account is therefore just tracking, pure & simple.
Next, fix your code that still pumps out large numbers of unnecessary or unwanted notifications (see Aarons thread for my comments, and others, on the large number of wasted ones that you now want me to pay for. I donāt have time to waste on more duplication)
Maybe that will save you more than a few bucks, and a lot of irritation for users.
Fix the problem. Donāt just stick an expensive plaster over it as usual. A plaster you expect people to pay for.
Last, the one that really annoys me.
Limits. You contradict yourself so many times it is embarassing. I donāt have time to quote you on it all right now. Iāll save that for later.
You say we need a login to monitor notifications. But you seem to already know the stats. So why you canāt give us those stats already?
You say 1,000 will cover 70% of users (show us the data).
And 10k 90%?
Those are some odd numbers.
70% of all your users use less than 1000 notifications? A lot of very small users then?
But but butā¦ you also said you only wanted to charge the top few large users.
I already did the maths on this. Either you have a lot of instances with 2 users who donāt talk to one another, or you canāt count. But I donāt know which without the stats.
Lets try something simple for you.
1000 / 20 working days / 5 users = 10 per day.
Seriously? Thatās a ālargeā user? (āWe only want to charge a few of the large usersā)
If it is you have serious issues because youāll earn next to nothing out of them. So I know youāre kidding reallyā¦
My small group sends way more than that, 90% of which we donāt even need because browsers are openā¦ the system is a completely unreliable kludge with no fine grain control.
But the 5 or 10% are really important. How do you work that out?
I wouldnāt say we were high use by any means. We use far more than are needed, but you donāt give us the tools to help ourselves. I canāt mute or limit in any reasonable way. Becauseā¦ see previous. Easier just to charge us, isnāt it?
So somehow nothing adds up. Despite these things being known a long time, they have been ignored. I see lots of excuses and platitudes and jolly bloody hockey sticks, and no real action to deal with any of the issues raised. Two extra weeks? Ooooh. Fab. Iāll take a week off then, and have a week to spare. Joy.
Iām off to chill as you have just completely screwed an otherwise completely awful week and I badly need a drink.
Hopefully your lot will sort out some of the mess they have created before you start ripping them off.
========
āI love deadlines. I like the whooshing sound they make as they fly by.ā
)