barathr

17 ms·

151.
by barathr 4y ago
I think DMs should be treated as semi-public on any platform without end-to-end encryption and a method for verifying keys of who you're DMing. So not really that different than Twitter, Facebook, and many others.
152.
by barathr 4y ago
Yes, you can export, and most servers will put up a helpful forward pointer once you move your account so people see where your new profile is. I haven't tried it but others who have seem to keep all their followers / following se
153.
by barathr 4y ago
Yes that's true in terms of the local feeds, but in terms of getting one's feet wet it's fine. For HN users, this is one among many reasonable tech-oriented choices: https://techhub.social Here are a couple that a
154.
by barathr 4y ago
For those wondering about how to sign up to mastodon and what server to pick: It's like picking an email server. They all have their differences, but generally they are interoperable. You can read users from anywhere, and follow from a
155.
by barathr 4y ago
Yes and no; while the second hop (recursive resolver) won't know the client's IP/geo, we've chosen to locate the first and second hops very near each other in terms of network latency and, eventually, to roll out enough
156.
by barathr 4y ago
With my colleagues I've been advocating for a decoupled approach to achieve security/privacy for network services like DNS, which we built a demo of earlier this week and wrote about a bit here -- the gist is that there's no
157.
Sen. Wyden Requests Probe into Sale of DNS Query Data [pdf](wyden.senate.gov)
79 points by barathr 4y ago|6 comments
158.
Show HN: Fast, Clientless Oblivious DNS(invisv.com)
3 points by barathr 4y ago|0 comments
159.
by barathr 4y ago
Nice to see this here; happy to discuss our paper with folks. The TLDR is that there's a classic idea (dating back at least to Chaum's early work if not earlier) that we can get privacy in networks by splitting knowledge across mu
160.
The Decoupling Principle: A Practical Privacy Framework [pdf](dl.acm.org)
1 points by barathr 4y ago|0 comments
161.
by barathr 4y ago
Instead, I'm saying that Coindesk is a stopped clock here (maybe not the clearest metaphor, I know) and knows it -- it's right about FTX but it's strange that they (and plenty of others) have been pumping lots of other highly
162.
by barathr 4y ago
Not really what I'm saying -- it seems that there was fraud here. But it's a bit strange to see this from Coindesk, which has undoubtedly reported in glowing terms about plenty of other companies doing fraud in this space.
163.
by barathr 4y ago
This seems a bit like a "doth protest too much" article -- while the things FTX did are no doubt shady, this article seems to be trying to heap scorn on FTX as if it is unique in the cryptocurrency space. (And there are factions w
164.
by barathr 4y ago
Soonish there's going to be a standardized way to do this, via CONNECT-IP: https://github.com/ietf-wg-masque/draft-ietf-masque-connect-...
165.
by barathr 4y ago
This sort of practice is soon to be disallowed in New Jersey, if I understand correctly: https://www.thedrive.com/news/new-jersey-legislators-aim-to-...
166.
by barathr 4y ago
Thanks! We're thinking through the right architecture; it's a question of whether WebKit will get Insertable Streams soon enough, or if we'll need to create a custom client. Our preference is for users to not need a custom cl
167.
by barathr 4y ago
The data goes through the Multi-Party Relay. (Similar to Apple's iCloud Private Relay, if you're familiar with that.)
168.
by barathr 4y ago
That's what we'll be doing for a well-defined group of users -- that is, with stable, long-term cryptographic identities. It's not as useful for conversations where participants join with a link.
169.
by barathr 4y ago
The good news with this is that we've built our implementation on top of LiveKit, and you can look at the source, so you can see the E2EE in the browser. The encryption key for video/audio is only known to the client, so it's
170.
by barathr 4y ago
That's right -- unfortunately Firefox doesn't support WebRTC Insertable Streams, which we use for end-to-end encryption. It's on their roadmap but not there yet. (And I am primarily a Firefox user, so this is a disappointment
171.
by barathr 4y ago
Unfortunately, that's the case: Safari and Firefox haven't yet implemented WebRTC Insertable Streams, which we use for end-to-end encryption. And on iOS even Chrome is not really based on chromium (due to Apple's restrictions
172.
by barathr 4y ago
We actually haven't yet limited the free tier :) -- we figure until our servers are overloaded there's no need to actually impose limits. So yes, feel free to use for now, and probably for a while until server load becomes an iss
173.
by barathr 4y ago
STUN/TURN took a bit of work to deal with -- we have a bit more on it here, at the end of the blog post: https://invisv.com/articles/booth One key part is that the video conferencing server thinks its IP is the fi
174.
Show HN: We made metadata-secure video conferencing that's easy to use(booth.video)
41 points by barathr 4y ago|17 comments
175.
Show HN: We made metadata-secure video conferencing that's easy to use(booth.video)
14 points by barathr 4y ago|0 comments
176.
by barathr 4y ago
This isn't Mullvad's fault -- it's a challenge with the VPNs-as-a-privacy-service architecture generally, something we wrote about here: https://invisv.com/articles/relay.html VPNs are great when the net
177.
by barathr 4y ago
I think the term "zero trust" creates a bit of confusion, in this and other contexts -- not Cloudflare's fault, because the term has been used/abused quite a bit. I think it's a good idea to prevent SIM swapping att
178.
The Invention of Money (2011)(thisamericanlife.org)
1 points by barathr 4y ago|0 comments
179.
Maps, the Territory, and Meta-Rationality(metarationality.com)
1 points by barathr 4y ago|0 comments
180.
Judging Whether a System Applies(metarationality.com)
2 points by barathr 4y ago|0 comments

More ›