Dibs On Stuff: advanced queuing for Slack and Discord
@dibsonstuff.com
The official Dibs On Stuff feed. Tune in for all your Dibs-related mischief!
https://dibsonstuff.com
https://conchable.slack.com/marketplace/AT3N0PJUB-dibs-on-stuff
https://dibsonstuff.com
https://conchable.slack.com/marketplace/AT3N0PJUB-dibs-on-stuff
Ideas for Discord API:
* Custom validation errors in modals would be nice
* Overflow menu buttons w-b-nice
* Dropdowns that permit free-form text entry w-b-nice
ps: btw allowing JSON responses, rather than new POSTs to endpoint is awesome, TY! (also faster UX for the user)
#discord #discordapi
* Custom validation errors in modals would be nice
* Overflow menu buttons w-b-nice
* Dropdowns that permit free-form text entry w-b-nice
ps: btw allowing JSON responses, rather than new POSTs to endpoint is awesome, TY! (also faster UX for the user)
#discord #discordapi
September 23, 2025 at 1:22 AM
Ideas for Discord API:
* Custom validation errors in modals would be nice
* Overflow menu buttons w-b-nice
* Dropdowns that permit free-form text entry w-b-nice
ps: btw allowing JSON responses, rather than new POSTs to endpoint is awesome, TY! (also faster UX for the user)
#discord #discordapi
* Custom validation errors in modals would be nice
* Overflow menu buttons w-b-nice
* Dropdowns that permit free-form text entry w-b-nice
ps: btw allowing JSON responses, rather than new POSTs to endpoint is awesome, TY! (also faster UX for the user)
#discord #discordapi
Also: It must have been pretty painful to do a single-customer data restore from a backup. (Believe me I know). So, many, many, thank-yous to the patient Slack engineers 💖💖💖
April 16, 2025 at 12:31 AM
Also: It must have been pretty painful to do a single-customer data restore from a backup. (Believe me I know). So, many, many, thank-yous to the patient Slack engineers 💖💖💖
2025-04-16 09:30 (GMT+10)
We've reached out to the initial customer who reported the issue and offered them some merch from the shop.dibsonstuff.com store, and it looks like that's the end of the adventure. Phew.
Lesson learned: **never change anything ever again.** 👻
We've reached out to the initial customer who reported the issue and offered them some merch from the shop.dibsonstuff.com store, and it looks like that's the end of the adventure. Phew.
Lesson learned: **never change anything ever again.** 👻
Products
Shop for Dibs On Stuff gear, t-shirts and fun
shop.dibsonstuff.com
April 16, 2025 at 12:30 AM
2025-04-16 09:30 (GMT+10)
We've reached out to the initial customer who reported the issue and offered them some merch from the shop.dibsonstuff.com store, and it looks like that's the end of the adventure. Phew.
Lesson learned: **never change anything ever again.** 👻
We've reached out to the initial customer who reported the issue and offered them some merch from the shop.dibsonstuff.com store, and it looks like that's the end of the adventure. Phew.
Lesson learned: **never change anything ever again.** 👻
2025-04-16 08:00 (GMT+10)
So, root cause: Slack have a limit of 10 apps for Free plan. When I downgraded from Pro they nuked our apps in our single Slack instance. Ok fine. **But also destroyed any apps we'd created.**
They acknowledged that it was a serious error and that they're fixing it asap.
So, root cause: Slack have a limit of 10 apps for Free plan. When I downgraded from Pro they nuked our apps in our single Slack instance. Ok fine. **But also destroyed any apps we'd created.**
They acknowledged that it was a serious error and that they're fixing it asap.
April 16, 2025 at 12:26 AM
2025-04-16 08:00 (GMT+10)
So, root cause: Slack have a limit of 10 apps for Free plan. When I downgraded from Pro they nuked our apps in our single Slack instance. Ok fine. **But also destroyed any apps we'd created.**
They acknowledged that it was a serious error and that they're fixing it asap.
So, root cause: Slack have a limit of 10 apps for Free plan. When I downgraded from Pro they nuked our apps in our single Slack instance. Ok fine. **But also destroyed any apps we'd created.**
They acknowledged that it was a serious error and that they're fixing it asap.
2025-04-16 08:00 (GMT+10)
Slack restored the app from a backup. We can see it again. We can administrate it again. It can be installed again. It shows up in the Slack Marketplace. It shows up in the Brilliant Bots page. The crick in my neck suddenly releases.
Slack restored the app from a backup. We can see it again. We can administrate it again. It can be installed again. It shows up in the Slack Marketplace. It shows up in the Brilliant Bots page. The crick in my neck suddenly releases.
April 16, 2025 at 12:21 AM
2025-04-16 08:00 (GMT+10)
Slack restored the app from a backup. We can see it again. We can administrate it again. It can be installed again. It shows up in the Slack Marketplace. It shows up in the Brilliant Bots page. The crick in my neck suddenly releases.
Slack restored the app from a backup. We can see it again. We can administrate it again. It can be installed again. It shows up in the Slack Marketplace. It shows up in the Brilliant Bots page. The crick in my neck suddenly releases.
2025-04-16 04:11 (GMT+10)
Slack support had internally escalated and let us know that help was on the way. 🐎
Slack support had internally escalated and let us know that help was on the way. 🐎
April 16, 2025 at 12:20 AM
2025-04-16 04:11 (GMT+10)
Slack support had internally escalated and let us know that help was on the way. 🐎
Slack support had internally escalated and let us know that help was on the way. 🐎
2025-04-15 19:30 (GMT+10)
We started digging through logs to try and figure out which clients were impacted so we could reach out to them.
Curiously, the logs were still thundering along. The ghost app was still working away and no other customers reached out to us.
What the heck was going on?
We started digging through logs to try and figure out which clients were impacted so we could reach out to them.
Curiously, the logs were still thundering along. The ghost app was still working away and no other customers reached out to us.
What the heck was going on?
April 16, 2025 at 12:19 AM
2025-04-15 19:30 (GMT+10)
We started digging through logs to try and figure out which clients were impacted so we could reach out to them.
Curiously, the logs were still thundering along. The ghost app was still working away and no other customers reached out to us.
What the heck was going on?
We started digging through logs to try and figure out which clients were impacted so we could reach out to them.
Curiously, the logs were still thundering along. The ghost app was still working away and no other customers reached out to us.
What the heck was going on?
2025-04-15 17:30 (GMT+10)
The full realization of how badly it was going to suck if hundreds of Slack Workspaces were going to be impacted was beginning to set in. We offered up every tiny little idea we could come up with to Slack support.
You may have detected a note of desperation in my tone 😅
The full realization of how badly it was going to suck if hundreds of Slack Workspaces were going to be impacted was beginning to set in. We offered up every tiny little idea we could come up with to Slack support.
You may have detected a note of desperation in my tone 😅
April 16, 2025 at 12:16 AM
2025-04-15 17:30 (GMT+10)
The full realization of how badly it was going to suck if hundreds of Slack Workspaces were going to be impacted was beginning to set in. We offered up every tiny little idea we could come up with to Slack support.
You may have detected a note of desperation in my tone 😅
The full realization of how badly it was going to suck if hundreds of Slack Workspaces were going to be impacted was beginning to set in. We offered up every tiny little idea we could come up with to Slack support.
You may have detected a note of desperation in my tone 😅
2025-04-15 09:30 (GMT+10)
Support mentioned the date of the deletion. It would turn out to be a vital clue. It coincided with when we had made a Slack plan change on the 9th.
We had temporarily enabled the Pro plan to experiment with Workflow Builder Steps for Dibs (it didn't pan out).
Support mentioned the date of the deletion. It would turn out to be a vital clue. It coincided with when we had made a Slack plan change on the 9th.
We had temporarily enabled the Pro plan to experiment with Workflow Builder Steps for Dibs (it didn't pan out).
April 16, 2025 at 12:13 AM
2025-04-15 09:30 (GMT+10)
Support mentioned the date of the deletion. It would turn out to be a vital clue. It coincided with when we had made a Slack plan change on the 9th.
We had temporarily enabled the Pro plan to experiment with Workflow Builder Steps for Dibs (it didn't pan out).
Support mentioned the date of the deletion. It would turn out to be a vital clue. It coincided with when we had made a Slack plan change on the 9th.
We had temporarily enabled the Pro plan to experiment with Workflow Builder Steps for Dibs (it didn't pan out).
2025-04-15 08:30 (GMT+10)
Slack support got back to us. Unfortunately the news was not good: Someone had deleted Dibs On Stuff. Like the app itself had been destroyed. Literally hundreds of Slack Workspaces were going to be impacted. It was suggested that maybe someone at our end had deleted it.
Slack support got back to us. Unfortunately the news was not good: Someone had deleted Dibs On Stuff. Like the app itself had been destroyed. Literally hundreds of Slack Workspaces were going to be impacted. It was suggested that maybe someone at our end had deleted it.
April 16, 2025 at 12:12 AM
2025-04-15 08:30 (GMT+10)
Slack support got back to us. Unfortunately the news was not good: Someone had deleted Dibs On Stuff. Like the app itself had been destroyed. Literally hundreds of Slack Workspaces were going to be impacted. It was suggested that maybe someone at our end had deleted it.
Slack support got back to us. Unfortunately the news was not good: Someone had deleted Dibs On Stuff. Like the app itself had been destroyed. Literally hundreds of Slack Workspaces were going to be impacted. It was suggested that maybe someone at our end had deleted it.
2025-04-14 23:33 (GMT+10)
We noticed that our logs were still scrolling past happily. Dibs was still being used aggressively, but **we** didn't have access to it anymore.
Neither in the Slack Marketplace, nor to make config changes ourselves.
It had become a GHOST app! 👻
We noticed that our logs were still scrolling past happily. Dibs was still being used aggressively, but **we** didn't have access to it anymore.
Neither in the Slack Marketplace, nor to make config changes ourselves.
It had become a GHOST app! 👻
April 16, 2025 at 12:11 AM
2025-04-14 23:33 (GMT+10)
We noticed that our logs were still scrolling past happily. Dibs was still being used aggressively, but **we** didn't have access to it anymore.
Neither in the Slack Marketplace, nor to make config changes ourselves.
It had become a GHOST app! 👻
We noticed that our logs were still scrolling past happily. Dibs was still being used aggressively, but **we** didn't have access to it anymore.
Neither in the Slack Marketplace, nor to make config changes ourselves.
It had become a GHOST app! 👻
2025-04-14 18:12 (GMT+10)
We reported the issue to Slack support. Mentioned that it was urgent and added some downtime notices to our homepage.
We had recently jumped through some hoops to try to enable Dibs as an Org-level Slack app... could that have been the problem?
We reported the issue to Slack support. Mentioned that it was urgent and added some downtime notices to our homepage.
We had recently jumped through some hoops to try to enable Dibs as an Org-level Slack app... could that have been the problem?
April 16, 2025 at 12:10 AM
2025-04-14 18:12 (GMT+10)
We reported the issue to Slack support. Mentioned that it was urgent and added some downtime notices to our homepage.
We had recently jumped through some hoops to try to enable Dibs as an Org-level Slack app... could that have been the problem?
We reported the issue to Slack support. Mentioned that it was urgent and added some downtime notices to our homepage.
We had recently jumped through some hoops to try to enable Dibs as an Org-level Slack app... could that have been the problem?
2025-04-14 17:58 (GMT+10)
A customer informed us that Dibs was no longer in the Slack Marketplace and couldn't be installed. Indeed it no longer appeared in searches and it appeared that Dibs was completely unavailable to use.
It was beginning to look like the first real downtime in 4 years.
A customer informed us that Dibs was no longer in the Slack Marketplace and couldn't be installed. Indeed it no longer appeared in searches and it appeared that Dibs was completely unavailable to use.
It was beginning to look like the first real downtime in 4 years.
April 16, 2025 at 12:09 AM
2025-04-14 17:58 (GMT+10)
A customer informed us that Dibs was no longer in the Slack Marketplace and couldn't be installed. Indeed it no longer appeared in searches and it appeared that Dibs was completely unavailable to use.
It was beginning to look like the first real downtime in 4 years.
A customer informed us that Dibs was no longer in the Slack Marketplace and couldn't be installed. Indeed it no longer appeared in searches and it appeared that Dibs was completely unavailable to use.
It was beginning to look like the first real downtime in 4 years.