Avatar
fmar
30782a8323b7c98b172c5a2af7206bb8283c655be6ddce11133611a03d5f1177
I like freedom and to build stuff Building dart NDK Devops at nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm #bitcoin #nostr #hanggliding #sailing #batucada #diy #powerwall

no, listr.lol

Replying to Avatar iefan 🕊️

You can create a list using https://listr.lol/

Login, create the list & come back to your Amethyst client click on "All Follow", it will show you all your newly created list.

Why doesn't it use my relays from nip-65?

Replying to Avatar Gigi

GN

After hours of fiat mining and then taking care and playing with my kid, I'm grateful to still find a bit of time to work on such fullfiling freedom tech that is #nostr, GN. #gratefulchain

nostr:nevent1qqs8cldg4sk5h9v94gkpnjw4cj0u890nx0hqtnkz935gs58uklkk9dqpzemhxue69uhkummnw3ezuenfd3khwetz9ecxcq3qdergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsxpqqqqqqzkgd7uv

How do you find out from either 9734 or 9735 events who sent the zap? I have a tag anon on the 9734 event starting with pzap1... Amethyst is showing me on the notifications the real sender of the zap, so I assume there is a way to somehow extract the sender from this anon pzap1... do you guys know how to do that? nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

When something you're building is so nice to use that you spend hours using it instead of coding new features...

Replying to Avatar jimmysong

The False Dichotomy: Soft Forks vs. Innovation

----------------------------------------------

A common argument in the altcoin community is that Bitcoin isn't innovating, especially compared to newer, "advanced" altcoins. I've debunked this fiat argument in the past, as it equates bribed rent-seekers with entrepreneurs under the label of "developers." These arguments come from non-technical midwits that spew altcoin propaganda and have no interest in providing value.

Unfortunately, this argument has a particularly obnoxious form within Bitcoin where the so-called "moderates" argue that Bitcoin needs to implement more soft forks to continue innovating or progressing or gaining adoption. This argument is flawed for several reasons.

First, it's incorrect to say Bitcoin isn't innovating. Numerous developers are continually working on Bitcoin, not just in Core, but in the many projects building on top of it. Innovation doesn't just mean changes at the protocol level; it also happens in second layers. Innovation is happening in a permissionlessly.

Second, equating soft forks with innovation is not understanding the long-term consequences. Soft forks are permanent changes to the protocol, and implementing them doesn't necessarily make Bitcoin more innovative or better. In fact, rushing to add new features can introduce security vulnerabilities, a problem often seen in many altcoins. Worse, if the soft fork is a complete dud, we're stuck with it. Reversing a soft fork requires a hard fork. We're essentially stuck with these soft-fork changes forever so we'd better be careful about the changes we let in.

Third, there's a misconception that a lack of soft forks indicates stagnation. This view ignores Bitcoin's biggest strength: its decentralization. Because Bitcoin is not controlled by a single entity, it doesn't have a traditional roadmap or deadlines. This decentralization enables a more organic and safer form of innovation, primarily occurring in layers above the Bitcoin protocol.

Innovation in Bitcoin is not solely defined by the number or frequency of soft forks. The argument that Bitcoin is lagging because it isn't continually implementing soft forks misrepresents how genuine, sustainable innovation occurs. Such misunderstandings comes from a fiat, centralized mindset and the less credence we give to this assumption, the better off we'll be.

There are AppImage and deb packages but the chance libs needed are installed in your system is a bit of luck for now. I will work on that to ensure all libs needed are included in the next versions releases. Thanks for testing

My main issue is you're dependent on google centralized cloud service for a good UX of getting notifications when something happens interesting to you.

In the spirit of decentralized freedom tech which I believe nostr is, the natural path for having that nice UX feature should be to do it also in a decentralized, third-party risk free, uncensorable way.

Should not have to be too expensive to keep a socket to a few relays in the device open, or just pull then periodically.

For sure google push services also does this somewhere/somehow for connection with fcm cloud, just lower level taking advantage of privileged access to the system.

That should be a choice for the end user, not a forced dictated imposed thing.

Replying to Avatar Pitufo

Share Your Location Live PRIVATELY

https://github.com/Myzel394/locus

Locus is a free, open source app for Android and iOS that allows you to share your location live. It encrypts your location end-to-end, meaning that no one, not even we, can read it. It stores the location decentralized on multiple servers of your choice using Nostr, meaning that you are not locked to a service. No authentication required.

And does it work in the background even after you kill the foreground app?

Replying to Avatar Pitufo

Share Your Location Live PRIVATELY

https://github.com/Myzel394/locus

Locus is a free, open source app for Android and iOS that allows you to share your location live. It encrypts your location end-to-end, meaning that no one, not even we, can read it. It stores the location decentralized on multiple servers of your choice using Nostr, meaning that you are not locked to a service. No authentication required.

Why the warning?

Have a good flight. And if possible join our #nostr meetup on monday in warsaw.