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.
this includes like cool interactive art projects and data visualizations ( and @i001962 & @noctisatrae are helping build a long run pipeline/platform for this, with a whole browser-based advanced statistical error tracker)
ok, gotta wake up in 5 hours :( cheers, cya!
(oh last comment: eventually one of these games is gonna explode, and AXE already cant handle the existing millinos of users, so we need need need DHT team to get things scaling ASAP! For the existing users, let alone for intense apps like gaming, will be even more performance/benchmark needing!)
i think it might be causing issues with my vercel build of the site but not 100% sure
it works locally, but on the vercel site im getting this error
may be unrelated to gun tho
i dont use bigints anywhere, wasn't sure if gun did or something
@lain:iwakura.xyz That line is fully using bigints, not mixing types, so that issue is rather odd
i found this which seems to be the same thing, doesnt look like a gun issue
Hi, I am new to gun, and I have a very basic question but its confusing me a lot. I am trying to make the friends example but I don't understand how to get/listen to alice friends. My code looks like this:
const GUN = require('gun/gun');
const gun = GUN({localStorage: false, radisk: false});
const alice = gun.get('alice').put({name: 'alice'});
const bob = gun.get('bob').put({name: 'bob'});
const users = gun.get('users');
users.map().on(user => console.log(user));
users.set(alice)
users.set(bob);
alice.get('friends').map().on(friend => console.log("Alice Friend", friend));
alice.get('friends').set(bob);
But alice.get('friends').map ... doesnt print anything.
on the last line
You're not making Bob Alice's friend. You're putting the Gun constructor in there
I think 'bob' should be a string
so ive trying to understand how gun works but im a bit confused on some stuff. if i create a key value pair in my user graph that only i can update, how is this guaranteed? peers can reject the update if its not me that tried to update the value, but given the value can i prove that i was the only one that updated it?
hmmmmm i think im, starting to get it. i keep thinking of it in terms of an immutable blockchain where you can view the whole history of a value, but if im understanding this right this is mutable in that you can only read the current value, not any past values
but the principles of authorization and ownership verification are the same
Found the problem,
const GUN = require('gun');
const gun = GUN(/*{localStorage: false, radisk: false}*/);
const alice = gun.get('alice').put({name: 'alice'});
const bob = gun.get('bob').put({name: 'bob'});
const users = gun.get('users');
users.map().on(user => console.log(user));
users.set(alice)
users.set(bob);
alice.get('friends').map().on((friend, k) => console.log("Alice Friend", friend, k));
alice.get('friends').set(bob);
alice.get('friends').set(alice);So apparently I can't disable storage, so is there a way to run gun only in memory ?