#4747 closed enhancement (fixed)
Feature Request: Expose/promote subchannels using /here by reposting to #core
Reported by: | garrett-eclipse | Owned by: | dd32 |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Communication (Matrix, Slack, IRC) | Keywords: | has-patch |
Cc: |
Description
Hello,
Just an idea, not sure if possible or if there's much merit.
Was thinking as many Slack users aren't aware of all the channels it would be nice to give them a little exposure especially when they have meetings and bug scrubs by posting a snippet of their /here
call to #core for example. Or #meta, etc for other channel types.
So a bug scrub starting in #core-privacy would put a little note/link on #core to let others know about it happening.
I feel especially for the smaller or newer components like Site Health, etc this could ellicit more participants.
Thank you
Attachments (6)
Change History (31)
This ticket was mentioned in Slack in #core by dd32. View the logs.
5 years ago
#3
@
5 years ago
- Owner set to dd32
- Resolution set to fixed
- Status changed from new to closed
In 9216:
#4
@
5 years ago
The response in #core was good, so lets try this out.
[9216] implements this, but is 80% untested as I couldn't quite get slack to play nicely with me without actually putting it in production.
I'm hopeful that it'll work, and I'll try to be around in ~7hrs when it should be triggered.
If it doesn't quite work, reverting shouldn't be needed unless it broadcasts badly to the parent channel.
#5
@
5 years ago
We may want to require a minimum message length (either characters, or words) before posting the parent channel to encourage everyone to use a reasonably descriptive and helpful notification.
#7
@
5 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Here's an example of it happening overnight in #core: https://wordpress.slack.com/archives/C02RQBWTW/p1571666411454100 (Attached above)
That's an example of a /here
that lacks context, the first line of the following message would've been better as the broadcast.
That's a good example of why multiple words being a requirement for an "upstream broadcast" makes sense IMHO.
Thoughts?
#8
@
5 years ago
That's a good example of why multiple words being a requirement for an "upstream broadcast" makes sense IMHO.
Potentially even as part of the /here
command - Require it be at least two words?
#11
@
5 years ago
Thanks @dd32 this is awesome, look forward to seeing it pop up more in #core. I agree having a minimum word count of 2+ seems to make sense to me and reduce spammy messaging.
#12
@
5 years ago
- Keywords 2nd-opinion removed
- Resolution set to fixed
- Status changed from reopened to closed
I'm going to close this as fixed.
After some thinking, I don't think we should implement controls on /here
such as needing multiple words, I think that'd be better done through documentation of best practices. As others see the short broadcasts they should get the idea of adding a helpful description :)
@psykro is drafting up some documentation for the slash commands and how to use them, what they do, how to get whitelisted, etc. which should handle that well enough.
@
5 years ago
Failure to perculate up to #core with 500 error. Still posted to the current channel though
#13
@
5 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Hi @dd32 this seems to be a fairly successful feature. People seem to be enjoying it (screen) and I've personally found we're getting more people to participate in #core-privacy
One minor issue that cropped up today when I attempted the following command was a 500_service_error reported by Slackbox (screen), the command;
/here Come join Privacy Office Hours and we’ll continue our discussions on the Consent API and Disclosures tab
Reopening, but might just turn out to be a service disconnection. Or possibly I went beyond the string length limit?
#14
@
5 years ago
- Resolution set to fixed
- Status changed from reopened to closed
Unfortunately there aren't any logs for webhook deliveries from Slack, and no PHP fatals/warnings were generated on our side here from what I can see.
I suspect this may have been a temporary interruption or something on Slacks side.
If it happens more often, I'll look into it, but as it is, it's seemingly working..
This ticket was mentioned in Slack in #accessibility by sergey. View the logs.
5 years ago
This ticket was mentioned in Slack in #meta by garrett-eclipse. View the logs.
5 years ago
#23
@
5 years ago
- Keywords has-patch added
@SergeyBiryukov / @JeffPaul I provided a patch to add #tide to annoucements in #core.
4747.tide.diff is the basic patch
4747.tide.switch.diff is an alternate that changes the if-else block to a switch.
This seems like a good idea to me, and I can see it working well for
#meta
.I would assume that it would drop the
@
here
part for the 'parent' channel and just have the text, or even just have it quote the message from the other channel using Slacks message embed functionality.If there's any form of buy-in from the
#core
team then lets make this happen. I primarily want to make sure that adding this doesn't cause noise that is unwanted in the channels.Marking this as
2nd-opinion
only to gather extra feedback.