pop.com is not blocked by this blocklist
Probable causes:
- An other blocklist blocking it? - Regex? - An older version of this list contained it? > Make sure you are using the latest version.
Not sure what happened!
1,473 karma · joined July 14, 2009
Now building pop (https://pop.com).
pop.com is not blocked by this blocklist
Probable causes:
- An other blocklist blocking it? - Regex? - An older version of this list contained it? > Make sure you are using the latest version.
Not sure what happened!
Monetization: very similar to what everyone else in this space does. Free for social users, paid for business users, and finding a good way to segment the two.
However, I can say that 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 for anyone interested in buying a high-value domain.
I wrote this elsewhere:
We bought this domain a few months ago, and you're probably right, since Gmail seems to mark our outgoing emails as spam. I'm not very well-versed in how to undo the reputation the previous owners seem to have created for the domain, so if you have any recommendations, please let me know!
Our plan is to merge the two in the near future, and work on the intersection between 2D and 3D calls.
Pop lets you have a video call in 3D, with positional audio. It works in a browser, without any download. The experience is surprisingly fresh, and the social dynamics are quite fun.
You can feel like you’re part of a group, you can see who’s looking at you, you can go to the side with someone and have a separate conversation, without interrupting the current conversation. You can share a screen that floats in space (and always faces the viewer). You can even bow to say hello!
We use Mediasoup for the WebRTC backend, Ionic/Angular for the frontend, and BabylonJS as our 3D framework.
Also, as an experiment, we’re hosting a virtual launch party at [EDIT: 6 hours later, and we're done! Thanks to everyone who came by!].
Happy to answer any questions here too, of course!
Edit: there are more screenshots here: https://www.producthunt.com/posts/pop-9
On the other hand, screen sharing with interactive control when working together on a shared task is actually better than sitting next to someone on their computer. In person, I can only talk and point at their screen. With interactive screen sharing, I can click, type, and even draw live on their screen.
I spend hours a day in interactive screen share sessions (quasi-pair programming but not really) and never feel the effects of Zoom fatigue. But when I have to use a product without the ability to easily draw or interact, or have a meeting where it’s just about faces in boxes, I immediately feel extra “drag”.
I’m curious to hear if anyone else has had the same experience.
If this is correct, there may be a way to sidestep the issues of Zoom fatigue with better tools and processes (e.g. don’t talk about work, instead do the work together).
Digital multiplayer whiteboard: we sort of do. You can draw even outside of a screen share — just draw during a video call (or even voice (or even no media at all!)). But I’m curious if you meant something else? There are a number of websites that do digital whiteboards, and we didn’t want to reinvent the wheel.
Bug: this is an intermittent bug we’ve heard about from some users but have had a hard time reproducing. Thank you for letting me know — we’ll try to figure out a better way to log the error to help us reproduce and solve it.
>Neither Screen nor these third parties store or record media data as part of the Service, nor process it other than for the purpose of providing the Service to you.
Having said that, I’ve heard this request a few times now, and we will likely get to this soon. But I am curious whether the workaround would work for you for the time being.
If you have suggestions of what we can say and do to make this better, please let me know. I will be looking into improving the language before we do our GA launch.
But if the guest needs to see something else on the host’s computer (if you’re working together on a webpage, or a desktop app), then whole-desktop screen sharing is the best approach.
Screen definitely isn’t the best tool for every job. But it’s great for when you want everyone on the same page, seeing the same thing, and able to talk about the content of your screen and even control it together.
Your bike shedding comment made me laugh out loud :D
WebRTC server: Daily (primary), and Twilio (secondary)
There’s no shortcut to the performance side of things, so we had to do a lot of custom work on Mac, Windows and Linux to get screen sharing to be super fast. The high level bit there is the boring-but-correct advice: measure everything, start with the biggest bottleneck, optimize, repeat.
The desktop apps follow a Slack approach (with a slight twist). Like Slack, we use Electron, but in our case, we’ve heavily modified it to make screen sharing super fast. We then use the standard Electron model to have main & renderer processes. The renderer process fetches the UI from our website (hosted on Firebase).
Almost everything (other than our custom node module) is in a monorepo. Even our modifications to Electron are stored as patch files, which just makes it easy to keep things aligned between our app and our modifications to Electron.
Our website/webapp (they are one and the same) are built on Ionic/Angular (we started before Ionic supported React). We used Ionic because I didn’t want to have to create new different UIs for each platform — I think the user is served by having a low cost product where the effort is spent mainly on performance and quality, rather than a slightly different UI for each different platform (which has significant cost). We’ve tried to maximize code re-use wherever possible, which is how a 2 person engineering team was able to build this product (granted, it took almost an entire year, or more if you count the project we pivoted from).
Happy to dive into details if you’d like!
Looks like a bug in our Linux multi-monitor code. I'm going to look into this right now! It’s been a while since we touched that code, and it’s likely that bugs may have crept in since then.
Also, corp level user management is something we’ve got in the works, but we wanted to get the product out so that people could start using it, and then add admin tools on top of that. For instance, if you’re on G Suite, everyone should be able to OAuth in. But I hear you on the need for better tooling around users.
Were you able to try screen sharing from your Mac to his Linux computer?