73 karma · joined October 27, 2014
Not everyone needs to do everything. And if someone’s amazing idea can get out of their head and onto paper/film/video or into a game I’m all for it.
There will be a lot of AI shovelware junk. But it doesn’t all have to be that way. Now more people compete on larger landscape of ideas.
What makes a normal CC better?
It’s ugly. Would not recommend. 0/10
I have been working on WebRTC a lot lately. If you have ideas on how you’d solve this issue I’d take a stab at implementing them.
I’ve built a demo that lets you get two systems connected by copying and pasting the session description information. No third party systems required. But you still need to get your clipboard data to someone else. Which usually means SMS, Apple Messages, etc.
WebRTC needs info about where to try to connect. It doesn’t specify the signaling method which is how you get that information and share it.
If you’re already on the same subnet, use mDNS.
If you’re on different subnets it requires some kind of way to share the subnet info.
If you’re on different networks behind NAT then scanning isn’t very helpful. You’d need to scan IPs and ports because NAT randomizes the outbound ports. That’s what STUN helps you figure out. Once you’ve got that info and you build the session description structure you can send that to the other party however you want.
Public, free STUN servers exist. And people use them for all kinds of WebRTC stuff.
Neither WebRTC nor WebSockets prevent pure P2P. It sounds like your bigger issue is with NAT. IPv6 isn’t going to fix it though since the IP space will be too large to scan for peers.
I think it is very strange.
$92M - $45M = $47M
Average pay out to customers who were ripped off = $0
Incentive to not do this again = 0
I’d write and explain the problem was with the same song, on different machines (Windows, Linux, and Max) and both Android and iOS. Still got the same form letter back.
I’ll almost guarantee that if I search my email for the broken tracks they’d still be broken. One was Saddam-a-Go-Go by GWAR. A few seconds in it just skips ahead a few seconds from one lyric to another.
As an aside, instead of talking about growth hacking, and OSINT I think this whole thing could be a lot more relatable if the author chose a simple motivation like privacy. Another comment here mentioned subtools (?) which clearly highlights that not everything should be trusted with full access to your system.
Long abandoned but I’d love something like this. Someone I know tried to revive it but Node has changed so much that they gave up.
I would donate to an effort to revive it.
On the auth side, the major change since then is that you can use the IoT credentials provider to provide certificate based auth to all services (https://docs.aws.amazon.com/iot/latest/developerguide/author...). You don’t need to be using any of the other IoT services. It was created to make it easier for devices to use AWS services but can be used by anyone/anything.
What we did was combine the AWS CLI feature to source credentials from an external process (https://docs.aws.amazon.com/cli/latest/userguide/cli-configu...) with a script to do the certificate based auth. This allows you to obtain STS credentials using a certificate and pass them to the CLI (access key, secret key, session token). Your secure hardware just needs to do the normal work of assisting in the mutual TLS auth which in our case was done with curl and Zymbit’s OpenSSL engine. We are releasing that code along with a SoftHSM2 setup so people can see how it works in a test environment.
We haven’t released the code yet but are in the process. If you think this could work for you or you’d just like to see how we did it DM me on Twitter @timmattison and I’ll give you the code ASAP.