4 ms·

Probably against ToS, so can get your account banned (happened to sixcord dev). It does follow a client/server model so your server asks like a proxy/BNC while

by Fnoord 5y ago

Probably against ToS, so can get your account banned (happened to sixcord dev). It does follow a client/server model so your server asks like a proxy/BNC while your client(s) connect(s) to your server.

fxtentacle 5y ago
Luckily, this doesn't matter if you create an entirely new community, because then you won't need the discord interop.
- toomuchtodo 5y ago
  Now we just need distributed crypto identity (open source keybase) so you can maintain identity across platforms, with the ability to transparently sign and verify messages regardless of where they’re persisted. This would allow for message logs to be ETLd while timestamps and provenance is maintained.
  - wizzwizz4 5y ago
    You mean like https://keyoxide.org/ https://keyoxide.org/?
    - toomuchtodo 5y ago
      Yes! This is what I was looking for! Thanks!
  - ben0x539 5y ago
    I don't even want to maintain identity across Discord servers, I certainly don't want to automatically-verifiably maintain identity across completely separate platforms. :(
    - toomuchtodo 5y ago
      I’m by no means suggesting it be mandatory, only available for those who do want to maintain their identity across disparate systems. If you want to be $random_uuid, that’s fine too.
  - all2 5y ago
    Can we do this with Mastadon or the Matrix comms standard? I have no clue how federated ID would work. Maybe some interop with PGP?
  - altantiprocrast 5y ago
    Technically, PGP can already do that using something like [keyoxide](https://keyoxide.org/4AF679D0ABA0ED4B07BF7B6932CA3267C8D187D7 https://keyoxide.org/4AF679D0ABA0ED4B07BF7B6932CA3267C8D187D...). The user experience of creating and managing keys is very bad though.
  - teirce 5y ago
    An aside: I realize I've been brainwashed by popular shorthand nomenclature when I see 'crypto' and immediately cringe. My brain expanded this to 'crypto [currency] identity', despite its usage in this sentence clearly meaning 'crypto[graphic] identity'.

by Fnoord 5y ago

fxtentacle 5y ago

Luckily, this doesn't matter if you create an entirely new community, because then you won't need the discord interop.

toomuchtodo 5y ago
Now we just need distributed crypto identity (open source keybase) so you can maintain identity across platforms, with the ability to transparently sign and verify messages regardless of where they’re persisted. This would allow for message logs to be ETLd while timestamps and provenance is maintained.
- wizzwizz4 5y ago
  You mean like https://keyoxide.org/ https://keyoxide.org/?
  - toomuchtodo 5y ago
    Yes! This is what I was looking for! Thanks!
- ben0x539 5y ago
  I don't even want to maintain identity across Discord servers, I certainly don't want to automatically-verifiably maintain identity across completely separate platforms. :(
  - toomuchtodo 5y ago
    I’m by no means suggesting it be mandatory, only available for those who do want to maintain their identity across disparate systems. If you want to be $random_uuid, that’s fine too.
- all2 5y ago
  Can we do this with Mastadon or the Matrix comms standard? I have no clue how federated ID would work. Maybe some interop with PGP?
- altantiprocrast 5y ago
  Technically, PGP can already do that using something like [keyoxide](https://keyoxide.org/4AF679D0ABA0ED4B07BF7B6932CA3267C8D187D7 https://keyoxide.org/4AF679D0ABA0ED4B07BF7B6932CA3267C8D187D...). The user experience of creating and managing keys is very bad though.
- teirce 5y ago
  An aside: I realize I've been brainwashed by popular shorthand nomenclature when I see 'crypto' and immediately cringe. My brain expanded this to 'crypto [currency] identity', despite its usage in this sentence clearly meaning 'crypto[graphic] identity'.