731–740 of 809 posts
It's pretty hilarious that first Stewart Butterfield tried to make an MMO (Game Neverending), failed at that, and ended up making a fortune on the spinoff, Flickr. Then he tried to make another MMO (Glitch), failed at that, and ended up making a fortune on the spinoff, Slack. I hope he tries to make another MMO.
I just want him to set aside a fund for remaking glitch. The most ambitiously cooperative mmo I ever played. I miss it everytime I think about it :(
Well deserved. Their product-vision was clear, their execution focused on what mattered... and they didn't need to bend or break laws to succeed. It's easily my favorite unicorn of the past decade.
I think the whole argument of "unicorns exploiting legal grey areas" falls victim to Hanlon's razor. I don't really believe these companies set out to bend or break any laws, it was more a case of the legal system not catching up fast enough. Uber started as a service to hire limousines, not a platform company. If governments weren't so concerned with party politics, infighting and staving off populist surges, we'd p…
They didn't start as a company for the sole purpose of exploiting legal grey areas, but they certainly have consistently done so since their inception.
Happy for the people that built it, with the idea of improving what the chat was. Sad for the internet, because we were better in the 1980s with an open standard like IRC, and gradually the internet community lost the ability to adapt their old open protocols for the future.
There's moe to it, but this is definitely a factor.
Earlier quoted context omitted.
It's not as disastrous as this person makes it seem. It's a rest call you can use to have slackbot do or say whatever you want for integration purposes. You can customize the name of the bot as well as its icon, which would allow you to "impersonate" someone. The slackbot has limitations in that it looks different from a regular user and will identify it as slackbot if you click on it, as well as tell you who created…
And since we're talking about Slack's use in business, if someone does that you fire them. It might be a problem for people using the free version to host public communities, but that's not Slack's target market.
> t might be a problem for people using the free version to host public communities, but that's not Slack's target market.
But these two are not mutually exclusive. Many business use cases eventually require a public community chat, and Slack is a dead-end for them. Discord on the other hand has served us well.
Earlier quoted context omitted.
> DCC allows one to send files and since it's a direct connection since it's a direct connection it will never work in our modern nat'd/firewalled world, even between company branches (unless you have the whole company in the same VPN - but yeah don't do that) Yes Jira is ok, it's just the target of (some) unfair hate like slack
Are you sure? Wouldn't it be a direct connection, just between two NAT gateways? With each using the ports to track which connection belonged to the host behind the NAT?
Earlier quoted context omitted.
> So now I've lost a bunch of my communications due to others' choices that I had little control over. I wrote a simple exporter using Slack api. It archives Slack from position of user, almost everything (like attachments). But I'm not publishing it on GitHub because I don't want more people to use it, and don't want Slack to block mass api calls, and don't want slacks admins to know I written it and use it.
Your exporter goes beyond the 10k limit for DMs on a free plan?
Slack is great. The valuation makes sense and I wish them continued success. All the integrations, and workflows that Slack has enabled for our company make us more productive. I would hate to go back to what came before it. IRC is complete trash and I don't know why anyone would use it in the same sentence as Slack. UX matters. It matters A LOT.
Slack is one of the most bloated apps on my computer, and my smartphone. On both, it takes seconds to boot, and that's just to load the local cache. Syncing with the main server takes a few more seconds. It has some good UI patterns. But overall, it's heavy and slow. It takes longer to load than the previous chat clients I used.
Earlier quoted context omitted.
Not that it really matters much, but a lot of the design issues you're highlighting are due to the age of the software and Atlassian's seeming commitment to not breaking backward compatibility. In particular, Jira predates Markdown, so the software adopted the text formatter of the day, which was textile[0]. This is where the `bq.` syntax comes from. Jira didn't invent it from whole cloth -- it was adopted because th…
That's a helpful comment. Nevertheless bq. commitment to not breaking backward compatibility Backward compatibility with what? People's brains? We're talking about markup language and rendering right, which is not an API consumed by machines. bq. it's hardly the case that they hired a bunch of inept engineers. So why is the new "Visual Mode" WYSIWYG text entry mode so terrible? And why that absurd "link" icon in the…
As for the link issue, I'm not entirely sure what you're referring to. I have an icon that looks like the Android "share" icon and that drops down a dialog with a link to the current page and a target user field. The link icon in the text entry field just adds a textile formatted link. I'm probably just overlooking something, but I'm not seeing what you described. And I never use the visual editor, so I can't speak to its quality.
I should note that I don't work for Atlassian and never have, so I don't have a horse in this race. But I have been using Jira since maybe 2004 due to its early adoption by the Apache Software Foundation. Jira is hardly perfect, but it's the least bad issue tracker I've used. At some level, I'm sure it's just a matter of preference. E.g., I know plenty of people that laud the GitHub issue tracker and I don't get it. It works well enough for small projects, but is too limiting for any project of non-trivial size, IMHO. I also find more than 2 or 3 labels in the issue list to just be a distracting sea of colors.
I hope you're able to find something that works well for you. I'll add that if you're using an on-premise version of Jira in your company, there's a high likelihood that you're running a dated release. I've found that some of the more aggravating issues people run into have actually been fixed, but not deployed in their environment. If you can find access to a running instance of the latest version, you might find it to be a more less frustrating experience.
Earlier quoted context omitted.
so does IRC. I believe even if it adopted IRC as a protocol, slack would still be successful, it's all about the UI being dumb-proof, friendly and capable and seemingly in-vogue. Discord, even more.
>it's all about the UI being dumb-proof Make something idiot-proof and the world will make a better idiot. And it looks like I'm the bigger idiot here because I don't understand the interface at all. I'm in two servers for two open source projects but my ID seems to be different for the two servers and not federated for some reason. Or is it? I don't really know. ¯\_(ツ)_/¯