home.social

#veilid — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #veilid, aggregated by home.social.

  1. 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

  2. We usually met on the second level of the mall, in the coffee shop run by some weird dreadhead. They didn't seem to mind a couple cyberpunk kids hanging out in the back, as long as we drank copious amounts of coffee. Also, the uplink was exceptional.

    We had already fueled up and jacked in. Shelly hooked a tripwire into the shop's cams, to let us know if someone got too nosy, security in the mall was a joke.

    "Yo check this out." bROOTal dumped a couple twilight addresses on the channel. Ain't gotta tell us twice.

    0pid moaned "Sooo slooow! Where the fuck is that routing?"

    I set up a jail, opened a connection, and data trickled in. We dumped checksums and partial payloads in the channel.

    "Huh, everyone gets a bespoke stream, headers look like VR sims." Shelly had started annotating patterns in the binary and bROOTal had set a ghidr/ai loose to decompile the code. "There's connection code in there, and lots of crypto. What's a #veilid?"

    "So, anyone wanna sample?" 0pid's avatar started wagging an eyebrow.

    "Fuck it." I flashed a hard damper onto my interface and the world grew dim. Less pressure from the seat and the cup in my hand felt cooler. My vision grew a little blurry and muted. I fed the payload into the runtime.

    The world vanished. No more seat, cup, or hand. No more vision. I floated in absolute blackness. Then a fractal of light exploded in the sky. Unfurling tendrils of complexity ate away the darkness, replacing it with pulsating constructs of nightmarish beauty. Nothing was dampened. My head hurt and I tried to remember how to unplug, but instead of my memories I found a face. Not a human face. A facsimile of one, nearly correct but wrong. Smiling a wrong smile with too many teeth. Speaking without opening it's mouth.

    «BE. MY. GUEST.»

    The headache got worse. There was pressure on my ears and my heart was racing. I couldn't breathe.

    «LET. ME. HELP.»

    The face grew a body with too many limbs and stretched an arm out to touch me. Just before the hand reached me, I snapped back.

    I lay on the floor of the coffee shop, smelling vomit and tasting blood. My friends were staring down at me, and so was a weird dreadhead.

    "You alive?" They slapped me gently on the cheek and I moaned as the headache flared up again. My friends grabbed me and pulled me onto a seat. Dreadhead threw us a pitiful look.

    "So you're smart enough to find trouble, and dumb enough to not know."

    They grabbed a coffee, pulled up a chair and sat at our table.

    "Listen up, kiddos, today we'll learn the lesson: Fuck ICE."

    #guest #wss366 #cyberpunk #writing #tootfic #macrofiction #microfiction #scifi

  3. Beginning to research #OnionSites vs #EepSites to see which might be more secure, and functional. Also wondering if there are any other options that might secure both the end user and the host online (maybe veilid). Curious what is recommended in 2026. :)

    #CyberSecurity #Tor #I2P #Veilid

  4. Beginning to research #OnionSites vs #EepSites to see which might be more secure, and functional. Also wondering if there are any other options that might secure both the end user and the host online (maybe veilid). Curious what is recommended in 2026. :)

    #CyberSecurity #Tor #I2P #Veilid

  5. Beginning to research #OnionSites vs #EepSites to see which might be more secure, and functional. Also wondering if there are any other options that might secure both the end user and the host online (maybe veilid). Curious what is recommended in 2026. :)

    #CyberSecurity #Tor #I2P #Veilid

  6. Beginning to research #OnionSites vs #EepSites to see which might be more secure, and functional. Also wondering if there are any other options that might secure both the end user and the host online (maybe veilid). Curious what is recommended in 2026. :)

    #CyberSecurity #Tor #I2P #Veilid

  7. Beginning to research #OnionSites vs #EepSites to see which might be more secure, and functional. Also wondering if there are any other options that might secure both the end user and the host online (maybe veilid). Curious what is recommended in 2026. :)

    #CyberSecurity #Tor #I2P #Veilid

  8. FLOSS Weekly Episode 849: Veilid: Be a Brick - This week Jonathan talks with Brandon and TC about Veilid, the peer-to-peer networ... - hackaday.com/2025/10/01/floss- #hackadaycolumns #peer-to-peer #flossweekly #podcasts #veilid #tor

  9. Would it not be fair to say that #vanguards is the #fdns of #tor ?

    #netblue #firejail and #mikePerry really should talk to each other if they haven't already.

    lots of factors come into play. There isn't just one easy solution that works for everything online. There are levels of tor just like there are levels of dns filtering and control.

    ****** Why have local storage if you have a secure and accessible global commons? Because there will never be enough of one, just more fences on the prairie? Could you keep out a Tailored Access APT even if you were primarily locally owned? *****

    I wonder why p2p like i2p and yggdrasil have remained less developed than tor or dns. Has anyone got the i2p config to work well with ygg or torsocks as was envisioned?

    #obliviousDNS is new and interesting R&D.

    #VPN has definite flaws. Often acts more like a vector than a security.

    #Veilid looks promising with #IPFS and the anonymity design. But it might end up like i2p, freenet, or yggdrasil without more development. Technologies like tor's #onionshare (which requires agreed upon share time) or ricochet-refresh #gosling (#rust) are useful if you don't want upload/download from 3rd party drives and the cloud. Everyone finds a need to share hefty files from time to time unless you like passing USB sticks around.

  10. Would it not be fair to say that #vanguards is the #fdns of #tor ?

    #netblue #firejail and #mikePerry really should talk to each other if they haven't already.

    lots of factors come into play. There isn't just one easy solution that works for everything online. There are levels of tor just like there are levels of dns filtering and control.

    ****** Why have local storage if you have a secure and accessible global commons? Because there will never be enough of one, just more fences on the prairie? Could you keep out a Tailored Access APT even if you were primarily locally owned? *****

    I wonder why p2p like i2p and yggdrasil have remained less developed than tor or dns. Has anyone got the i2p config to work well with ygg or torsocks as was envisioned?

    #obliviousDNS is new and interesting R&D.

    #VPN has definite flaws. Often acts more like a vector than a security.

    #Veilid looks promising with #IPFS and the anonymity design. But it might end up like i2p, freenet, or yggdrasil without more development. Technologies like tor's #onionshare (which requires agreed upon share time) or ricochet-refresh #gosling (#rust) are useful if you don't want upload/download from 3rd party drives and the cloud. Everyone finds a need to share hefty files from time to time unless you like passing USB sticks around.

  11. So, I recently got interested in #veilid

    Veilid is a new (or, new-ish) idea from the Cult of the Dead Cow, yes, those folks who've been doing hacker-y things since the 80's, and its meant to help us take back the Internet. By giving us a secure and private means to inter-connect.

    So anyway, I didn't just go get the source and build it.. I took the veilid project's RPM distribution, and threw it into a RHEL UBI container.

    What I've built is a headless veilid server. Which is basically a peer-to-peer node, that helps add to the reliability of the veilid network. The more nodes we have, the better.

    Oh, and I published it on github so you can all tear it apart and make it better.
    github.com/gangrif/veilid-serv

    Oh, and I published the resulting container on docker hub, so you can all go use it.
    hub.docker.com/r/gangrif/veili

    Go give it a try! File issues if you find problems.

    #defcon #cdc #cultofthedeadcow

  12. oh hell yeah, the beta VeilidChat app is now available for Android and iOS!!!

    anybody wanna try it out with me?

    #veilid #p2p #privacy #encryptedmessaging

    --- BEGIN VEILIDCHAT CONTACT INVITE ----
    ClMKLw0wRExWEigNeVRXYhVyYyMcHT2g-9UlQgzB
    0S2NPXVnNeTsmkE94qZPyEWaRUrZEiDOjJ3xeE5C
    XU6bPflnNHYdf-n8Xh_JY-NrYAJuNWo5ORJRDd9L
    v6gVqefuJR2532s3JYzdAWwthoNDtDVWmWXxPezF
    QMpF_2s7RE30bH0RVeatEGZdFmbhTWWeYaKmbabE
    nX51jCRb7H02hM3jhQEF-QsE
    ---- END VEILIDCHAT CONTACT INVITE -----
    Fingerprint:
    MFNjb_RGlAPg7xbGcAC3DrFZwZn96kNeRjkBvi9kIdY

  13. Updated the rpm repo path for my container. Nice to see that we now have a nightly build as well ! If you are looking for a with a public build pipeline, signed with and auto released every sunday.

    Checkout github.com/chimbosonic/veilid-.

    Container images are uploaded to and .io

  14. One of my clients needs #Rust for some #p2p stuff using #veilid and #iroh and I'm gonna see how far I can get with just telling #Phi3 to make changes to the code using continue.dev :P

    My guess is it's gonna suck, but we'll see.

  15. Can anyone tell us some more about the "mobile first" objective of the #Veilid project?

    Cellular devices are less susceptible to Spectrum Dominance attacks and #EMI / EW / EA attacks. That is a great advantage!

    lemmy.social/c/explorations_in

    #yggdrasil #nym #mixmaster #tor #freehaven #IT #CS #fullspectrumdominance

  16. @Sempf
    I also changed my mind halfway through that toot I guess x_x

    #lookingFor #veilid

    1. A rust demon. It listens for datagrams on a local unix socket. When it receives one, it changes a property on its associated veilid node to be that / the last datagram's bytes.

    2. A rust demon. It subscribes to updates on a known veilid node address. When it is notified of an update, it sends the updated property's bytes as a datagram on a local unix socket.

  17. @Sempf
    I also changed my mind halfway through that toot I guess x_x

    #lookingFor #veilid

    1. A rust demon. It listens for datagrams on a local unix socket. When it receives one, it changes a property on its associated veilid node to be that / the last datagram's bytes.

    2. A rust demon. It subscribes to updates on a known veilid node address. When it is notified of an update, it sends the updated property's bytes as a datagram on a local unix socket.

  18. @Sempf
    I also changed my mind halfway through that toot I guess x_x

    #lookingFor #veilid

    1. A rust demon. It listens for datagrams on a local unix socket. When it receives one, it changes a property on its associated veilid node to be that / the last datagram's bytes.

    2. A rust demon. It subscribes to updates on a known veilid node address. When it is notified of an update, it sends the updated property's bytes as a datagram on a local unix socket.

  19. @Sempf
    I also changed my mind halfway through that toot I guess x_x

    #lookingFor #veilid

    1. A rust demon. It listens for datagrams on a local unix socket. When it receives one, it changes a property on its associated veilid node to be that / the last datagram's bytes.

    2. A rust demon. It subscribes to updates on a known veilid node address. When it is notified of an update, it sends the updated property's bytes as a datagram on a local unix socket.

  20. @nonlinear ...anywho it never seemed to me that AP even intended to be an all encompassing "seamless integration between services" but rather just the data exchange amd interaction component...the evolution of RSS into something more fully interactive if you will.

    What I think you are envisioning with "seamless integration" probably requires AP plus other open standards like #IndeAuth for authentication, something based on #OCAP like what @cwebber has long been advocating for authorizarion, and some agreed upon extensions to AP (maybe an AS vocabulary too?) to federate social graphs between instances/applications...and maybe for apps requiring better privacy and security we need to look at a rathere differewnt approach like #Veilid

  21. #lispyGopher show at Wed 000UTC #archived archives.anonradio.net/2023102
    #climate haiku by @kentpitman
    Climate resilient societies
    @hayley pigeon proposal
    #gopher
    #gopherMOO #VR from @masinter & kmp^
    #lisp
    #ExploratoryProgramming #veilid
    #SSB after
    #mastodon
    @mousebot calms me down after I got in one argument once
    #futurePlans
    I'll work on #usim with @amszmidt for [Nov Jan]
    #redacted
    Student Correction for using a chatbot leak

    Show #unix_surrealism by @prahou
    #music from @mxv

  22. Two days of exploratory programming (actually prose) (and an appendix.) 031/ #100daystooffload #phloggersgarage #gopher
    gopher://tilde.club/0/~screwta
    gopher.tildeverse.org/tilde.cl
    while also being my inaugural two days of #ExploratoryProgramming in #Lisp, prose ranges from #clim commentary to the wistful feeling that the mastodon is in its last days as #veilid waxes.
    The appendix is also an interesting real life example of Not Planning.