81–90 of 112 posts
Earlier quoted context omitted.
Yes
Please tell guys who is responsible for js engine to fix handling of large cookies that google is using to slow down youtube on firefox. It is impossible to watch youtube logged in because of that. God bless you sir.
Why is a SaaS locking out a fairly high-profile customer like this, and publicly airing B2B accounts-receivable drama, to the customer's community? How big can the bill be, for something you could run on a 20 year-old PC? Given the strange coincidence with the social media outrage over TOU fiasco, I don't know who to be scratching my puzzled head at here.
Easily 7 figures, possibly 8 figures. Enterprise sales are a weird realm.
The comments here are hilarious. So many people getting on their soapbox about someone forgetting to pay a bill. Something that has undoubtedly happened at your organisation, and happens at most, given enough time. This website fucking sucks.
Earlier quoted context omitted.
Once they figure it out, they can come back as a paying customer. :) It's not the provider's responsibility to help their customer get their sh#t together.
This is a fine attitude to have if your problem is that you have too many customers.
This doesn't feel like an oversight or an accident. It'll be interesting to see how they try to explain this away.
As reported by parts of the tech press this last year, Mozilla is seemingly on its way to certain bankruptcy. I guess we should expect more incidents like this the time to come.
Please don't read too much into this ;) We moved from self-hosted Discourse to hosted Discourse. The transfer was initiated late from the Mozilla side (my bad) and the automatic system from Discourse kicked in.
Thanks for the explanation! Is there any chance to move away from the Discourse? It's a bit too slow (on any page opening), but the biggest issue is its hostile habit of catching the browser "find in page" hotkey (replacing the local find with the remote site search).
Still wish pages would stop hijacked hot-keys in the first place, but hope this helps.
Very unprofessional of Discourse to publicly shame a client like this. If they are not being paid and they care so much about the cost they should bring the website down instead of resorting to petty shaming.
Also consider that those types of things happen after several rounds of ignored warnings.
As reported by parts of the tech press this last year, Mozilla is seemingly on its way to certain bankruptcy. I guess we should expect more incidents like this the time to come.
More of you switch to data-harvesting Chromium derivatives and scams, and we'll have no true alternative browser, the only one that is Manifest V2 compatible.
Could you provide a reason why that is a feature?
All the extensions I’ve implemented runs fine as V3 manifests, and they allow much more fine-grained security permissions. That’s something I’m happy with, even as a developer. It limits the security impact of whatever flaws my extension may have.
Earlier quoted context omitted.
They will tell you it must have slipped though the cracks, and that they'll get right on it, but no payment will materialize.
That doesn’t mean you get to skip that step though