Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

slackhq.com

Post reply on HN
Print view View original

81–90 of 155 posts

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#81

Post by JadoJodo »

jsherwani wrote: post #13
adamwathan wrote: post #6

Really 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…

There is a way for each individual to pay for their Slack account: Shared Channels! https://slackhq.com/introducing-shared-channels-where-you-ca...

This doesn't solve it either, however. As an example, if I'm friends with 5 people who each have this setup, I'll have to pay to belong to each of their 5 separate shared Slack channels. And they would need to do the same for each of THEIR friends.

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#82

Post by degenerate »

Mindstormy wrote: post #22

I use screenhero daily for work and I am incredibly sad to see it go, even though we all knew this day was coming. It hits even harder for me since my company just moved us off of slack due to their lack of hippa compliance and cost issues, so not only is the standalone screenhero gone, I've lost the ability to use it in slack too. Does anyone have a good suggestion for an alternative?

Mattermost, the (leading?) Slack open-source alternative, seems to be HIPAA compliant if you know what you are doing:

https://docs.mattermost.com/overview/security.html#hipaa-com...

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#83

Post by timdorr »

amedvednikov wrote: post #73
mk89 wrote: post #67

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.

Probably should disclose that you make it: https://github.com/eul-im

Also, given that it's not open source, I can't trust it with my private Slack teams. I would seriously consider making the source open. You can still charge for it (and I'd love to pay for it!), but I need assurance that it's not doing anything untoward. Perhaps a Patreon level that includes source code access?

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#84

Post by michaelmrose »

amedvednikov wrote: post #73
mk89 wrote: post #67

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.

Why does it need to "download embedded browser" as part of setup?

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#85

Post by twothamendment »

eikenberry wrote: post #17
giovannibajo1 wrote: post #5

When is videocalling and screensharing coming to Linux?

Slack's beta Linux client already supports video calling and screen sharing.

It "works" for me, but my "screen" is virtual - so slack wants to share both monitors as one big screen. So yes, it works, but not for my setup. It isn't useful. Being able to pick which monitor or app to show would make it useful. Being able to share the current app, whatever that is would be awesome.

It has driven me to use google meet - which seems to be more stable and doesn't bog down my system.

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#86

Post by dkersten »

jsherwani wrote: post #14
tedmiston wrote: post #7

Screenhero is hands down the best (smoothest) screen sharing app I've ever used. It's bittersweet to see them acquired by Slack as a paid only feature, but I'm happy for the team and it seems like a very ideal kind of acquisition where they solve a problem Slack has and wasn't solving well, and then Slack can scale the Screenhero userbase overnight. Edit: I just tried this feature in Slack with /call then enabling ot…

Screenhero co-founder here. We're committed to making Slack Calls better, and have a number of upcoming improvements in the works.

Thanks for making screenhero, it’s been one of my most used applications and I love it. I would have gladly personally paid a monthly subscription for it. But this news makes me very sad. Slack runs like garbage — it’s slow, it has CSS rendering issues (for a desktop app... ugh) every so often, it uses waaay too much RAM (I’ve had it use 4gigs... I’m sorry but chat is never the primary thing I do on my computer, that is not acceptable) — the slack track record when it comes to performance has been pretty bad, so forgive me if I don’t hold my breath. I hope I’m wrong...

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#87

Post by michaelmrose »

amedvednikov wrote: post #73
mk89 wrote: post #67

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.

Its disingenuous to claim its 4MB when the first thing it does when you run it is download 500MB of data in order to function.

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#88

Post by tomsmeding »

timdorr wrote: post #83
amedvednikov wrote: post #73

Earlier quoted context omitted.

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.

Probably should disclose that you make it: https://github.com/eul-im Also, given that it's not open source, I can't trust it with my private Slack teams. I would seriously consider making the source open. You can still charge for it (and I'd love to pay for it!), but I need assurance that it's not doing anything untoward. Perhaps a Patreon level that includes source code access?

Having the source but not building it yourself doesn't rule out that the compiled app actually has different source than the code you got. So having the source but having it rely on some complex or irreproducible build system is not enough for open source here.

Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)

#90

Post by aaronbrager »

elsif1 wrote: post #78
adamwathan wrote: post #6

Really 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…

I think single channel guests would work?

Yeah it would be a little obnoxious but I think it would work
Post reply on HN