Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 13:50
    antiochp edited #3618
  • 13:50
    antiochp edited #3618
  • 13:50
    antiochp edited #3618
  • 13:50
    antiochp edited #3618
  • 13:50
    antiochp edited #3618
  • 13:49
    antiochp commented #3629
  • 13:39
    antiochp commented #3634
  • 13:36
    antiochp commented #3634
  • Apr 16 01:20
    bladedoyle commented #3624
  • Apr 16 01:18
    bladedoyle edited #3624
  • Apr 15 18:34
    trevyn commented #3634
  • Apr 15 17:56
    trevyn commented #3634
  • Apr 15 17:28
    phyro commented #3634
  • Apr 15 17:27
    trevyn edited #3634
  • Apr 15 16:34
    trevyn edited #3634
  • Apr 15 16:33
    trevyn opened #3634
  • Apr 15 16:22
    phyro commented #3624
  • Apr 15 16:21
    bladedoyle commented #3624
  • Apr 15 16:19
    bladedoyle synchronize #3624
  • Apr 15 01:26
    bladedoyle commented #3624
Antioch Peverell
@antiochp
(and it gives me some time tomorrow to focus on changelog etc.)
lehnberg
@lehnberg

Quentin wrote:

Regarding the package thing we have created a repo with @JosephGoulden and Joseph added the ubuntu snap there https://github.com/mimblewimble/packaging. Future work would be to find a way to automate this for each release or at the very least have a check list somewhere with all the tasks required. I'd be also in favor of adding choco, ubuntu and debian (apt) if possible though I'm not very familiar with the process.

Yeastplume
@yeastplume
Okay, think that's moving along anyhow, we can come back to it in more detail at a later date
hrm.... are we genuinely in the mood for a project focus discussion right now?
Antioch Peverell
@antiochp
suspect very little will be done on this until post 3.0.0
lehnberg
@lehnberg
Sorry gitter hanging up on me
I don’t have anything to add to that focus discussion rn
Yeastplume
@yeastplume
Gitter being unusable right now.. think we're done for now anyhow, so thanks all!
lehnberg
@lehnberg
:wave:
David Burkett
@DavidBurkett
We should move these meetings to Keybase. Gitter is always unusable
energyburn
@energyburn
Is there a public dev channel on Keybase?
lehnberg
@lehnberg

@DavidBurkett I could definitely be convinced to move the meetings to keybase. Reason we've been reluctant to do it so far is that we've had a big group of people here and wouldn't want to make the meetings less visible, but perhaps it's time to start making a more serious effort to move over main comms over to Keybase?

Gitter is pretty awful. I read that their desktop/mobile apps were getting less frequent updates, so I started using it in the browser instead, but it's just as bad.

David Burkett
@DavidBurkett
Yea, gitter is unusable on an android, and buggy AF on Windows. Keybase works quite well on Windows, Mac, Ubuntu, and Android. Keybase is far from perfect, but imho, it's worth the effort of transitioning. We all have more than enough messaging apps to monitor.
lehnberg
@lehnberg
@energyburn there wasn't, but I just created grincoin#dev and grincoin#crypto for good measure.

If I read the Keybase documentation correct, and if you've got Keybase installed, try running this from your terminal:

keybase chat join-channel grincoin '#dev'
keybase chat join-channel grincoin '#crypto'

Please report back if it works!

David Burkett
@DavidBurkett
That works on mac
lehnberg
@lehnberg
wicked
@DavidBurkett will add to governance meeting agenda next week a point on switching meeting locations
David Burkett
@DavidBurkett
Thanks!
lehnberg
@lehnberg
done
Joseph Goulden
@JosephGoulden
I would also prefer meetings to be on keybase. Don't really like that conversation is split between here and there.
Yeastplume
@yeastplume
:+1: for moving to keybase
Jason Comito
@jcomito
anyone know, does keybase work okay with Brave browser?
David Burkett
@DavidBurkett
@jcomito There's no web version. It requires installing the client, unfortunately
Antioch Peverell
@antiochp
making some progress on the Changelog for 3.0.0 here mimblewimble/grin#3166
also feel like we are in a really good shape with respect to fast sync stability (current master, soon to be 3.0.0 beta.2)
its a lot better than 2.1.1 put it that way
lever
@1971192997
hi there How are tx fees calculated?
John Tromp
@tromp
see https://github.com/mimblewimble/grin/blob/2ee8d06d483649647e39a172693a7522496b8a27/core/src/libtx/mod.rs
lever
@1971192997
got it， thanks
Quentin Le Sceller
@quentinlesceller
@tromp could you fix the merge conflict here mimblewimble/grin-miner#231 ?
John Tromp
@tromp
will take a look
Quentin Le Sceller
@quentinlesceller
:+1:
John Tromp
@tromp
should be good now?!
Quentin Le Sceller
@quentinlesceller
Yes it is :)
Quentin Le Sceller
@quentinlesceller
@tromp trying to build latest Cuckaroom plugin but getting: 
/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(148): warning: variable "sizeC" was declared but never referenced

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(534): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(535): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(536): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)

/home/op/mimblewimble/grin-miner/cuckoo-miner/src/cuckoo_sys/plugins/cuckoo/src/cuckaroom/mean.cu(537): error: expected a comma (the one-argument version of static_assert is not enabled in this mode)
Issue opened here mimblewimble/grin-miner#232 with complete error log
John Tromp
@tromp
taking a look
John Tromp
@tromp
try latest cuckoo commit
Quentin Le Sceller
@quentinlesceller
Ok
Quentin Le Sceller
@quentinlesceller
Looking good thanks !
Blade Doyle
@bladedoyle
It seems like grin discussions are bifurcating. Gitter, discord, keybase, telegram, more? Its hard to even find all of them, harder to try to check them all.
energyburn
@energyburn
Consequences of decentralization?
Blade Doyle
@bladedoyle
Now there appears to be several different parallel keybase groups? There are grincoin .teams.node_dev #general and grincoin.teams.wallet_dev #general and also grincoin #dev , and grincoin #general, etc.
We have almost as many chat groups as API versions :-/
johndavies24
@johndavies24
lol, i agree, hard to keep up
Quentin Le Sceller
@quentinlesceller
Floonet HF latest estimation: 2019-12-22 22:25:01
lehnberg
@lehnberg

I agree @bladedoyle there are many teams and channels. The intention when we set it up was to allow wallet dev and node dev work to proceed more independently, possibly with different people engaging where they were more interested.

Now after it’s been running for a while we can ask ourselves whether it’s really necessary at this stage and whether it would be more beneficial for development work to have a single team with different channels instead?

Dunno, I can see merit to both approaches tbh. At least now that we’ll try to migrate gradually away from gitter we’ll have one place less to check!

John Tromp
@tromp
Floonet HF latest estimation: a few minutes ago