I mute a lot of territories so that when I’m signed in, I only see the most relevant content. If I want to see cats and dogs, I just manually go to that territory.
I also view the site on mobile while not signed in so I can see everything.
Filtering by combined sats volume like ek mentioned is also a great default option.
You've excluded all of my attempts to reason with you and explain things from the screenshot, but that's okay because the real message here is that you are not a user I am worried about losing.
You just wanted to complain and that is of limited usefulness to us. If you think you can do better, please do. I can only tolerate your noise for so long, and you found that limit.
Thank you for your testing feedback, and for your consideration, it will be considered appropriately.
Otherwise, I'd recommend some methods of stress relief, including, but not limited to, crying harder.
I'm wary of going the moderation route - it's too subjective. I like the market based system of SN. In the spirit of Bitcoin, spam can be prevented by increasing the cost to post with each successive post. The cost can rise exponentially or polynomially in the number of posts without upvotes. If a post gets upvoted, then it won't add to your posting cost because the post has added value.
I guess this is not entirely secure against sybil attacks because a user can create multiple accounts to upvote their own posts. I forgot if there was an account creation fee, but if there was then that'd be a solution
Do you think any of these ideas could help counter this trend:
white listing: only open channels with counter parties you can trust not to share balances
black listing: compile a list of known balance sharing nodes and develop open source tools to automatically blacklist them in routing, peering, and channel creation
Taint balance history databases with intentionally bad data
Modify routing algorithms to split payments more aggressively and route through more nodes
Augment the protocol with some kind of payment batching / net settlement protocol
Let's suppose we took the current block size limit, 4mb, and decided that on January 1 we will reduce it to 2mb. Now, Grandma Gemma doesn't want to upgrade, so she keeps running an old node. On January 1, what happens?
Well, Grandma Gemma's node doesn't require blocks to be 4mb -- it will accept anything 4mb or less. Suddenly she starts seeing 2mb blocks. No big deal -- she accepts those too. That's why it's a soft fork, old nodes don't mind the new rules. But let's suppose some rogue miner decided to mine a 4mb block after January 1. What happens?
Well, most of the network rejects that block, because it violates the new rules, but Grandma Gemma accepts it. Chain fork, right? Not so fast: nodes follow the "most work." So unless the rogue miner has more hashrate than everyone else, the chain with "small blocks" will "outgrow" the chain with "large blocks" -- and as soon as Grandma Gemma's node sees a longer chain with more work, she will discard the "big block" and go with the longer/more-work chain.
That is why making the block size smaller is a soft fork: it doesn't cause a meaningful chain split as long as most miners are on board with it. It doesn't have to be all, just more than 51%.
I think it is a matter of perspective. People who don't understand Bitcoin think they are being aggressive owning it but people that understand it know they are being conservative and see it as savings.
The market is so very lopsided between the few gigs offered and the millions of people wanting to do gig / task work l.
That alone is a huge challenge for any gig work /task platform. Then add in how the few gigs are now spread out among a hundred gig / task work platforms.
I built a small python app that I can run alongside my node and accept lightning address payments. It’s nothing new but gave me a chance to play with my node’s LND gRPC api. Note you still need to host a well-known text file somewhere 😃
Good. Should have it done this week. It's a huge pain.
How about a one time migration, from lnurl-auth to another lnurl-auth or user/pwd?
The plan is to allow you to link/unlink a node (via lnurl-auth), twitter, github, or email to your account once you're logged in. So you can use multiple login methods and replace or remove any login method.
To be fair, it's normal procedure during bug reports to ask the user about the behavior they are seeing and what they want to see so we can confirm we understand your problem and can fix it.
A good bug report should include this:
Description with actual behavior
Steps to reproduce
Expected behavior
Since you used "fix" here, we assumed you are talking about a bug and not about a feature request. Sorry for that misunderstanding.
This isn't dumb, the concerted efforts (by the NY times and co) to smear mining, and now this, is a concerted effort to stop bitcoin adoption in the us. This isn't a move from a senile man, this is a move likely backed and funded by banking and other interests
As others have said I hope for a gradual adoption of the masses coupled with steady improvement in the tools around bitcoin. I hope for increased privacy and simplicity of tools. Ideally privacy should be easier than it is today. I hope the average person has bitcoin and has self custody of it.
What do you fear its like?
I fear we will see the US and the tradfi world "sanitize it" and people only use paper bitcoin. I fear that everyone that adopts it will be KYC'd and owned by the state.
What products do you think we'll see?
I think we'll see games using bitcoin. Up and coming games that don't yet exist. Game where bitcoin makes sense. I think we will see more of what we are seeing now. Content creators using bitcoin to support their work. Peer to peer value for value.
Where are the loud voices in Bitcoin wrong?
This one is harder for me but honestly I think a big area is the idea that bitcoin will lead to an anarcho-capitalist utopia. I just don't see that. I do think we will see positive moves away from state power but that vision will probably take centuries if it every happens. I say this as someone sympathetic to that vision.
Others are that real estate is a waste of time as are stocks. I think both of these are highly pumped up by the fiat system but with a non-fiat currency they will return to their place of utility. We still need land. Rental property will continue to be a profitable endeavor as well publicly traded companies. It will just be different. Where I think they are right is that over the next 20 years bitcoin will outperform.
I have 112 referrals and this is because I didn't want to abuse it too much. I used the invitation links only with specific people, after I tested a mass invitation and then stop it. In this way you can "control" a bit who is coming to SN, not all unknown assmilking shitcoiners finding your link in the wild.
This option with invitation links I like it a lot,. especially that you can set exactly the amount.
“referrals” and “affiliates” are terms with shady connotations,
Agreed. I use to invite others, not to be specifically my "referral" but to offer them a new way to communicate with other bitcoiners. I so not care too much about the sats I get from "my referrals", that is not so important. Important is that they bring new good content.
Discussions will be in French, and the event will start at 6pm. If you're interested and in the area, feel free to come! More info on Telegram: https://t.me/BitdevsFR.
My assumption: There were a number of rigs that got powered down by around mid-May as they no longer remained profitable when the exchange rate collapsed. When it was apparent the price wasn't going to quickly rebound (i.e., in a bear market) there were then decommissioned, boxed, and sold to someone else who has a lower cost of electricity and are now being powered back on.
Similar sentiment stated in the mining section of this weekly newsletter:
You want to aim to strike a balance between having too few and too many UTXOs. If your wallet is too fragmented, your inputs may incur a lot of fees in the future. If you have too few UTXOs, you may reveal significantly more information to your counterparties about your stash. E.g. if you pay someone 1 m₿, but use a 1 ₿ input, they learn that you at least have a whole coin. On the other hand, if you want to pay someone 1 ₿ and need to combine ten or more UTXOs to fund the transaction, you may also tell your recipient and the people that sent to you a bunch about your wallet history.
I would avoid splitting everything into round amounts as you propose. Doing so would incur unnecessary additional transactions, the round amounts would be a fingerprint, and having multiple UTXOs of exactly the same amount is less versatile than having that sum composed from different amounts. That said, an exponential distribution seems like a good idea. If I were in your situation, I would take a look at my UTXO pool composition and decide which UTXOs you want to keep, and where you have gaps in the value distribution. Then I’d try to create transactions that each give me one or two UTXOs in those less densely populated value ranges. Be sure to spend UTXOs with inefficient script types while the fees are low: P2PKH (legacy) weighs 148 vbytes to spend, P2SH-P2WPKH (wrapped segwit) weighs 91 vbytes, P2WPKH (native segwit v0) weighs 68 vbytes, and P2TR even only takes 57.5 vbytes.
For a private wallet, I’d say that you probably have too few UTXOs if you have fewer than ten, but you may have too many UTXOs if you have over 50 or 100. Those ballpark numbers of course depend on the overall amount of ’corn you stash. If you are more cost-conscious, you may want to aim lower, if you are more privacy-conscious, you may want to aim higher. If you have coins from different sources that you want to keep strictly separate (e.g. business funds and private funds), I find it more straight forward to have separate wallets than to keep them separate manually in one wallet.
Among other things, I contacted almost every pool I could find to pitch them on running full-rbf.
Good example of how Bitcoin really works actually: Core developers don't have any direct power. To make something change, users and miners have to be convinced to run new code and/or change configuration options. In some cases, not very many people have to be convinced: full-rbf just needs a few miners opting in to be useful. In other cases, pretty much everyone needs to be convinced: tail emission isn't going to happen without a hard fork and wide support.
Of course, I'm personally being sued by Craig Wright, who claims I among other people can give him coins that he claims are stolen (with zero hard evidence). It's a laughable lawsuit: can't even get full-rbf widely enabled without convincing a lot of people. 😂
I mute a lot of territories so that when I’m signed in, I only see the most relevant content. If I want to see cats and dogs, I just manually go to that territory.
I also view the site on mobile while not signed in so I can see everything.
Filtering by combined sats volume like ek mentioned is also a great default option.
A big issue was the fact that the source code was not public. It appears that is is now though: https://github.com/imperviousai
Would be good to know if the browser can actually be built from the repo, as it should ideally be..
EDIT: am in the process of following the build steps here, all good so far: https://gitpod.io/github.com/imperviousai/imp-browser
I can see now that it's based on Firefox, nice to have a new browser that isn't chromium based
https://m.stacker.news/16733
You've excluded all of my attempts to reason with you and explain things from the screenshot, but that's okay because the real message here is that you are not a user I am worried about losing.
You just wanted to complain and that is of limited usefulness to us. If you think you can do better, please do. I can only tolerate your noise for so long, and you found that limit.
Thank you for your testing feedback, and for your consideration, it will be considered appropriately.
Otherwise, I'd recommend some methods of stress relief, including, but not limited to, crying harder.
I'm wary of going the moderation route - it's too subjective. I like the market based system of SN. In the spirit of Bitcoin, spam can be prevented by increasing the cost to post with each successive post. The cost can rise exponentially or polynomially in the number of posts without upvotes. If a post gets upvoted, then it won't add to your posting cost because the post has added value.
I guess this is not entirely secure against sybil attacks because a user can create multiple accounts to upvote their own posts. I forgot if there was an account creation fee, but if there was then that'd be a solution
Let's build out the lightning network so it's ready for worldwide adoption! 🙌
Do you think any of these ideas could help counter this trend:
Let's suppose we took the current block size limit, 4mb, and decided that on January 1 we will reduce it to 2mb. Now, Grandma Gemma doesn't want to upgrade, so she keeps running an old node. On January 1, what happens?
Well, Grandma Gemma's node doesn't require blocks to be 4mb -- it will accept anything 4mb or less. Suddenly she starts seeing 2mb blocks. No big deal -- she accepts those too. That's why it's a soft fork, old nodes don't mind the new rules. But let's suppose some rogue miner decided to mine a 4mb block after January 1. What happens?
Well, most of the network rejects that block, because it violates the new rules, but Grandma Gemma accepts it. Chain fork, right? Not so fast: nodes follow the "most work." So unless the rogue miner has more hashrate than everyone else, the chain with "small blocks" will "outgrow" the chain with "large blocks" -- and as soon as Grandma Gemma's node sees a longer chain with more work, she will discard the "big block" and go with the longer/more-work chain.
That is why making the block size smaller is a soft fork: it doesn't cause a meaningful chain split as long as most miners are on board with it. It doesn't have to be all, just more than 51%.
I think it is a matter of perspective. People who don't understand Bitcoin think they are being aggressive owning it but people that understand it know they are being conservative and see it as savings.
Also, I hate that they use the word crypto.
Bringing the first non-custodial Lightning implementation to a hardware wallet companion app, the BitBoxApp.
The market is so very lopsided between the few gigs offered and the millions of people wanting to do gig / task work l.
That alone is a huge challenge for any gig work /task platform. Then add in how the few gigs are now spread out among a hundred gig / task work platforms.
https://cointastical.medium.com/freelancing-platforms-which-pay-in-bitcoin-e38be56166df
So I know what we need ... platform number one hundred and one!!!!
Great list. US dollar dominance enables abuses of the global south through debt slavery via the IMF. This kinda touches all 4.
Another one is censorship resistance. Bitcoin has already helped women escape abusive marrages in nations were women lack basic freedoms.
I built a small python app that I can run alongside my node and accept lightning address payments. It’s nothing new but gave me a chance to play with my node’s LND gRPC api. Note you still need to host a well-known text file somewhere 😃
https://github.com/calaniz/lnurl
3 is the magic number
https://www.inpowermovement.org/
https://onestupidfuck.com/
https://www.educatedinlaw.org/
Good. Should have it done this week. It's a huge pain.
The plan is to allow you to link/unlink a node (via lnurl-auth), twitter, github, or email to your account once you're logged in. So you can use multiple login methods and replace or remove any login method.
First of all you should ask yourself for what do you want to run that LN node.
There are many types of LN nodes and use cases.
Please start reading here, is very important to read these:
and many more that I wrote.
To be fair, it's normal procedure during bug reports to ask the user about the behavior they are seeing and what they want to see so we can confirm we understand your problem and can fix it.
A good bug report should include this:
Since you used "fix" here, we assumed you are talking about a bug and not about a feature request. Sorry for that misunderstanding.
Regarding the request: This was discussed during implementation but we went with user relays adding to the defaults for now, not overriding them.
I hope it's a “boat accident” 😵💫
https://imgprxy.stacker.news/rwNHaFlLuoiLrHXmSkjY3l711ikgZjnE2W59BVRGsJI/rs:fit:600:500:0/g:no/aHR0cHM6Ly9wYnMudHdpbWcuY29tL21lZGlhL0YxeXJXWDdXSUFBZ0s2ZD9mb3JtYXQ9anBnJm5hbWU9bGFyZ2U
Day 484 of snailposting everyday 'til BTC hits $100k.
...and day 48 of trimmin' the fat (93.1 | 80.0 | 4.5).
__@_'-'
Created a PR: https://github.com/stackernews/stacker.news/pull/235
This isn't dumb, the concerted efforts (by the NY times and co) to smear mining, and now this, is a concerted effort to stop bitcoin adoption in the us. This isn't a move from a senile man, this is a move likely backed and funded by banking and other interests
https://imgprxy.stacker.news/MYHYjOkNfAUrss0b8QcBxJ7PpQhK4TWcAZpLGOG808s/rs:fit:600:500:0/g:no/aHR0cHM6Ly9wYnMudHdpbWcuY29tL21lZGlhL0Y2MlJLbU1YTUFBc1FmZj9mb3JtYXQ9d2VicCZuYW1lPXNtYWxs
As others have said I hope for a gradual adoption of the masses coupled with steady improvement in the tools around bitcoin. I hope for increased privacy and simplicity of tools. Ideally privacy should be easier than it is today. I hope the average person has bitcoin and has self custody of it.
I fear we will see the US and the tradfi world "sanitize it" and people only use paper bitcoin. I fear that everyone that adopts it will be KYC'd and owned by the state.
I think we'll see games using bitcoin. Up and coming games that don't yet exist. Game where bitcoin makes sense. I think we will see more of what we are seeing now. Content creators using bitcoin to support their work. Peer to peer value for value.
This one is harder for me but honestly I think a big area is the idea that bitcoin will lead to an anarcho-capitalist utopia. I just don't see that. I do think we will see positive moves away from state power but that vision will probably take centuries if it every happens. I say this as someone sympathetic to that vision.
Others are that real estate is a waste of time as are stocks. I think both of these are highly pumped up by the fiat system but with a non-fiat currency they will return to their place of utility. We still need land. Rental property will continue to be a profitable endeavor as well publicly traded companies. It will just be different. Where I think they are right is that over the next 20 years bitcoin will outperform.
I have 112 referrals and this is because I didn't want to abuse it too much.
I used the invitation links only with specific people, after I tested a mass invitation and then stop it.
In this way you can "control" a bit who is coming to SN, not all unknown assmilking shitcoiners finding your link in the wild.
This option with invitation links I like it a lot,. especially that you can set exactly the amount.
Agreed. I use to invite others, not to be specifically my "referral" but to offer them a new way to communicate with other bitcoiners. I so not care too much about the sats I get from "my referrals", that is not so important. Important is that they bring new good content.
I need to find time for:
100 days of Python
Pleb Dev Courses
Nostr Dev Courses
Bitcoin is Venice
Praxeology
Way to scattered, now I'm attempting to write articles and seriously considering starting a podcast with my newly orange pilled wife.
And I should probably update my resume with chatgpt and find a bitcoin job......
Hit me up if you (or anyone else) wish to grab a beer. Nov-March is the best time.
https://image.nostr.build/6020d2f803209f8bfcbdd4b9bdd2c9b4f13fa826bf03644e55b170619437aa76.jpg
Making pictures about holding your own keys
https://bitcoinscoresby.com/wp-content/uploads/2022/12/Bitcoin-Vacation-Short.png
https://bitcoinscoresby.com/wp-content/uploads/2022/12/Bitcoin-Barbarian-Queen.jpg
I've got my lightning address going out and NWC going in so I think I'm ready for the diaper change.
Hello SN,
I'm using the daily discussion thread as an excuse to announce that tonight we'll have the first (afaik) BitDev in Paris, France.
What is a BitDev ? See https://bitdevs.org/about
Discussions will be in French, and the event will start at 6pm. If you're interested and in the area, feel free to come! More info on Telegram: https://t.me/BitdevsFR.
Cheers!
My assumption: There were a number of rigs that got powered down by around mid-May as they no longer remained profitable when the exchange rate collapsed. When it was apparent the price wasn't going to quickly rebound (i.e., in a bear market) there were then decommissioned, boxed, and sold to someone else who has a lower cost of electricity and are now being powered back on.
Similar sentiment stated in the mining section of this weekly newsletter:
Blockware Intelligence Newsletter: Week 53
https://stacker.news/items/65782
https://newsletter.blockwareintelligence.com/p/blockware-intelligence-newsletter-fba
https://nostr.build/i/nostr.build_1caeb444f28fa0ddf7b751f355755e0d1b8d427a52c520d44a9791d4bfbf7a77.png
You want to aim to strike a balance between having too few and too many UTXOs. If your wallet is too fragmented, your inputs may incur a lot of fees in the future. If you have too few UTXOs, you may reveal significantly more information to your counterparties about your stash. E.g. if you pay someone 1 m₿, but use a 1 ₿ input, they learn that you at least have a whole coin. On the other hand, if you want to pay someone 1 ₿ and need to combine ten or more UTXOs to fund the transaction, you may also tell your recipient and the people that sent to you a bunch about your wallet history.
I would avoid splitting everything into round amounts as you propose. Doing so would incur unnecessary additional transactions, the round amounts would be a fingerprint, and having multiple UTXOs of exactly the same amount is less versatile than having that sum composed from different amounts. That said, an exponential distribution seems like a good idea. If I were in your situation, I would take a look at my UTXO pool composition and decide which UTXOs you want to keep, and where you have gaps in the value distribution. Then I’d try to create transactions that each give me one or two UTXOs in those less densely populated value ranges. Be sure to spend UTXOs with inefficient script types while the fees are low: P2PKH (legacy) weighs 148 vbytes to spend, P2SH-P2WPKH (wrapped segwit) weighs 91 vbytes, P2WPKH (native segwit v0) weighs 68 vbytes, and P2TR even only takes 57.5 vbytes.
For a private wallet, I’d say that you probably have too few UTXOs if you have fewer than ten, but you may have too many UTXOs if you have over 50 or 100. Those ballpark numbers of course depend on the overall amount of ’corn you stash. If you are more cost-conscious, you may want to aim lower, if you are more privacy-conscious, you may want to aim higher. If you have coins from different sources that you want to keep strictly separate (e.g. business funds and private funds), I find it more straight forward to have separate wallets than to keep them separate manually in one wallet.
On public channels, routing fees and max/min htlc sizes can be used to steer payments in one or the other direction. This is very helpful.
Private channels on the other hand don't need that and can just have a static fee, maybe based on usage patterns.
Among other things, I contacted almost every pool I could find to pitch them on running full-rbf.
Good example of how Bitcoin really works actually: Core developers don't have any direct power. To make something change, users and miners have to be convinced to run new code and/or change configuration options. In some cases, not very many people have to be convinced: full-rbf just needs a few miners opting in to be useful. In other cases, pretty much everyone needs to be convinced: tail emission isn't going to happen without a hard fork and wide support.
https://petertodd.org/2023/why-you-should-run-mempoolfullrbf
Of course, I'm personally being sued by Craig Wright, who claims I among other people can give him coins that he claims are stolen (with zero hard evidence). It's a laughable lawsuit: can't even get full-rbf widely enabled without convincing a lot of people. 😂
Sorry guys, I'm kinda busy these days with some work, can't join too much on SN & Saloon.
But I try to keep my cowboy hat on.
https://the-wild-hustle.ghost.io/
Trying to get into blogging/meetups/faucet creation/node running/Random Stuff.
just a reminder
https://m.stacker.news/46442
What notification daemon are you using with i3? Also does this only apply to notifications from Chrome or other applications?
When do you think will be available some testing code for all this ark?