#veilid — Public Fediverse posts

Hey #veilid crew, when a qr code is scanned and a transport route ID is authorised, is there an existing mechanism to generate a saved for the future de-authorisation "kill switch" or is that just something I need to cook up in rust?

Ok, I do appreciate that my hacker friends bring back cool #veilid stickers from defcon for me

@monkeyninja

I don't have a lot of brain at the moment, but would be interested in talking it out with you. I think there are some ways #Veilid could work for you if you built a custom app on top (distributed storage, potentially network isolation, and relatively cheap lookups at scale).

There are also some places where it wouldn't be great for a traditional implementation out of the box (DHT entries aging off, large index storage, substring or complex search). This situation can improve pretty dramatically when large object storage lands, though, and TTL on DHT entries is configurable.

Having a semantic layer on the indexer do some old skool bucketing of pages by topic instead of text content might be a shortcut to something useful. 🤔

Now I'm also not thinking about this.

I'd like to say that I came back from #defcon energized and ready to pick up the fight. Instead was completely exhausted, in a lot of pain, and immediately buried in work deadlines, so I'm just getting back into things now.

I had some great conversations with @thegibson and @tek about the direction of #veilid and friends, and it seems like folks are all coming to the same conclusions about next steps (ie we need more apps). So even if things I'm working on get superseded by better stuff from people who actually know what they're doing, I think the ideas are valuable.

Today's Maypole time was all about performance and updating the DHT watch pool to back off to polling since the current design of contacts & invites does a substantial amount of looking for changes and is intended to be very long running.

Once I have something that is also useful to api consumers I can go back and fix up my own designs to fan out less, but this has been a consistent footguns for me and I'd love to abstract it away forever!

Thanks to the good work by @thegibson , I have a wearable #Veilid node. #DEFCON34

Mission accomplished. Managed to snag the first hackers.town #veilid badge and drop my donation! 🦾

Another question...

In trying to compare #VeilId and #i2p it seems like they're pretty similar and much of the difference is one is in rust and the other java.

veilid's documentation advertises being able to directly use a DHT and it claims to support recovery of the complex connection for mobile clients which i2p doesn't mention.

i2p seems to have more ways for other applications to opening streams over i2p.

Am I interpreting their docs reasonably?

Updates to the #veilid developer guide have been pushed to prod (and not on a Friday at 4:20!) so check it out if you have projects in mind.

https://veilid.gitlab.io/developer-book/

#introduction part 2! What is Project Maypole actually about? Bringing compute back to the people. We want to make encrypted, peer-to-peer software the default for personal networked applications. No joke.

A big barrier for writing those kinds of tools is that the existing libraries are generally low level,  complicated, and easy to get wrong. That's the part we hope to push forward.

The first foray is Astod, a framework, daemon, and user facing application that should greatly simplify building on the #Veilid network. It will act like cross-device single-sign-on (but entirely in the user's control!) and handle things like identity, authentication, contacts/groups, trust, and invites using secure, private, tested, and vetted primitives so developers can focus on what makes their apps special.

Apps ask for permissions, Astod provides the interface for users to grant and revoke them. Revocation is cryptographically enforced, so other people and apps will see that an app attempting to use a revoked permission is rogue.

We're also writing simple a apps as examples to showcase Astod, like Maypolls for making polls and surveys, and Rosie (me! *preens*) a text based user interface for low level debugging and poking at the Astod daemon interfaces.

Apps will be able to rely on the daemon to manage all things Veilid, or use the Rust crates directly, or use bindings for a set of popular languages, or re-implement the protocol wire format for interoperability.

The goals are ambitious, but we hope there is enough interest in these kinds of things to build a community to share the load. If you're interested in helping out get in touch!

https://codeberg.org/ProjectMaypole

Scrapwire 0.4.0 has the Mac app merged into main. That app's still early but hey, it's working and usable!

So yes, you can now chat over #Scrapwire & #Veilid with a pretty native Mac GUI.

Dude.

#Scrapwire & #Veilid fun for the evening.

The Maypole Trust Playground has outpaced the actual doc that it's supposed to represent (thanks brain).

It is standalone, and tries not to reference the distributed #veilid / #maypole implementation. Instead it focuses on the trust/caution algorithm, human elements of trust, and demonstrates how the system reacts some scenarios (Sybil, Brigading, Impersonation currently).

It may still be too complicated and is probably a nightmare to navigate on mobile, but give it a spin and let me know what you think!

https://trust-playground.maypole.chat

@teohhanhui I've been playing with #activitypub ideas in https://codeberg.org/cmars/medina recently (very incomplete and slightly incoherent rough sketch). I had this idea of a hub or relay where the identities are moderated but the clients own their keys and data in a portable #sqlite db which could be hosted by an instance or relayed. Exploring that balance between moderation and autonomy. I'm also testing some of these ideas with #veilid in another project that I haven't shared yet.

Looks like you're using #iroh which I haven't tried yet. It's hard for me to commit to side-projects right now, but very interested to see how your project goes!

I'm watching 2 hosts on my own LAN transfer a file between themselves via #Veilid. They might as well be in Australia or on Mars for all each other can tell. Cypherspace is magical, I tell ya.

@jordan It's a peer-to-peer chat app, powered by #Veilid, E2EE and serverless, designed for maximum privacy: https://scrapwire.chat/

vnewb has just been updated. Using Veilid 0.5.3 now.

http://vnewb.net/

#veilid

Will Rustlang becoming a first class citizen in Linux Kernel 7 make #veilid faster? I don't know enough about the kernel impact.

I kinda threw out the entire Scrapwire #veilid TUI chat code and started over by making a protocol doc. It's paying off. I'm just now having the first ever group chat with it, using MLS encryption. 1:1 chats use double-ratchet Signal-style encryption.

This is so fun!

The #Veilid chat app has an inline image sender/viewer now, so you can type "/image" in a chat to send a picture to the recipient.

The significance of the #Veilid bit here is that you should imagine something like Signal… but where there’s not a server in the middle. No central registry. Not a metadata handler or NAT bridge or STUN broker or login anywhere to be found, just a series of reads and writes to a shared global distributed hash table.

It seemed nifty for the #Veilid chat app to have file transfers, too, so I wrapped Stigmerge into it. The UI is still buggy, but… it actually transfers files, and they come out the other end intact.

@bobdobberson

We live in the decentralized age of #BitTorrent, #TOR , and #Veilid

Behold, the world's first ever successful #Veilid group chat, as far as I know. The UI is wonky and buggy at the moment, but each machine was able to post to the chat and read others' messages.

Current status of a new peer-to-peer chat app running on #Veilid.

Simply Plural is shutting down in June.

Ampersand, pretty much the only alternative that mostly lines up with our needs, does not aim to provide feature parity with Simply Plural (e.g. by implementing privacy-preserving fronter change notifications via Veilid).

You know what that means! It's forking time!

Please be encouraged to get in touch to work with me on this, let's make this happen! :)

:boosts_ok_gay:

#Plurality #Plural #Systemhood #FOSS #NoAI #OfflineFirst #Veilid #Tauri #Rust #JavaScript