-
Notifications
You must be signed in to change notification settings - Fork 54
Community Call #11
Gigi edited this page Mar 24, 2022
·
12 revisions
Resources for the community call today 728,533 (2022-03-22, 17:00 CET).
- 📹 Recording: YouTube, BitcoinTV
- 📝 Call Notes
- User Surveys
- Representation (and naming) of Mixdepths (and language in general)
- --> See Edi's Figma
- Merged & open PRs
- Priorities, next versions
mandel
mandel says:Hi all
17:05
tbk
tbk says:it's called "jars" now : D
17:08
me says:Hi mandel 👋
me says:lmao not sure about "jars" - I mean I like it, but I'm not sure if it makes things more clear 😄
17:09
openoms
openoms says:they are Deposit and Change addresses is you wan tto jeep the distinction
openoms says:need to think what to show if the balanceis zero, but it was used
17:12
me says:good point 👍
17:12
mandel
mandel says:I'd definitely still argue good old 'mixdepths' is more clear and useful
17:13
me says:Typo: "Interal" -> should be "Internal"
17:17
mandel
mandel says:Agree that the current JM labels are very useful and should be clear to users in Jam UI. Current labels include 'change-out', 'cj-out', 'deposit', 'new'
17:17
me says:Agree, should be visible for this expert view; but as we mentioned the last time, the best case would be if we wouldn't have to expose all that stuff to the user in the first place.
17:18
mandel
mandel says:Understood. Sorry, this is the first Jam meet I've made it to. Will try to catch up
mandel says:Holy grail is certainly to have all of this abstracted and automated such that best-practices are enforced by the UI
17:20
me says:No worries, the relevant recording is linked here:
https://github.com/joinmarket-webui/joinmarket-webui/wiki/Representation-of-Mixdepths
17:23
mandel
mandel says:👍
mandel says:I'd argue that used addresses should never be exposed to users in Jam by default
17:32
me says:👍
me says:
https://github.com/joinmarket-webui/joinmarket-webui/pull/184
me says:Sweep PR 👆
17:41
mandel
mandel says:I think we should be working to increase the prevalence of fidelity bonds through ease of use (e.g. make it the default), versus appeasing makers desire for earnings
mandel says:optimisation of privacy at all costs
mandel says:usability go up => liquidity go up
mandel says:gamification to incentify privacy?
mandel says:incentivise
mandel says:Agree. FB + maker by default.
17:50
me says:Link to user survey, since I mentioned it:
https://twitter.com/dergigi/status/1506200933709094912
17:51
mandel
mandel says:It needs to be very clear in the UI 1) that coins will be locked up 2) why they are 3) what the consequences are of not using (hopefully default) FB
17:52
openoms
openoms says:the privacy issue is important with automatically sending deposits to FB
17:54
mandel
mandel says:Solution: tumbler into auto FB maker
mandel says:This would be a great way to 'gatekeep' ( the good kind) the maker pools
mandel says:Enforces high quality mix
17:56
openoms
openoms says:agreed - we are on the right path
17:57
mandel
mandel says:Would be great as a requirement if UI can be suitable slick
17:57
openoms
openoms says:👏
17:57
mandel
mandel says:👏
17:58
tbk
tbk says:Is there capacity for developing api access to the tumbler in clientserver?
17:58
edi
edi says:recording will stop at ~1:10 😉
17:58
tbk
tbk says:👏
18:02
Christoph
Christoph says:👏
18:00
mandel
mandel says:Great work on the Figma
18:01