4,918 sats stacked
stacking since: #7290
Yes, merchants in the US pay a fee to payment processors. I think it can range from 1-5%. It's transparent to the consumer, though.
Interesting that you mentioned a surcharge on card payments. In the US we have the opposite. Cards have cash back programs that give basically a floor of 1% back on every purchase. Depending on the card you have, it can be a lot more. Now we have the Fold card that gives cash back in Bitcoin. As you can imagine, it heavily incentivizes everyone to use a card for everything. Unless these programs go away, I have a hard time seeing cash getting a lot of use in the US.
This is great. It's almost exactly what I had envisioned in this post.
This has a lot of promise. I’m not sure how I feel about them building in a native messaging layer though. Do we really need that?
I finally got it working through my Umbrella node. There doesn’t seem to be a lot of activity. I kind of get the concept (pay sats to send messages), but so far everybody seems content of Telegram.
Definitely. Unfortunately everything I can think of is already owned. Maybe someone in the community has a good one they can donate?
Of course. Lightning would be a first class citizen on a site like this.
It looks like someone started to do this but has abandoned it.
Is it online? Do you mind sharing the address?
Baseball cards from my childhood. I plan on selling them soon.
Old issues of Electronic Gaming Monthly. I also intend to sell them. I recently sold all of my Nintendo Power issues.
I used to own a ton of CDs and DVDs. It felt great to sell them all.
I just reread this. I have no idea where “I’m daft” came from.
The code itself is perfectly safe. With the way Git works, everyone that has pulled down the latest code has a copy of the entire history of the codebase. If GitHub decided to delete the public repo, it would be trivial for one of the maintainers to push it to a different host.
What’s more concerning are the issues, pull requests, discussions, etc. But GitHub has a really robust API that could be used to write an export tool. I’m daft, there are already some in existence. This seems like a good starting point: https://github.com/topics/github-issues-export
I gave that a try and couldn’t take much. No wonder the tech industry is a clown show of one JavaScript framework after another. It’s filled with people who think they know everything.
How did you come up with the name? Was it obvious to you from the start? Or did you have other ideas?
Amazing work @k00b. This kind of community software could change online communication in a profound way. Have you considered generalizing the source code so that any community can easily spin up their own instance? (I haven’t looked at the code to see how easy this would be.) Imagine niche communities like knitting and bird watching slinging sats back and forth!
Don't feel bad. I recently worked on a website that would retrieve data exclusively from Redis. The problem was, whoever wrote the thought that Redis calls were free. It would make thousands of Redis calls in a single request... for the same data.