Imagine #Blobbi, but as an open-source #pokemon / #digimon powered by #Nostr.
I'd consider Cashu and Ark on a separate layer.
They utilize the Lightning protocol for inter-node transactions, but they're able to function independently of Lightning as a network for their in-node transactions using their own "currency", for lack of a better term.
Trying out the #Blobbi project.
What a fantastic idea. This could really spring into something.
The nostalgia of Tamagochis, the openness and versatility of Nostr as a protocol, and a coating of modern paint, there's some serious potential in this.
Vanish.
Community picks up.
Hope for the best.
Prevails over what?
What's... Competing?
I see a lot of people moving off (or wanting to) #Plex due to their recent changes.
If you're in the same boat but don't feel like setting everything up, I'm offering a modest #Jellyfin #Share if anyone is interested.
- Requests Portal
- Automated content additions
- 1 week trial
- Includes other services (single login via SSO) under a single-cost
- #Matrix Server (can create your own community+calls etc a la #Discord)
- More to come
This is a service I've offered for over a year at this point.
DM for details.
FYI, failed to get zap invoice when trying to zap you.
I updated https://p2p.band to connect with web extensions. So I guess it's a new nostr client now.
You cab create your own order right on nostr and sign them with your web extension, I hope clients start implementing at least visualization if them.
The coolest part: you can filter orders by your WoT so you can directly contact your frens to exchange internet magic money
There seem to be some lnp2pbot BUY type orders that point to Spanish sell orders.
Just FYI.
I could see it being an interpretation mistake "BUY -> EUR", Am I buying bitcoin, or Eur?
I wonder if the filters would be improved with operator words like
BUY
FROM ( network/orderbook)
FOR (currency)
Looking real good!
Assuming no one moves..
Maybe D, definitely* C, potentially E.
* Also assuming the stone/boulder doesn't get stuck in D's position.
Forgot to mention, settings - Click "Manage" 5 times to unlock dev tools(this is so it swaps out for Core automagically), then hit reinstall. That's it.
If interested I can get you IPTV.
DM me if interested.
Sats only :D
The effect in the sky of an explosion out in space from some time ago, turned into a verb for participation.
If you want to run a node that has clear defaults in terms of what it stores, with little control or say on the matter, run #Bitcoin #Core.
If you want full control over to remain flexible over what transactions are stored, run #Bitcon #Knots.
Simple.
Core closing up discussion on the matter and banning people is the real issue here in my opinion. But at the end of the day, that's what forks are for.
To all #Start9 node runners out there,
if you're aware of what's going on with Bitcoin #Core, but think you need to resync the entire #timechain again - you do NOT.
Just switch to Bitcoin #Knots (click "Reinstall")!
It'll swap out Core for Knots and give you back the control you had previously and and your indexer (electrs, etc) will simply reindex blocks - I did this on a running node, with Lightning active, no issues.
If you get an "not successful" message, don't fret - You'll see it installed anyway and all is working, the message is mainly a cosmetic issue.
The question was clearly phrased in a way to cater those who are already aware of the situation.
I have no issue explaining the situation, if politely asked to.
If by 'can of worms' you mean exactly what is happening with Bitcoin Core, I can't disagree, but let's simplify - Open-source development happening behind closed doors is not open-source as far as the general ethos goes.
Especially when valid concerns are brought up only for the people who bring up those concerns to get banned from the discussion. You can agree or disagree.
Running an older release is an option, but eventually won't be sustainable if you want to use newer features.
Finally, I'm not looking so much to dwell on the happenings because that's already being discussed to length on multiple fronts, but making it known that alternatives exist and that Core (the big 'default' up to this point) is not the only option, because thinking it is, is the bigger issue in my view.
I don't want to give browser extensions my private key :(
Disagree with the BS happening over at #Bitcoin #Core?
That's fine. Make it known by running a different fork of the software on your #node.
The quicker people understand THEY have the power, the quicker we move on from this, stronger.
If you're looking for an alternative, Bitcoin #Knots is the biggest contender.
All the drama in Bitcoin Core debates gives more credence to Saylor’s position that we need to “ossify.”
“BUT WALKER, SOFTWARE NEEDS UPGRADES!!” >> yeah, no shit, listen to nostr:npub10qrssqjsydd38j8mv7h27dq0ynpns3djgu88mhr7cr2qcqrgyezspkxqj8 , that’s not what I’m talking about… nor am I endorsing a position of “ossification” because ossification is not a decision, it is a natural and inevitabile process.
Literally all am saying is that the current Bitcoin core debates make Saylor’s points for him.
Not necessarily.
Bitcoin is open-source.
This is a walk-in-the-park, day-to-day for open-source.
Projects make decisions that many users and maintainers dislike - So they fork.
This is NOT an issue, unless you're running the software fork you DISAGREE with.