Earlier quoted context omitted.
* file uploads in your chat client are misplaced at best, and "rich" environments with formatting and images are 99.999% distractions * channel services can provide archiving and notifications. * scrollback can be handled by a bouncer, yes, but it's up to the IT dept to set it up per-user * there are plenty of usable irc clients for mobile, web, and desktop to satisfy this need. source: Started using telegram/slack b…
> * file uploads in your chat client are misplaced at best, and "rich" environments with formatting and images are 99.999% distractions Nope. They're extremely useful. Just offhand I can think of tons of times we've (a) pasted metric graphs, (b) pasted annotated screengrabs, (c) pasted snippets of code, (d) pasted snippets of test output. None of this is easy in IRC.
We Tried Slack and We Deeply Regretted It (2015)
111–120 of 133 posts
Re: We Tried Slack and We Deeply Regretted It (2015)
#112Earlier quoted context omitted.
> * file uploads in your chat client are misplaced at best, and "rich" environments with formatting and images are 99.999% distractions Nope. They're extremely useful. Just offhand I can think of tons of times we've (a) pasted metric graphs, (b) pasted annotated screengrabs, (c) pasted snippets of code, (d) pasted snippets of test output. None of this is easy in IRC.
But once they're pasted in there, they can only be used there. It's barely harder to upload a file to any myriad of file sharing/hosting services and paste a link which most graphical IRC clients can be configured to auto-expand (and users who don't care/don't want a bunch of images can choose to handle links differently)
I've been on IRC since 1993, and I'm an accomplished programmer. I still find setting up and configuring ZNC and an IRC client complicated, error-error prone, and confusing. And it doesn't always work - sometimes it quits working for no reason and I have to restart things.
Re: We Tried Slack and We Deeply Regretted It (2015)
#113Earlier quoted context omitted.
But once they're pasted in there, they can only be used there. It's barely harder to upload a file to any myriad of file sharing/hosting services and paste a link which most graphical IRC clients can be configured to auto-expand (and users who don't care/don't want a bunch of images can choose to handle links differently)
I want the text snippets to be shown inline. I'm fine with Slack owning the image assets, because I don't have to worry about permissions the way I would if I uploaded them somewhere else (unless it was to some other internal tool). I've been on IRC since 1993, and I'm an accomplished programmer. I still find setting up and configuring ZNC and an IRC client complicated, error-error prone, and confusing. And it doesn'…
Re: We Tried Slack and We Deeply Regretted It (2015)
#114Earlier quoted context omitted.
But once they're pasted in there, they can only be used there. It's barely harder to upload a file to any myriad of file sharing/hosting services and paste a link which most graphical IRC clients can be configured to auto-expand (and users who don't care/don't want a bunch of images can choose to handle links differently)
I want the text snippets to be shown inline. I'm fine with Slack owning the image assets, because I don't have to worry about permissions the way I would if I uploaded them somewhere else (unless it was to some other internal tool). I've been on IRC since 1993, and I'm an accomplished programmer. I still find setting up and configuring ZNC and an IRC client complicated, error-error prone, and confusing. And it doesn'…
Re: We Tried Slack and We Deeply Regretted It (2015)
#115Earlier quoted context omitted.
But once they're pasted in there, they can only be used there. It's barely harder to upload a file to any myriad of file sharing/hosting services and paste a link which most graphical IRC clients can be configured to auto-expand (and users who don't care/don't want a bunch of images can choose to handle links differently)
I want the text snippets to be shown inline. I'm fine with Slack owning the image assets, because I don't have to worry about permissions the way I would if I uploaded them somewhere else (unless it was to some other internal tool). I've been on IRC since 1993, and I'm an accomplished programmer. I still find setting up and configuring ZNC and an IRC client complicated, error-error prone, and confusing. And it doesn'…
Re: We Tried Slack and We Deeply Regretted It (2015)
#116I switched over a large group of friends from using a gazillion hangouts to slack and it's mostly been an improvement. That being said, there's a lot less of us: around 30. I'm definitely disappointed to hear about this. The pricing model sucks for us as well since it means $60 a head to add someone to the friend group if we wanted to pay for slack. If we could pay a fixed price and get a slightly better message hist…
> we had issues with some people not having access at work. Do you know why it happens? Do those companies block Discord as an "unprofessional" website?
Re: We Tried Slack and We Deeply Regretted It (2015)
#117I switched over a large group of friends from using a gazillion hangouts to slack and it's mostly been an improvement. That being said, there's a lot less of us: around 30. I'm definitely disappointed to hear about this. The pricing model sucks for us as well since it means $60 a head to add someone to the friend group if we wanted to pay for slack. If we could pay a fixed price and get a slightly better message hist…
Slack isn't intended for "friends". Their business model is clearly aimed at supporting teams inside businesses. $60 per head is absurd for a tool to chat with friends but pretty reasonable for a business that gets real value from the tool.
+ For all kinds of "Work"
+ For teams of all types and sizes
+ Bringing people together to make them productive
Compare that to the messaging for say Hipchat:
+ "Team chat built for business"
+ Enterprise features
+ Loved by your IT team
(Edit - Formatting)
Re: We Tried Slack and We Deeply Regretted It (2015)
#118Earlier quoted context omitted.
I contend that my question was slightly snarky. As someone who moves from computer to computer a lot, having a unified client is quite critical. With IRC and Bitleebee, I can combine a lot of protocols in one client, keep it running in a screen, and access it via SSH. I realise my setup is hardly common, and I contend that the main issues with IRC are the clients and the account systems. However , both those issues (…
> With IRC and Bitleebee, I can combine a lot of protocols in one client, keep it running in a screen, and access it via SSH. At which point you're not really using IRC. You're using the Bittleebee-commands-over-SSH protocol. This protocol has a number of issues: it requires having a server with a unix user account running on it (which is a massive attack surface, no-one can offer a server like that for free or it wi…
As for Slack's IRC gateway, I think it's pretty decent, yes. I personally prefer it to Slack's own client (again, that's just me). But this is what bothers me about Discord, because that doesn't offer an IRC gateway, and I am forced to use their client(s).
And if you're like me - which apparently few are - and you are in many different communities, that use different protocols to communicate, having a bunch of different clients just means more hassle.
Re: We Tried Slack and We Deeply Regretted It (2015)
#119How to view Medium pages on Safari Mavericks without crashing the browser? It's been happening for weeks.
Try blocking Javascript for medium.com? I'm sure there's a plugin for that, but use Firefox for general browsing on all platforms where it's a thing, so can't make a specific recommendation. I do have the same problem in Safari on iOS 9.3.5, but I suppose that must have tab isolation, since the whole browser doesn't go down.