Thanks for pointing out that small pools benefit from less strict mempool policy nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy0hwumn8ghj7mn0wd68yttjv4kxz7fwvf5hgcm0d9hzumnfde4xzqpq85h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qtyz2zr . I hadn't considered that.
Do you think Bitcoin core could benefit from moving the social interactions around the repository to nostr? gitworkshop.dev features nostr based pull request and issue management for instance.
Absolutely! Gitworkshop.dev has improved a lot since Fabian Jahr last checked it out. I think this is a great opportunity to give it another shot..
Thanks for pointing out that small pools benefit from less strict mempool policy nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy0hwumn8ghj7mn0wd68yttjv4kxz7fwvf5hgcm0d9hzumnfde4xzqpq85h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qtyz2zr . I hadn't considered that.
Do you think Bitcoin core could benefit from moving the social interactions around the repository to nostr? gitworkshop.dev features nostr based pull request and issue management for instance.
@npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr after realizing that miners who are too small to receive transactions out of band benefit from a permissive relay policy, I'm starting to wonder if DATUM and StratumV2 are the right tools for node operators to express their opinions rather than mempool policy.
Perhaps its time to stop calling our nodes "full nodes" if they aren't producing cost effective hash-rate.
Whats your take on this?
Thanks for pointing out that small pools benefit from less strict mempool policy nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy0hwumn8ghj7mn0wd68yttjv4kxz7fwvf5hgcm0d9hzumnfde4xzqpq85h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qtyz2zr . I hadn't considered that.
Do you think Bitcoin core could benefit from moving the social interactions around the repository to nostr? gitworkshop.dev features nostr based pull request and issue management for instance.
Bitcoin Core Going Rogue?
https://blossom.primal.net/84a48874e563ed3373810b6b6a4ed763cd3d64b982d6b1ac3b6e46fa24e924c8.mp4
Thanks for explaining whats going on nostr:nprofile1qy8hwumn8ghj7mn2w4khqtndv5hszythwden5te0dehhxarj9ekxzmny9uqzpprrqa5g5z0vzy5k06c9gnnc485gcj84qufv88k5j8ljkmaqrxhgkgzyc0 !
nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr perhaps this is an opportunity to start using `ngit` for social interactions around the bitcoin core repo.
Ngit creates nostr events for commits, pull requests and issues and there is a nostr client (gitworkshop) for interacting with these events. Essentially this nostr client acts as a proxy between you and the git server, so you can continue to share a repo with users who are still doing social interactions on github.
nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngmyntqg is maintaining this and it has made tremendous progress since the last time a core dev (Fabian Jahr) tried it out. This controversy could be an opportunity to move away from the network effects on GitHub..
Which pull request is it? Can you link it for us?
Gitworkshop just keeps getting better every time I look away. Thanks for adding the (perhaps controversial) delete feature nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd
I love how the deleted PRs are still visible to remind us that we can't un publish nostr events.
Also nice to see that squashed branches have a new history now 😀
Gitworkshop just keeps getting better every time I look away. Thanks for adding the (perhaps controversial) delete feature nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd
Is that a V shaped wing tip? Looks like a 737 max..
Working on removing myself from Google:
Step 1: get a nostr:npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5 phone (a Pixel 🤦♂️) ✅
Step 2: start using nostr:npub18q57qr3t07qljnapzqldaqa7ru2qwfpfnjdrwvhk327n3sc82f0qqwrs6f mail ✅
Step 3: start using Proton Docs ✅
Still many steps ahead, but the direction is clear. nostr:note1w3m6k060zc30eqnaeh7ms4vqlyl4v0x3vggcfw7xsym8uxsudtxsy82r27
Have you considered cryptpad.fr instead of proton for docs?
When nostr?
Flash memory cells don't keep working forever. The more times each cell is written to, the more it degrades. Wikipedia states that typical memory sticks are only designed to have each cell written to a few thousand times before the degradation causes data corruption.
Most devices use a technique called "wear levelling" that attempts to spread writes around the memory. That means you're not constantly hammering the same cells and causing them to fail when the rest of the memory is still fresh. Because of wear levelling, a USB flash drive should last until the amount of data that has been written to it is approximately a few thousand times its capacity. For example, a gigabyte drive should be able to cope with a few terabytes of data being written to it, over its lifetime.
I'm not sure what you mean by "full erasing" but I guess it means either overwriting all the data on the card or overwriting the entire card. That has just the same effect as writing the same amount of data, in terms of memory wear. So, for example, writing a megabyte of data and then overwriting it all should have roughly the same effect, in the long term, as just writing two megabytes of data. Reformatting the flash drive should have roughly the same effect as completely filling the card with data.
So, long story short, if every time you write data to the drive, you eventually delete it by overwriting, that should roughly halve the life of the drive (as compared to a standard operating system delete, which just marks the areas of the card as unused, without overwriting the data stored there). Maybe you care about that; maybe you don't. It would have been good for a few thousand uses; now you can "only" use it a couple of thousand times.
If you delete by reformatting, the drive will wear faster: if you fill the drive to x-percent, then reformat, you're writing as much data as you would if you filled it to (100+x)-percent. If you just deleted the data, you'd be able to use the drive a few thousand times 100/x times; reformatting means you only get to use it a few thousand times 100/(100+x) times. The life of the card is reduced by a factor of (100+x)/x. For example, by a factor of three if you only half-filled it, and by a factor of 11 if you were only 10%-filling it.
I love these new gitworkshop features!
Thanks for your amazing work nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr and nostr:npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr !
For interoperability
You may think I'm a `c03rad0r`, but I'm not the only one.
Thanks, that worked 😃
It doesn't show up in the search though...
nostr:nprofile1qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqsg8lg8m6dhvve5ejw5dunctsj43ekza2l705xxass5ve7t4mzs63cckktdx it costs facebook almost nothing to have traffic within its own networking infrastructure. They only need to start paying once they send traffic through a gateway, because they are using someone else's infrastructure at that point. #TollGate enables anyone with access to a gateway to undercut facebook's data plans.