If you manage a public Slack/Discord that has a jobs channel, or anything similar, you are very likely to be spammed by a company called Outhire[.]ai. They are supposedly an "AI powered" hiring platform, but really what that means is they automate creating accounts for you on Discord, Slack, Reddit, and more, and then spam the shit out of the platforms.
They're easy to spot: they all post links to outhire[.]ai and their email addresses are all [name]@outhire[.]ai.
really dislike the #slack update that removed the sticky thread pane. now it's bound per channel, so in order to reference a message of a thread from another channel i now have to switch between different channels...
really what i want is decent messaging apps that let me have multiple windows for separate channels when i need it to. this is one of the few things telegram desktop gets right
Does anyone know if there are any #slack groups or something of the kind for #aws ? Where do you go for help when the AWS documentation doesn’t have the answer? (Which in my experience is VERY often)
Is there an example somewhere how to send Slack messages (including rich text, and tagging users) in JavaScript (to be more precise in AWS Lambda)? I'd receive channel name and user IDs as parameters and the code should be flexible enough to use those channels and users.
@counteractor@jdp23 there's merit in sticking to your lane when it comes to deciding what kind of app you want to be. You can do all things kinda crappily, or do a few things really really well.
Some quick examples:
NodeBB is a forum first, and a chat second (chats were replacements for older forums' DM systems)
#Discord and #Slack started building out threading/forum-style functionality. Arguably, it leaves much to be desired.
holy fuck #Slack's API doesn't have a single unique ID for an individual messages, messages are identified by the ID of a channel, thread, or DM and a unix timestamp (as a string, in the timezone of the slack workspace (i think?)).
you have got to be joking me, this API is such a mess.
Oh, Slack have removed Split view - that's a great decision... NOT!
I used split view a lot so I can be in a thread whilst checking another channel - being in DevOps I need that as a lot of things can be happening at the same time.
Now they have changed it so if you move out of a channel the thread is automatically closed.
You now have to open another window to keep it open...
I love the fact that the CEO of #Portainer jumped into my thread on #Slack to give me a hand on getting it up and running properly the other day on #DockerSwarm. 🙌🏼💛
Admittedly I'm becoming increasingly frustrated that folks can go on and on about the evils of Reddit and yet continue to sequester all the knowledge about their interests and hobbies in obscure chats, allowing Reddit to go uncontested in being the source of publicly accessible info on some of those topics.
Yes I know there's definitely an element of "and yet you participate in society" in this, but that doesn't really lessen the frustration.
I use the kebab menu “Remind me about this” all the time on messages I need to act on, but the old way of getting a ping in a PM made it easy to miss if you didn’t act immediately.
Now it’s super clear what’s coming up and what’s due, and easy to resolve or snooze.
There’s nothing more cringeworthy to me in #Slack than people posting text in Screenshot form, specially if my response would naturally lead to copy/paste.
Wrote a post about using Vencord's injection methods with Discord client modding on Slack's desktop client. Gonna write some plugins for Slack within time :p
Elon Musk is threatening to end his $44 billion agreement to buy Twitter, accusing the company of refusing to give him information about its spam bot accounts.