00:41 <stellar-slack> <dzham> @jonh: Vanilla is still a bit heavy. I’ve developed customizations on it, and I’ve run forums on it. I’d suggest NodeBB instead

00:43 <stellar-slack> <dzham> Nano sats are still, uhm, a bit expensive, but if we’re going to the moon, low-earth orbit is on the way :)

01:11 <M-matthew1> i just noticed you folks are looking at bootstrapping stellar peers from SRV records?

01:12 <M-matthew1> just wanted to let you know that we deeply regret using SRV records in Matrix as a way of identifying nodes, and are trying to transition to using .well-known URIs instead as the primary way of publishing discoverable nodes for a domain

01:12 <stellar-slack> <jed> graydon ^

01:13 <M-matthew1> as it appears most folks are much happier publishing some JSON by HTTP on foo.com/.well-known than messing around with DNS

01:14 <M-matthew1> (you find people trying to create SRV records to CNAMEs, just screwing up the TTLs, or the app caching stale DNS irrespective of the TTLs, or having weirdness with IPv6 DNS, or their crappy DNS not supporting SRV records, etc. etc.)

01:15 <M-matthew1> (also, you should be using a FOSS standards-based decentralised comms system like Matrix rather than Slack, but that's another story :D)

01:15 <stellar-slack> <jed> you work on matrix?

01:15 <M-matthew1> yup, i'm the proj lead.

01:16 <M-matthew1> and was poking in stellar-core whilst taking a look at using SCP as a possible building block for solving our decentralised identity/reputation problem

01:16 <stellar-slack> <jed> Just looking at it now. looks pretty cool

01:16 <M-matthew1> :)

01:17 <stellar-slack> <jed> yeah it should work well for that I think

01:22 <M-matthew1> cool. we're playing with the idea of needing a decentralised but consistent/trustworthy datastructure to keep track of which 3rd party IDs (e.g. email addresses, phone numbers etc) map through to opaque-ish matrix IDs, and perhaps store folks' public keys, and potentially even a global reputation score

01:23 <stellar-slack> <jed> I'm just adding a thing now to let you associate meta data with accounts. You could potentially use this for that.

01:23 <stellar-slack> <dzham> PSA: that’s http://matrix.org|matrix.org BTW

01:23 <stellar-slack> <dzham> looking good

01:24 <M-matthew1> do you also have the same problem of how to actually identify humans based on 3rd party IDs like email addresses in stellar itself?

01:24 <M-matthew1> (amused that these messages are going matrix client -> matrix -> matrix -> matrix-irc -> freenode -> slack-irc -> slack -> slack client :/ i dread to think what the latency is)

01:24 <stellar-slack> <jed> heh

01:26 <M-matthew1> (currently matrix maintains a logically centralised but physically distributed DB for 3PID (third party ID) to MXID (matrix ID) mappings, modelled vaguely after DNS root servers, and it's an increasing point of contention given the rest of the system is entirely decentralised).

01:26 <stellar-slack> <jed> financial institutions that use stellar do have this problem since they have to know who they are sending or receiving money from

01:28 <stellar-slack> <jed> I have a half baked idea of allowing people to tie their keybase ID to their stellar account but haven't thought it through yet.

01:28 <M-matthew1> right. so keybase is probably closest to what we're after too... except it's unashamedly centralised too

01:29 <M-matthew1> and nobody seems to have a good decentralised alternative. there's stuff like onename.io and namecoin, but blockchains don't seem the best medium for storing that

01:31 <M-matthew1> hence looking at SCP to share keybase-like 3rd party identity assertions between 'trusted' identity verifiers (fsvo of trust)

01:32 <stellar-slack> <jed> hmm yeah I think it would be straight forward with this extension to stellar I'm adding now. You can just attach the PGP key to your account and do the same keybase style verification of various social media to confirm

01:33 <M-matthew1> i'm (obviously) not that familiar with stellar yet, but would the account metadata itself have any consensus semantics in the ledger? looking at the schema it looks like it just sits in a given node?

01:36 <stellar-slack> <jed> what do you mean consensus semantics? the meta data would be associated with a particular stellar account so only that account could modify it. so you can have the same level of assurance as you do with keybase that this public key is controlled by the same person that controls this ,twitter/reddit/whatever account

01:37 <M-matthew1> guess i'm just trying to understand where stellar accounts get stored, and if they're decentralised within the ledger, what assertions about them SCP enforces to make them consistent. but i'll go read up some more; no need to waste time answering newbie questions

01:38 <stellar-slack> <jed> ah yeah : https://www.stellar.org/developers/learn/concepts/ledger.html

01:38 <M-matthew1> (hah, it looks like you do the same thing of shoehorning the same SQL to work on both sqlite and postgres that we do. unless soci is providing a proper abstraction layer of some kind)

01:38 <M-matthew1> thanks.

01:39 <stellar-slack> <jed> the ledger and accounts are all verified by SCP so are decentralized

01:58 <M-matthew1> jed: okay, am a bit more up-to-speed now. for your account metadata stuff, what would the transactions look like that which propagate the metadata? and how would other peers know whether to accept the metadata? (and am i right in understanding that any transaction, including metadata updates, would incur a fee?)

02:00 <stellar-slack> <jed> there would be a new operation that can attach/modify/delete data to an account. it will just take: accountID, key, value

02:00 <stellar-slack> <jed> anyone can look in the ledger to see what data is associated with what account

02:01 <stellar-slack> <jed> there is a small fee on all transactions but it is very small I think 1 cent will get you like 100k transactions

02:02 <M-matthew1> okay, and thanks for unpicking the q's. final question for now: any idea when the metadata stuff might land?

02:03 <stellar-slack> <jed> I think soon. It is in PR now. I just want to get some feedback from others before landing

02:03 <M-matthew1> cool :)

02:04 <stellar-slack> <dzham> @jed: Reserve? Same as other operations that store data?

02:04 <stellar-slack> <jed> yeah

04:52 <stellar-slack> <thewind> Hi

04:59 <stellar-slack> <thewind> おはようございます。

17:00 <Arathorn> stupid question, but: how do I actually open a stellar account now? can I create keypair with genseed and then xfer funds to it from XBT via something like kraken?

18:49 <stellar-slack> <bartek> yeap, you can also try https://lobstr.co/ and they will open an account for you.

19:45 <M-matthew1> thanks

22:32 <stellar-slack> <john> Here is another great link for picosatellites' hobbyists: http://www.cubesat.org/index.php/collaborate/suppliers