Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jsherwani
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
jsherwani
5y ago
Related anecdote: Screenhero's UI was originally totally native on the two platforms we supported (Mac and Windows). It was a night-and-day improvement (it looked better, had fewer bugs, was easier to build and maintain) when we moved
32.
▲
by
jsherwani
5y ago
We're pushing out a fix for the back button as I speak, thanks for the heads up! It should be live in ~10 minutes (CI build + test + deploy). Discord: we haven't looked into their API yet, but it's an oversight on our part. W
33.
▲
by
jsherwani
5y ago
Thanks for the heads up on Firefox/iOS — we'll take a look! Your repertoire of skills is crazy impressive — it's really inspiring and amazing to see all the stuff you've built and work you've done. Your manifesto is
34.
▲
by
jsherwani
5y ago
We could actually build this — drop us a line at hello@pop.com and let's talk through exactly how this could work with Slack + Pop!
35.
▲
by
jsherwani
5y ago
This is now fixed, thanks for the heads up!
36.
▲
by
jsherwani
5y ago
This is now fixed, thanks for the heads up!
37.
▲
by
jsherwani
5y ago
This is a really fair point, and we will look into seeing what we can do to alleviate this resource usage when in the background.
38.
▲
by
jsherwani
5y ago
Agreed! After starting with screen.so, we realized firsthand the importance of having a name that's easy to remember and communicate. Also, instead of viewing the domain as an expense, it's more of an enduring asset, which potenti
39.
▲
by
jsherwani
5y ago
This is a good point. We definitely want it to be a no-brainer for people to keep Pop running. One idea may be for us to look into relinquishing resources while running in the background, which could be a best of both worlds solution.
40.
▲
by
jsherwani
5y ago
Wow, that's great to hear! Please do let us know about the random hiccups at hello@pop.com, since the long tail of issues is surprisingly long in this product space, and so we really appreciate any feedback that can help us improve.
41.
▲
by
jsherwani
5y ago
Our core business is enabling remote work and remote pair programming. WebRTC infrastructure is largely commoditized, and we're open to revisiting how we handle our WebRTC infrastructure in the future. Daily is a great infrastructure p
42.
▲
by
jsherwani
5y ago
Thanks for the feedback! You're right, we need to improve each of these significantly. Reduce Power When Idle: decreases the frame rate from 30fps gradually down to 15fps when there's no user activity after a few seconds, and also
43.
▲
by
jsherwani
5y ago
Wow, thanks for sharing, and for the detailed write up! Please keep the feedback coming (I'm j@pop.com if you'd like to keep in touch in the future). I do agree Screenhero should have had a more generous free tier. With Pop, we wi
44.
▲
by
jsherwani
5y ago
This is a great point. We'll add support for this soon, thanks for the idea! We actually have a developer console command you can type to achieve this today if you really need something ASAP: - In the desktop app, click the hamburger m
45.
▲
by
jsherwani
5y ago
We have tinkered with the idea of a native module solely responsible for screen scrape + encode + send, which would further improve performance. Also worth noting is that there's a setting to "reduce power when idle", which t
46.
▲
by
jsherwani
5y ago
Yes! Once it's available in WebRTC, we'll implement end-to-end encryption for group calls. There is progress being made in this direction: https://webrtchacks.com/true-end-to-end-encryption-with-webr...
47.
▲
by
jsherwani
5y ago
Thanks! Discussed here: https://news.ycombinator.com/item?id=28225447
48.
▲
by
jsherwani
5y ago
When you say Pop could be more lightweight, are you talking about CPU or memory usage? Also, do you keep Slack / Microsoft Teams / Dropbox / 1Password / VSCode always running, and do you have the same concern with those
49.
▲
by
jsherwani
5y ago
It wasn’t ever intended to be a buy-and-kill, it’s just unfortunately what ended up happening. When Slack acquired Screenhero, it was with the full intent to bring voice/video/screen sharing to Slack. The problem was that, post-ac
50.
▲
by
jsherwani
5y ago
Hopefully we can fill the Screenhero-shaped void in your toolbox with Pop. Please do try it and let us know what you think! We're committed to making Pop exceed Screenhero in both functionality and longevity.
51.
▲
by
jsherwani
5y ago
Thanks! I worked with https://news.ycombinator.com/user?id=ted0 who was AMAZING at helping find and acquire the domain. I can strongly recommend him as an amazing person to work with. It took a few days to find a domain we
52.
▲
by
jsherwani
5y ago
We heard an equal number of people excited about being able to jump into a call with a coworker, vs. being worried about yet another layer of distraction. Having said that, we've now built out most of the infrastructure to support that
53.
▲
by
jsherwani
5y ago
Sending over keystrokes will always be faster than sending across a video stream of your screen. So VSCode Live Share will always be faster. However, in practice, we've found the cost of a few extra milliseconds in latency are far outw
54.
▲
by
jsherwani
5y ago
I'm explicitly not taking funding for Pop for this exact reason: I want to keep Pop around forever. I know that isn't something most people are able to do, and I'm grateful for my past success that's enabled me to do thi
55.
▲
by
jsherwani
5y ago
Hello HN! I’m the founder of Pop ( https://pop.com ) and formerly the co-founder and CEO of Screenhero. Also on the team are a couple other ex-Slack folks and a former Electron co-maintainer. Pop is the spiritual successor to Scre
56.
▲
Show HN: Pop.com – pair programming with low-latency, Screenhero-style sharing
(pop.com)
225 points
by
jsherwani
5y ago
|
125 comments
57.
▲
by
jsherwani
6y ago
In December 2012, one of our early alpha users of Screenhero posted the product to HN. It catapulted us into the public beta phase, and got us our initial traction. Those users eventually helped us refine the product over a year and a half
58.
▲
by
jsherwani
6y ago
Thank you for this gem and the responses. I haven’t laughed out loud from something I’ve read on HN as much as I just did thanks to this comment and its children comments. Even though I got zero wives out of these comments, there was some r
59.
▲
by
jsherwani
6y ago
Very cool, how does the team use this method as part of its prediction process? (Also: Roni, the head of this research group, was my PhD thesis advisor more than ten years ago!)
60.
▲
by
jsherwani
6y ago
Additionally, I think that tools like Webflow empower devs as well. Why spend hours writing a custom piece of code when it can be done in Webflow in a fraction of the time, and potentially even handed off to a non-dev to manage/maintai
More ›