Live data from Hacker News

Veilid is an open-source, P2P, mobile-first, networked application framework

veilid.com

31–40 of 75 posts

Re: Veilid is an open-source, P2P, mobile-first, networked application framework

#31

Can anyone access the demo example repo linked from this page? : https://veilid.com/chat/ (points to : https://veilid.com/chat/ )

I haven't been able to. I attempted to yesterday also with no luck. Their site mentions availability after recovering from DEF CON or something to that affect.

Nailed it. There’s a laundry list of stuff to be done, but lots of people are either still traveling or hibernating after a very hectic few weeks!

Re: Veilid is an open-source, P2P, mobile-first, networked application framework

#32
post #24
post #23

It says on the linked page that it's a "mobile-first framework" but what is mobile-first about it? I'm having trouble finding Swift or Kotlin code. Or do they mean something else?

Does flutter bindings work?

Yep. The upcoming Veilid Chat app is in Flutter.

Re: Veilid is an open-source, P2P, mobile-first, networked application framework

#34
post #22

Also discussed 8 days ago as "Cult of the Dead Cow wants to save internet privacy with new encryption protocol, 82 comments: https://news.ycombinator.com/item?id=37018404

It wasn't launched yet, and there were very few details then. Now there's a slide deck and code.

Some code.

"You can get the code for Veilid Chat at https://gitlab.com/veilid/veilidchat"

Visiting that link gives me a GitLab signup page. Not a good onboarding experience for someone who cares about security and privacy. Perplexed I return to the original page and spot the offhanded mention:

"If you want to try out this proof of concept, please stay tuned for details on how to gain access."

This doesn't bode well, if they're reluctant to release even their own proof of concept.

Re: Veilid is an open-source, P2P, mobile-first, networked application framework

#36
post #34
post #22

Earlier quoted context omitted.

It wasn't launched yet, and there were very few details then. Now there's a slide deck and code.

Some code. "You can get the code for Veilid Chat at https://gitlab.com/veilid/veilidchat " Visiting that link gives me a GitLab signup page. Not a good onboarding experience for someone who cares about security and privacy. Perplexed I return to the original page and spot the offhanded mention: "If you want to try out this proof of concept, please stay tuned for details on how to gain access." This doesn't bode well,…

That’s due to running out of time before DEF CON, not by plan. It’ll be there for everyone to see very soon, promise!

Re: Veilid is an open-source, P2P, mobile-first, networked application framework

#37
post #27
post #18

I saw this talk at DEFCON. It seems to combine ideas from IPFS, BitTorrent magnet links, Tor, and things like scuttlebutt. There was a very strong focus on privacy including for metadata. The biggest weaknesses I saw were around DOS attack resistance, which I did not see addressed. There were good approaches for privacy and security but what if someone with resources (botnet or money) wants to just burn the network d…

No expert but I do wonder how a cheap client can be more secure than a professionally managed server.

Depends on your definition of secure. If you mean software security against things like buffer overflows and other software vulnerabilities then the size of the machine is completely irrelevant.

If you mean robustness against brute force volumetric and resource exhaustion attacks then yes large systems are going to be more resilient than small systems for the same reason a big boat is harder to swamp with waves than a small one. The whole business model of things like Cloudflare is to put your site behind a gigantic CDN that is just so damn big it can weather volumetric attacks. It's a brute force solution to a brute force problem.

In this case I was talking about more intelligent distributed attacks against distributed protocols. Those types of attacks are very hard to protect against in general.

Most systems deal with it by being closed and isolated or at least having fairly strict policies about who is allowed to participate (e.g. BGP). In an open P2P network you're going to have to figure out a way to permit resiliency in aggregate without a trust model, which is IMHO an unsolved open problem in protocol design. There's been some progress in countermeasures but no huge breakthroughs.

Re: Veilid is an open-source, P2P, mobile-first, networked application framework

#39
post #34

Earlier quoted context omitted.

Some code. "You can get the code for Veilid Chat at https://gitlab.com/veilid/veilidchat " Visiting that link gives me a GitLab signup page. Not a good onboarding experience for someone who cares about security and privacy. Perplexed I return to the original page and spot the offhanded mention: "If you want to try out this proof of concept, please stay tuned for details on how to gain access." This doesn't bode well,…

That’s due to running out of time before DEF CON, not by plan. It’ll be there for everyone to see very soon, promise!

Good luck!

Re: Veilid is an open-source, P2P, mobile-first, networked application framework

#40

Do we have any metrics on the network performance? I have a project that might have use for this, but it depends on pushing a lot of data around.

Not yet. It’s also slower today than it will be as the node count increases. I mean, today there’s a fair chance that 2 nodes in California may talk through a node in Australia.
Post reply on HN