that is gonna require a lot of engineering work :P
swarm/dht/whatever is all necessary, so I want to understand your efforts more and write code with PANIC to benchmark scale.
Data coming through hypercore dht
This isnt the best case scenario because everyones gun data gets synced, but eventually work will pay off and they will only receive the data they ask for.
But a one room chat can use this method
Speaking of, does anyone know which event gets fired when data is meant to go out to a relay peer and be forwarded?
hi, on a nodejs stack, using another gunjs instance that i used from react frontend that work with register, get and login, and now dont work on my other nodejs stack. im connecting to my local [ 'http://localhost:8765/gun' ],
import * as SEA from 'gun/sea';
const gun = SEA.GUN(gunHosts);
// hang here, no callback
gun.user().auth('username', 'pass', (res) => {
console.log('result!', res);
}));
Sorry if this is a dumb question, but how do I create a websockety host server for gun? Just run gun on node and direct client to the IP? But how does gun know how to use websockets on my server, and how do I add the IP to the client? I'm really struggling to find this in the docs
+1 to the two questions above. I also can't really get a hold on this in my mind...
@connor-davis š
[whispers - get us off gitter be our saviour]
Im still learning the inner workings of how stuff gets transferred in Gun
See what happens is that the client connects to the dht and from there I get the dht to relay the data to the other sockets.
What I am excited about more so is being able to expand the capabilities, for e.g. I have built a p2p file sharing app with hyperswarm/dht that allows the desktop app (electron) to act as a server and a client, so if someone is "hosting" then someone connects to their http connection that is relayed over the dht and the "client" connects to that relay and can perform axios get requests etc, now this enables that to work in theory :)
But as well as that, now imagine this:
You have gun-relays that connect to eachother using the dht and the dht allows them to query data from eachother, simple enough because in nodejs you can pipe data from one relay to another, so when one asks for data, whoever has the data can send it to them. The same can work for a browser client, it connects to the dht and the dht can forward that get request to all on the network and whoever has it sends it to the client. This dht-relay will open those doors if we use it correctly, together. We basically need to work together as a community on this.
You have gun-relays that connect to eachother using the dht and the dht allows them to query data from eachother, simple enough because in nodejs you can pipe data from one relay to another, so when one asks for data, whoever has the data can send it to them. The same can work for a browser client, it connects to the dht and the dht can forward that get request to all on the network and whoever has it sends it to the client. This dht-relay will open those doors if we use it correctly, together. We basically need to work together as a community on this.
That could work yeah, I cant imagine a regular dht being as fast or reliable to handle too many things floating around though, but then again thats what Mark noticed when designing AXE over a traditional solution like this.
Have you seen this one ? https://www.npmjs.com/package/trystero Im testing it to get two browsers connected and it works like a charm, its webrtc so it probably does not scale but it could be interesting
Have you seen this one ? https://www.npmjs.com/package/trystero Im testing it to get two browsers connected and it works like a charm, its webrtc so it probably does not scale but it could be interesting
Agreed. Theres always a way however, the nice thing with hypercores dht is it is key based, so if I dont want my messaging app to be connected to your dht for instance, then it doesnt need to be. So it can scale I guess. At the end of the day its up to the infrastructures design.
hey guys, im trying to use user.recall(), but it doesn't save the alias. the user alias is set to the public key, is this supposed to happen?
this is user.is after i refresh the page
well i can still get the alias using gun.user(pub), still weird that alias isnt available in user.is though
lain: just some quick note, don't rely too much on alias, it can be misleading. The alias is not guaranteed to be unique. You can have multiple people with the same username/alias. It's best to work with pubkey and some custom display name that is saved by the user in his own subgraph
1 reply
also ive been getting these warnings from webpack, is there a way to fix this?
dont know what they mean, idk if its an issue or not
@theaspirational after you or someone else does a screen call with me to upgrade it to latest!!! Who wants to?
@connor-davis :fire: . Wednesday 11am CA it is! w00! ( @lmangani + @Manuel-777 you replied but didn't confirm time? @Dletta )
Yes, so AXE would filter even DHT subscriptions, shouldn't be too hard to add that to what you have already!
@u007 I wonder if it is the AXE bug being aggressive about cutting things off in NodeJS when it shouldn't? try
@jaspermolgvits_gitlab @kuhlmann.markus:matrix.kusys.de @u007 humm? just
@connor-davis @Manuel-777 nice thoughts, tho I think infrastructure should be automated, not require app devs to design it.
@lain:iwakura.xyz bleh I thought that bug got fixed? If you do pubkey login or register then it might not know of an alias. but yeah, seems wrong. Ah, tho @rococtz:matrix.org comment is a much more important point :+1: .
Tell webpack to use gun's prebuilt file so it doesn't try to build it again. Decade of package.json did this automatically, not sure why they changed/broke that.
@WillWang002_twitter are you running default? If you hit up other relay peers
@connor-davis :fire: . Wednesday 11am CA it is! w00! ( @lmangani + @Manuel-777 you replied but didn't confirm time? @Dletta )
Yes, so AXE would filter even DHT subscriptions, shouldn't be too hard to add that to what you have already!
@u007 I wonder if it is the AXE bug being aggressive about cutting things off in NodeJS when it shouldn't? try
GUN({axe: false@jaspermolgvits_gitlab @kuhlmann.markus:matrix.kusys.de @u007 humm? just
npm start or 1-click deploy it. Am I misunderstanding the Q?@connor-davis @Manuel-777 nice thoughts, tho I think infrastructure should be automated, not require app devs to design it.
@lain:iwakura.xyz bleh I thought that bug got fixed? If you do pubkey login or register then it might not know of an alias. but yeah, seems wrong. Ah, tho @rococtz:matrix.org comment is a much more important point :+1: .
Tell webpack to use gun's prebuilt file so it doesn't try to build it again. Decade of package.json did this automatically, not sure why they changed/broke that.
@WillWang002_twitter are you running default? If you hit up other relay peers
/stats.html you see it there. Not if you have a custom server tho.
9 replies
UPDATE:
I'm gonna aggressively start pushing towards and testing against encrypted p2p webgl gaming.
If you didn't already see 1 of the demos, this is latest: https://twitter.com/marknadal/status/1465135435965878273
I then found out FireFox let's me push more triangles to screen than I can natively in Rust! (see my other tweet, I'm mind boggled by it) tho Chrome sucks, so that could be an adoption hiccup without downsampling.
This initiative will be split into 2 main categories:
(A) actually implementing a micro-game based on some sci-fi stories I have (or yours?)
(B) migrating learnings from (A) to an reusable p2p tools for it and R&D into stuff like Nanite-in-browser and AI-based evolutionary physic simulations.
If you'd like to help build a game, I'll be doing video calls teaching people how to learn webgl & stuff, let me know if you want to join.