I agree. The “lightning is early” and other claims are all DOA now. It’s just greed.
What I like most about lightning is that’s is almost the exact opposite to Bitcoin. Which is why I think it’s such a good pairing.
It’s beyond lazy for exchanges not to support Lightning today. Literally no excuses.
Making your money hard to access is no different to the tactics of banks. These types of businesses won’t last.
I’m tired of chatGPT’s apologies.. and the endless overconfidence. Did they ask it to behave like the little boy who cried wolf?
It’s basically just a fancy auto-completion at this point.
Musk can just bore some more tunnels and travel underground freely. It’s the future.
How take-down resistant do we think domain names are?
I’m experimenting with a Nostr service that can allow you to use your own custom domain. Benefits include your Nostr events referencing a domain you control, so images or content references don’t break if you change to a new provider - or if you decide to self host.
It can also be an auth proxy to validate access or membership to that content.
Invoices can be wrapped for privacy and be atomic - so the provider and the creator get paid at the same time.
I like the Nostr torrent media idea, however content behind private membership or a paywall doesn’t really fit that approach.
GM buidl town ☀️ 🫖
Found this absolute gem in the process though:
"Nostr’s origins are mysterious. The name does not appear in the U.S. trademark database. According to WhoIs, the Nostr.com domain was originally registered in 2003 (almost certainly for some other entity) and brought back to life on November 29, 2022, by a person or persons whose names are shrouded. The service’s founder is known only by a pseudonym, “fiatjaf.”"
https://nancyfriedman.typepad.com/away_with_words/2023/05/new-name-beat-nostr.html
Technically I think BenArc bought/owns the Nostr.com domain.
Yeah. I’ve just seen some really stupid terms in the past around some former translation services saying you cannot cache results or whatever. Unsure how legit it is - impossible to really enforce anyway.
Literally anything that’s user facing needs caching today as it scales to have decent UX anyway.
Can translations be cached on your provider end, or are their terms of service issues?
Obviously multiple language pairs per event, however I’d expect that it’s biased to a few major pairs.
Bitcoiners causing airway traffic with all their helicopters
Under a ‘Moderated’ Nostr would this be flagged/labelled “Political Protest”? Would you even see this? Or only what people in power want you to see?
Seems like fair concerns from the people?
"Another thing is that they are making us suffer economically, energy is too expensive and so is food," she said.
Protesters at the "Czechia Against Poverty" rally called by the small non-parliamentary PRO party also slammed Fiala's cabinet for soaring public deficits and for poor communication with voters. nostr:note1s6ag3xh52nknrc4t695fgwxrwvlyrh74u8jylsq6mzvd4u3hx82sgh8tj8
#[0] have you seen this? https://github.com/lnbits/scrub
Just pushed a PR for lnproxy that enables support for a service provider to add a fee to an atomic invoice where both the service provider and a content creator can get paid upon successful payment/settlement.
Effectively this is like a split payment, where the service provider can add a dynamic fee on top of a seller price, that can cover hosting, or whatever costs the service provider has.
I added this as an API for hashtags and words. It’s based on past 24 hours unique events across 100+ relays. Updated a couple times an hour atm.
https://api.nostrgraph.net/beta/trending/hashtags.json?pretty=true
https://api.nostrgraph.net/beta/trending/words.json?pretty=true
That’s because chatGPT doesn’t have data older than two years.
gptSKY doesn’t code itself you know.
Same. The app doesn’t like zapping from a cold WOS start.
There is a common pattern that’s not well defined yet in Nostr that is effectively a cached result. It’s stateful and typically either expires by time, or expires when replaced.
An example could be how much credit you have used for a paid service. Goes up and down on payment and usage.
Another example is a list of current trending events or similar, updated hourly or daily.
One consideration is how and when to update. Schedule is ok, however a client bump to update their usage to be current is likely a valid case too.
It’s basically a snapshot of data that’s useful as an event and more (likely) accurate the closer to its creation time, however it’s content changes.