there is no concept of sourcing content beyond that, it's fundamentally a pretty simple setup
I don't know a ton about it yet (will need a few months)
sweet
but it doesn't do relays
so it isn't hard to add that to the outskirts
with a goal of federating/distributing beyond that
yeah that was kind of my thinking
that the problem of scaling a single cohesive/managed service is a separate problem from scaling the communication between those services
IE, if it isn't tracking vectors/etc., then doesn't matter
and content hashed identifier based nature of nab
tho I'm a little worried it'll be abused to store spam
I wonder if it'd be OK to have it auto-expire after X months
tho I know people hate that about IPFS, it just forgets stuff.
if it is text data sure let's sniff it all
but, now that people are doing video/audio, :/ :/ :/ :O
that bloats storage costs insanely fast
nobody got da money for dat
if(msg.put.length >= 1024 * 1024 * 1024){ mesh.peer({dam: 'send_paywall', pay_us_money_or_lose_your_puppy_photos: true, other_peers_you_might_get_away_with_it: [...]}, peer) }
I hate crypto tokens
tho I think it will be inevitable to have to have to meter bandwidth expenses and request bill pays
@bmatusiak you'll need to do that under a
gun.user()account, all data written there is protected from tampering, and can optionally be private, encrypted (by default it is public tho). There is no "root" in a graph database, just the data node you "start" at, which in this case, would be the user node (note: user nodes can be organizations, individuals, or one-off throwaway accounts) they're backed by cryptographic validation. If you haven't already seen these articles, I recommend checking out:
- https://gun.eco/docs/User#auth
- a good tutorial that covers the basics: https://gun.eco/docs/Todo-Dapp
- https://gun.eco/docs/Cartoon-Cryptography high level concept explainers (1min animated series)
- https://gun.eco/docs/SEA for more details on the cryptography
and WELCOME WELCOME WELCOME :) :) :) :zap: :zap: btw, @bmatusiak :) how'd you hear about us? What are you wanting to build? What are you skilled at? What are you passionate interested in learning? :)
[D]nonayerbiz: ah here it is... https://github.com/TensorTom/superPeer my Discord has impressive search.
@amark well i want to build a blockchain dapp casino starting with a few different games like hi/low and blackjack and a timed faucet (pretty much doing some pow with gambling is the reward), -- im not skilled in a single thing, i pretty much can do it all, just time and confidence , i found gun but searching the word "nodejs blockchain" and i found https://github.com/nomic-io/lotion, and keep digging and found gun though it was interesting project, i mostly work with nodejs, i love node-webkit(nwjs) for desktop apps.
so i have another question, https://github.com/amark/gun/wiki/Transactions this looks very much like it can be used for events. so the question is( and i know i can test this but wanted to point out the idea first) can Alice message Bob, if Bob is doing
me().get( "message" ).map( handleMsgEvent ), when Alice has no write permission doing bob.get( 'message').put( { name : 'pubkey', message:'encrypted' } ): , so , "Can Alice message Bob? When Alice has no write permission on Bob's db?", (i assume Alice needs permission to .put in bobs userdb,and if so, it would be nice to find a way to set a spot where a user can let anybody write to a key in your userdb if you 'allow it')
[D]jabis: neat 🙂
[D]nmaro: <@!203666215502217216> I think that eventually I'll add user capabilities, but not how one might expect: all resources will still have their own private keys - it's just that users will be able to store a library of such resources (incl. those private keys) in their own "account".
[D]circles: <@321271119304720384> sounds great. One more feature request: adding loading spinners to every app’s initial startup. It’s confusing when looking at a blank screen