pull down to refresh
19.1k sats \ 5 replies \ @anita 30 Aug 2023 \ on: Anita Posch Satsraiser bitcoin
Oh @Siggy47! Absolutely blown away by this text about my work. The best description anyone has written! Thank you so much for all you do!
Kids have been working on this all week. Last week's fact was from my 13 year old but this week we are stepping it up. Today's fact is from my 5 year old, which she learned from her abcmouse lessons.
Kiwi birds are the only bird with nostrils at the end of its beak.
Homeschool your kids folks!
-
I think a regular call would be good, to share things like major updates, road map, upcoming events, etc. I know a lot of this gets posted in ~meta, but a live forum could be nice, too.
-
I feel the directon of SN is very much community-driven. There are many feature requests posted in ~meta, and in general discussed in comments all over the site. While directing developers to GitHub to log feature requests or bug reports works well, I don't think a stacker should have to have a GitHub account to make suggestions or offer feedback. That being said, I think a first-class mechanism within SN to submit feature requests, bug reports, and vote on them as a stacker seems like a good idea. This would allow the community to express their opinion on what they'd most like to see, without having to leave SN.
-
I think @k00b has already started doing this, but just setting expectations around PR feedback is good. It could take a while for a small team such as SN's to review PRs, so just ensuring contributors are aware is helpful.
-
A prioritized backlog of items for contributors to pull from would be nice. I don't think that should limit what contributors can work on, but it might help contributors find something meaningful to work on.
-
Related to (4) above, if the backlog could also be annotated with things like
Good First Issueto help onboard new contributors, that would also be good I think.
I'll add more comments if I think of anything else
I'm very excited about the launch of this paper which is part of a project Robin and I have been working on together. Today I hope to launch a demonstration that you can use bitcoin to compute a 64 bit division function.
Forwarding the announcement post from our discord:
Satlantis Community,
First of all I want to thank you all for playing and supporting Satlantis for nearly a year now.
Mojang, the developers of Minecraft, have contacted us stating that we must remove the play-to-earn functionality from the server.
What does this mean for the future of Satlantis?
This sucks. There’s no getting around that. But,
SATLANTIS WILL LIVE ON
“The Game That Shares its Profits with Players” works. And it works well. All of the time, money, and energy that we put into this game together will not be forsaken by a few dinosaurs at some conglomerate. We will be porting the Satlantis community to a platform that encourages innovation, instead of stifling it. We are currently exploring platform options and I will keep you all updated in regards to that.
What does this mean for you, the player?
We will continue to do right by the players that make this all possible. All of your sats in-game will be honored. Please submit your withdrawals and I will work through the weekend to ensure they are processed. All of your ASICs will be ported to the new platform, as well the prize pool, your premium battlepass status and all other progress and data that is possible to transfer.
The minecraft server itself will continue running(without any pay-to-earn functionality) for the foreseeable future. This is to ensure the transition to our next game platform is as smooth as possible and allow you all to continue enjoying the great world you’ve built.
Stay tuned to our discord for further updates.
25 minutes of interacting in SN
- spent: ~160 sats
- stacked: ~1650 sats
- replies: 10
25 minutes of interacting in Nostr
- spent: ~160 sats
- stacked: 0 sats
- replies: 2
Base layer payments are self-custody. You alone have the private key. It uses my whisper addresses protocol to automatically derive infinite bitcoin keys from a single nostr private key, that way every time you receive a payment, it shows up in a different bitcoin address, but you can still recover it all.
Lightning payments are custodial by default. It automatically sets you up with a custodial lnbits account when you first load the page, which lowers the barrier to entry for people to get started. Also, I don't run the lnbits instance (Ben Arc's company does), so I am not responsible for having custody of anyone's funds.
I plan to make it easy to point it at your own node, but I need to write some software for that. Still, there is a way to do it right now if you're okay with a but of coding in the browser.
Here are instructions to point it at your own node:
- type console.log( localStorage[ "wallet_info" ] ) into your browser console
- it will show you your lnbits info
- change that info so that it shows info hosted on your own node (or e.g. a voltage node)
- then type in localStorage[ "wallet_info" ] = your_modified_lnbits_info
- then resubmit your store
If you do all that, all the sats you earn on lightning will flow to your own node. (But be aware! If your lnbits instance is hosted as a hidden onion service, as most of them are, people won't be able to send you funds on lightning unless they happen to be using a tor compatible web browser.)
10.8k sats \ 3 replies \ @ssuutxanu 20 May 2023 freebie \ parent \ on: Why was stacker.news DDOS'd? bitcoin
DDoSer on the phone.
Yes, you're absolutely right - it was done for fun. I'm testing a new method for DDoSing Amazon targeted servers, and stacker.news is the right place for such testing.
I apologize if I did any harm :c
I read stacker.news regularly myself and like lightning news
Top 21 domains shared on SN
includes links shared as posts and in text
Total links: 118,404
| Rank | Domain | Total | Percentage |
|---|---|---|---|
| 0 | twitter.com | 12,051 | 10.18 |
| 1 | www.youtube.com | 10,760 | 9.09 |
| 2 | youtu.be | 6,937 | 5.86 |
| 3 | news.ycombinator.com | 4,815 | 4.07 |
| 4 | stacker.news | 4,651 | 3.93 |
| 6 | github.com | 3,658 | 3.09 |
| 7 | bitcoinmagazine.com | 2,350 | 1.98 |
| 8 | i.postimg.cc | 2,279 | 1.92 |
| 9 | postimg.cc | 1,938 | 1.64 |
| 10 | i.imgur.com | 1,557 | 1.31 |
| 11 | archive.ph | 1,453 | 1.23 |
| 12 | www.coindesk.com | 1,209 | 1.02 |
| 14 | cointelegraph.com | 984 | 0.83 |
| 15 | nitter.it | 957 | 0.81 |
| 16 | www.nobsbitcoin.com | 929 | 0.78 |
| 19 | www.zerohedge.com | 848 | 0.72 |
| 20 | fountain.fm | 809 | 0.68 |
| 21 | bitcointv.com | 738 | 0.62 |
Top 21 image hosts used on SN
Total image links: 7,431
| Rank | Domain | Total | Percentage |
|---|---|---|---|
| 0 | i.postimg.cc | 2,266 | 30.49 |
| 1 | pbs.twimg.com | 560 | 7.54 |
| 2 | i.ibb.co | 331 | 4.45 |
| 3 | nostr.build | 292 | 3.93 |
| 4 | www.zapread.com | 263 | 3.54 |
| 5 | cdn.nostr.build | 248 | 3.34 |
| 6 | i.imgflip.com | 169 | 2.27 |
| 7 | nitter.at | 135 | 1.82 |
| 8 | imagedelivery.net | 103 | 1.39 |
| 9 | media.tenor.com | 91 | 1.22 |
| 10 | bitcoinscoresby.com | 78 | 1.05 |
| 11 | upload.wikimedia.org | 76 | 1.02 |
| 12 | image.nostr.build | 69 | 0.93 |
| 13 | i.redd.it | 58 | 0.78 |
| 14 | files.peakd.com | 54 | 0.73 |
| 15 | preview.redd.it | 53 | 0.71 |
| 16 | void.cat | 45 | 0.61 |
| 17 | gcdnb.pbrd.co | 43 | 0.58 |
| 18 | www.ft.com | 41 | 0.55 |
| 19 | substackcdn.com | 35 | 0.47 |
| 20 | i.kym-cdn.com | 34 | 0.46 |
| 21 | imgproxy.iris.to | 32 | 0.43 |
I thought this was a good insight into how bitcoin core nodes find peers on the network (using a hardcoded list of seed nodes)
Not quite correct: that's the first method they try. But if that fails, there is a backup list of IP addresses that are tried too. Also, for Tor only nodes, IIRC there's some fixed
.onion addresses that are tried too. I2P probably has something similar.If you run a node with
-connect, the seed nodes and other mechanisms aren't used. Similarly, if you use -addnode, provided your node works and returns addresses, the seed nodes aren't that relevant either.Assuming your ISP isn't themselves MITM attacking you, you only need a single "honest" peer for Bitcoin to properly connect to the P2P network. So the seed node mechanism has a lot of redundancy.