<BlueMatt[m]>
has anyone played around with radicale? we're (LDK) getting really tired of github being broken (unicorn/503s all the time) let alone flaky and their apparent increased desire to charge money. it seems something decentralized where things like comments are authenticated would be a big win in terms of removing third-party trust too, but curious if anyone has played with it/thinks its production-ready.
___nick___ has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
<sipa>
radicle, you mean?
jonatack has quit [Ping timeout: 264 seconds]
<sipa>
i've heard the name, but never played with it
jonatack has joined #bitcoin-core-dev
<dodo>
c
jonatack has quit [Ping timeout: 245 seconds]
<BlueMatt[m]>
sorry yes lol
<BlueMatt[m]>
radicale is great, but unrelated...
<bitcoin-git>
[bitcoin] hebasto opened pull request #34319: Drop some `IWYU pragma: export` and document IWYU usage (master...260116-iwyu-export) https://github.com/bitcoin/bitcoin/pull/34319
<BlueMatt[m]>
only real question i have is if they have any kind of ability to moderate comments, if they do (eg if we can just set up some automated "please go to this website and pass a captcha/deposit 10 sats to comment" thing) then istm very worth trying for a few months
<BlueMatt[m]>
otherwise you're gonna get flooded by bots and garbage
<flooded>
you rang?
<BlueMatt[m]>
also i guess whether you can comment/open issues via the web ui or if you have to use the tui
brunoerg has joined #bitcoin-core-dev
<BlueMatt[m]>
ah you cant allow randos to comment via the web interface, but you can run an instance locally and then comment via the web. bleh so close. nevermind
<darosior>
cc laanwj
<darosior>
i know she's been keeping track of radicle for a while
<BlueMatt[m]>
yea, it seems like they've got most of the big pieces in place but are short a few major items (at least the above two) before its really something to switch to.
<BlueMatt[m]>
looks like they have a draft spec for separating users and nodes but first have to do that then you could imagine a webui that is more traditional github-like for those who dont want to do cli tools
<BlueMatt[m]>
so probably using it is blocked on that
brunoerg has quit [Remote host closed the connection]
SakshiKasat18 has joined #bitcoin-core-dev
<laanwj>
<darosior> "i know she's been keeping..." <- there was a time i was actively watching radicle. at the time it was far from usable for any kind of real project with many contributors. it's been a while though
<laanwj>
also they started using some kind of block chain token, which made me mostly lose interest
<laanwj>
they do have a desktop version
<darosior>
oh yikes
Cory12 has joined #bitcoin-core-dev
<laanwj>
according to the faq (searching for "token") https://radicle.xyz/faq they say they only use it for financing development. there were times they wanted to integrate it into the software itself, i'm glad they reconsidered
Cory34 has quit [Ping timeout: 272 seconds]
SakshiKasat18 has quit [Quit: Client closed]
l0rinc has quit [Remote host closed the connection]
l0rinc has joined #bitcoin-core-dev
PaperSword has quit [Quit: PaperSword]
durandal_ has quit [Ping timeout: 250 seconds]
jonatack has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
durandal_ has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
memset has joined #bitcoin-core-dev
Guest72 has joined #bitcoin-core-dev
Guest72 has quit [Quit: Client closed]
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] l0rinc opened pull request #34320: coins: replace remaining `HaveCoin` calls with `GetCoin` (master...l0rinc/remove-HaveCoin) https://github.com/bitcoin/bitcoin/pull/34320
<laanwj>
Matt Corallo: as for more decentralized git hosting solutions, there's also https://tangled.org/ which is kind of popular nowadays. i don't know any details
l0rinc has quit [Quit: l0rinc]
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 246 seconds]
l0rinc has joined #bitcoin-core-dev
Cory65 has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
Cory12 has quit [Ping timeout: 272 seconds]
<BlueMatt[m]>
<laanwj> "also they started using some..." <- Afaiu they basically issued a token then took the money to fund development and have now removed any connection to the token lol. Kinda scammy but I guess that’s one way to fund development….
<BlueMatt[m]>
<laanwj> "Matt Corallo: as for more..." <- Ugh looks more federated than decentralized. Would be nice to avoid just having a hosted service that’s federated…doesn’t seem as exciting
<fjahr>
BlueMatt[m]: Have you considered self-hosting gitlab? It's a bit overkill for sure but works pretty well if someone is willing to do the maintenance, probably doable with 1-2h per month.
<BlueMatt[m]>
<fjahr> "Matt Corallo: Have you considere..." <- probably more likely gitea than gitlab, looks cleaner and much simpler to self-host, but I'm wayyyyy more excited to use something that has built-in cryptographic authentication and redundancy than just go self-host a github replacement.
Cory47 has quit [Ping timeout: 272 seconds]
<BlueMatt[m]>
I already hate enough that ACKs aren't in any way authenticated aside from "github says they came from someone with the right cookie"
<BlueMatt[m]>
something where you can do reviews offline and sync them later natively is also a really cool win for devs that want it (but requiring it for everyone to open an issue wouldn't really be okay)
<BlueMatt[m]>
in theory radicle looks like nearly exactly what i want from a "source forge" (as they call it), except for the above issues
durandal_ has joined #bitcoin-core-dev
timbo_xyz has joined #bitcoin-core-dev
jonatack has joined #bitcoin-core-dev
<sipa>
it looks designed for a situation where every contributor runs their own radicle node, so you can use node key as user identifier, and give permission based on those?
<sipa>
but it sounds like you're looking for something with a more social aspect, where external contributors can interact with the project too
WizJin__ has joined #bitcoin-core-dev
dermoth_ has joined #bitcoin-core-dev
dermoth has quit [Remote host closed the connection]
Cory5 has joined #bitcoin-core-dev
WizJin_ has quit [Ping timeout: 240 seconds]
<BlueMatt[m]>
sipa: yes, there appears to be a proposed spec to disentangle the node-id from the person doing the action, so that you can use the same identity across devices.
<BlueMatt[m]>
from there, it seems like a relatively simple leap to have a web ui that allows people to create identities and just interact via a web interface
<BlueMatt[m]>
I don't care toooo much if people can open PRs without running some software (though it would be nice!), but losing the ability for people to easily open an issue seems like a major loss
<BlueMatt[m]>
I suppose you could always wire something up where they just send an email and it automatically creates an issue under some bot account, but then you have to do a ton of work to let them reply to further interaction? kinda meh
dermoth_ is now known as dermoth
Cory90 has quit [Ping timeout: 272 seconds]
<BlueMatt[m]>
but at a high level it would be nice to move off of github onto something decentralized where contributors can do the things they want to do locally and have it all cryptographically signed and offline-but-synced, but also let those who just want to do more drive-by contributions do so in a more traditional manner (bonus points if its via github and just bridged to the other platform!)
<BlueMatt[m]>
even moving to a self-hosted platform has the major disadvantage (or advantage, depending on the project lol) that opening an issue requires someone signing up for yet another account which can definitely prevent issues from being reported.
<BlueMatt[m]>
but if radicle had a user option it would be a pretty trivial patch to just let people submit issues after passing a recaptcha check or whatever, which would be even better cause no account needed (and you just store a cookie to let them reply as long as its the same machine)
___nick___ has joined #bitcoin-core-dev
___nick___ has quit [Client Quit]
___nick___ has joined #bitcoin-core-dev
durandal_ has quit [Ping timeout: 240 seconds]
andreadcorreia has joined #bitcoin-core-dev
andreadcorreia_ has joined #bitcoin-core-dev
andreadcorreia_ has quit [Client Quit]
durandal_ has joined #bitcoin-core-dev
WizJin_ has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] benediktjohannes opened pull request #34321: 3x the same typo (I'm sorry, I don't speak French and I don't know wh… (master...patch-2) https://github.com/bitcoin/bitcoin/pull/34321
jerryf has quit [Remote host closed the connection]
jerryf has joined #bitcoin-core-dev
WizJin__ has quit [Ping timeout: 264 seconds]
jerryf has quit [Remote host closed the connection]
jerryf has joined #bitcoin-core-dev
mudsip has joined #bitcoin-core-dev
mudsip has quit [Client Quit]
Cory50 has joined #bitcoin-core-dev
Cory5 has quit [Ping timeout: 272 seconds]
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] andrewtoth opened pull request #34322: node: Persist private broadcast transactions over node restarts (master...andrew/persist-private-broadcast) https://github.com/bitcoin/bitcoin/pull/34322
Cory50 has quit [Quit: Client closed]
Cory50 has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] fanquake closed pull request #34321: 3x the same typo (I'm sorry, I don't speak French and I don't know wh… (master...patch-2) https://github.com/bitcoin/bitcoin/pull/34321
l0rinc has joined #bitcoin-core-dev
abubakarsadiq has quit [Quit: Connection closed for inactivity]
andrewtoth has quit [Remote host closed the connection]
kevkevin has joined #bitcoin-core-dev
eugenesiegel has joined #bitcoin-core-dev
abubakarsadiq has joined #bitcoin-core-dev
Cory50 has quit [Quit: Client closed]
Cory50 has joined #bitcoin-core-dev
Guest83 has joined #bitcoin-core-dev
Guest83 has quit [Client Quit]
deadmanoz has quit [Ping timeout: 240 seconds]
ozdeadman has joined #bitcoin-core-dev
Cory11 has joined #bitcoin-core-dev
Cory50 has quit [Ping timeout: 272 seconds]
___nick___ has quit [Ping timeout: 264 seconds]
jonatack has quit [Read error: Connection reset by peer]
<eugenesiegel>
I need to reset the global rng between fuzz iterations without creating a new TestingSetup every time, is it acceptable to call MakeRandDeterministicDANGEROUS after I've already called it during init?
<sipa>
isn't it reset automatically?
<eugenesiegel>
Oh huh it is reset in SeedRandomStateForTest at the start, I must have a bug somewhere.
<sipa>
i think there is an exception for strong randomness (like used for generating private keys)
<sipa>
that is not overridden in fuzz/test mode
<bitcoin-git>
[bitcoin] b-l-u-e opened pull request #34323: test: Add comprehensive tests for GetNewChangeDestination (master...test-wallet-getnewchangedestination) https://github.com/bitcoin/bitcoin/pull/34323
<eugenesiegel>
Oh, I could have been more clear. I'm doing a reset similar to how process_message(s) resets the chainman with ResetChainman, except I make a new mempool as well. I have to reset the global rng at the end of the test before I make a new mempool because of the SaltedTxidHasher / SaltedWtxidHasher
<eugenesiegel>
If I don't reset the rng at the end of the test, then I get non-determinism in the next iterations since these hashers are seeded with values from a "dirty" rng
brunoerg has joined #bitcoin-core-dev
kevkevin has quit [Remote host closed the connection]
brunoerg has quit [Ping timeout: 265 seconds]
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
durandal_ has quit [Ping timeout: 250 seconds]
durandal_ has joined #bitcoin-core-dev
abubakarsadiq has quit [Quit: Connection closed for inactivity]