Earlier quoted context omitted.
1gb of ram for an IRC client.... I don't know... :|
Try out eul: https://eul.im It's a native desktop client for Slack, Skype, Slack, Facebook, etc. It's only 4 MB, it has minimal CPU usage, and it can handle hundreds of thousands of messages without lag.
Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
101–110 of 155 posts
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#102I wish this was forked instead of killed. Everytime I use Screenhero, it has been butter smooth. I would be ready to pay $3/month for screenhero standalone or a pay-per-use. I'm not interested in Slack, the use cases are clearly different. I think Slack missed or rather killed an opportunity here, they could have kept Screenhero (and use it to upsell Slack) and also integrated it in Slack. Not only that but it took t…
Have you tried Discord? It's geared towards gamers but it's got most of the features we needed from Slack. More info: https://support.discordapp.com/hc/en-us/articles/11500098275...
[0]: https://twitter.com/i/web/status/903663357210841088?lang=en
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#103Earlier quoted context omitted.
> Slack: please keep the stand-alone ScreenHero until you make the integrated one have the same performance. Given the shitty performance of the Slack desktop client (which basically only does IRC with gifs and emoji), I'm not too confident in their ability to improve the performance of, well, anything.
1gb of ram for an IRC client.... I don't know... :|
[0]: https://get.slack.help/hc/en-us/articles/201727913-Connect-t...
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#104Earlier quoted context omitted.
i wonder if screenhero's smoothness had anything to do with it being stuck in invite-only limbo. when you have tight control on how many people are using your app, you don't really have to solve infrastructure scaling problems yet.
It wasn't P2P? Yikes...
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#105I wish this was forked instead of killed. Everytime I use Screenhero, it has been butter smooth. I would be ready to pay $3/month for screenhero standalone or a pay-per-use. I'm not interested in Slack, the use cases are clearly different. I think Slack missed or rather killed an opportunity here, they could have kept Screenhero (and use it to upsell Slack) and also integrated it in Slack. Not only that but it took t…
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#106Really disappointing news, rolling Screenhero into Slack doesn't solve the same problem at all. I work for myself and have a large contact list of people who don't know each other who I often pair with or screenshare with. With Slack, there's really no way for me to create the same setup. I'd need to create a new team called "Adam's Screenhero Contacts", invite all of my contacts (who don't know each other) to be par…
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#107I hope it's stable. Slack's audio/video conferencing is not exactly... smooth.
In fact, it still boggles my mind that in 2017, conferencing is still in the stone ages when it comes to reliability.
With Slack I often either get a one-way connection (only one party can hear the other) or the call is unable to connect, claiming that "Bob ended the call". Meetings tend to start with five minutes of "Can you hear me? Hello? Testing, testing..." until we either are able to get a connection, or we give up and move to Skype, which isn't perfect, but much more reliable.
Incredibly, it also turns out that if you try calling someone who's already calling you on Slack, you get a busy error! How insane is that? We were both trying to reach each other, both expressing — in terms of UI — the exact same intent, and the app interprets that as a conflict.
There's also some pretty shoddy intergration between the desktop and mobile app. Recently, I tried talking to a colleague, and we went through all of the above insanity, but at one point, as he was calling me, Slack on my phone was ringing, but the desktop app wasn't. Some of these bugs are hard to understand.
My company's go-to solution the last couple of years has been GoToMeeting, which is 99% rock solid, but doesn't integrate well with anything, and doesn't have a good mobile app. The biggest benefits to GTM are the ability to record meetings, and the ability to dial in through a normal phone. The latter feature has saved is a lot of times when one person has been on a bad Internet connection.
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#108This is highly appreciated (as someone who never got an invite to Screenhero, so was never able to compare)! I hope it's stable. Slack's audio/video conferencing is not exactly... smooth. In fact, it still boggles my mind that in 2017, conferencing is still in the stone ages when it comes to reliability. With Slack I often either get a one-way connection (only one party can hear the other) or the call is unable to co…
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#109Really disappointing news, rolling Screenhero into Slack doesn't solve the same problem at all. I work for myself and have a large contact list of people who don't know each other who I often pair with or screenshare with. With Slack, there's really no way for me to create the same setup. I'd need to create a new team called "Adam's Screenhero Contacts", invite all of my contacts (who don't know each other) to be par…
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#110Earlier quoted context omitted.
1gb of ram for an IRC client.... I don't know... :|
Except they actually have IRC and XMPP gateways available if you're RAM constrained or are a console cowboy type.[0] [0]: https://get.slack.help/hc/en-us/articles/201727913-Connect-t...