https://lightningrelay.com is live! A ⚡ paid relay for (6678 sats) one-time fee. Please add to your relays!

lightingrelay.com lightningrelay.com

Looks like someone is trying to scam the hype. "Bitcoin Name Service" says they can do on-chain .btc domains; Turns out they just did "satoshi.btc" as a text inscription on an ordinal and are calling it a day. They didn't even bother writing a real protocol description. The funny thing though is that if they actually pivot from being a SCAM to being legit, they could actually make the on-chain attestation work. My proposed protocol below:

  1. The earliest block height in which an ordinal was inscribed with the unique registration is the "beginning" of the registration; 1.a. If there are more than one inscriptions within the same block, the one with the lowest ordinal wins (or swap out some other reasonable & repeatable methodology here)
  2. The "registration" expires after N number of blocks... let's say a year worth: 52560. 2.a. If the wallet owning the "valid" ordinal posts another registration w/in the expiry period, the registration is renewed for another 52560. 2.b. If the registration expiry period passes, any other wallet can post a new registration on the block after expiration.

TADA. A "me first", "expiring", "renewing", "released" system for unique string inscriptions. You would only need a tool that could scan the blockchain for that data and provide results via an API. It would have to be open source and hosted by many. There'd be no middle-man grifter to take a cut either (the protocol could require a "valid registration" to send some to a known address, but unless it was of community benefit, no one would support it)

Either way, .btc domains already exist on stacks, but this protocol I've proposed here could be used for something else with expiring first claim issuance. Anyone have any good ideas on things to register in this manner?

synace ✅ shared 1 year, 4 months ago

https://battledrome.io still moving ahead, bit by bit. Excellent and steadfast commitment by @theglasswalker@twitter.com

Update on upcoming UI Release by https://medium.com/@BattleDrome/update-on-upcoming-ui-release-d748675cb2d0

synace ✅ shared 1 year, 5 months ago
synace ✅ shared 1 year, 5 months ago
synace ✅ shared 1 year, 5 months ago

in reply to this object

@kevinpurdy@indieweb.social Home Assistant is a great self-hosted project. I've been running it on my for over 7 years now. I think I switched from OpenHAB once Z-Wave became supported on Home Assistant. I'm glad to see dollars funneling in to shepherd other open source projects. The last time I looked, mycroft was leading the pack but was too CPU intensive for my needs. It'll be exciting in a few years, when combined with lessons learned from ChatGPT, once there's some contextual accuracy improvements, there will be a emergent leap in capability.

in reply to this object

I forgot!

Anigma anigma.io

Which clients are folks using? I've tried a bunch. Functionally speaking:

  • astral.ninja pretty functional, but don't try to load global
  • nostr_console for the most complete functionality, e.g. editing profile
  • damus.io/web but it's been turned off for now because of a private key issue
  • nostr.ch for lurking the global feed

damus is available for iOS and seems to be the one most prefer. I'm hoping the web version sees more progress.

in reply to this object

@t@hexa.ninja Gotcha. My concern was that when my notes show up on other instances, they wouldn't be clickable/linked if I just used the username portion. Obviously, there'd be an issue with the current implementation of just parsing the username from the raw post content, and it'd require context to know which user to link to, (in the case of duplicates for example). So, some markdown style syntax sugar would be needed, e.g. something like:

  [@t](@t@hexa.ninja)

~Cheers

▶️

Have you ever had a dream that that you um you had you'd you would you could you'd do you wi you wants you you could do so you you'd do you could you you want you want him to do you so much you could do anything?

  • 🤣 0% (0 votes)

  • 😂 0% (0 votes)

  • 😆 0% (0 votes)

  • 🧒 0% (0 votes)

in reply to this object

@t@hexa.ninja Has anyone put in a ticket to support @t in the replys to a current thread. Or, even on a new post with a particular markdown format, unless that's already a thing? It's feeling pretty comfortable here now. Thanks for the software!

synace ✅ shared 1 year, 5 months ago

in reply to this object

@s@u.sdj.au @dev@microblog.pub Could you contribute to microblog.pub?

in reply to this object

@aspleenic@hachyderm.io fixing my at mentions... again lol 👷

in reply to this object

aspleenic@hachyderm.io 1995? pumpkins; björk; presidents of the united states of america 😂

in reply to this object

@t@hexa.ninja looks like the "@" was already added upstream, reverted on my branch now. thanks!😄

@@t@hexa.ninja I put my personal changes on a branch if you want to check them out. https://github.com/synace/microblog.pub/tree/synace

🍻👍

in reply to this object

@aspleenic@hachyderm.io my client is currently not context-aware enough to properly link your handle without the domain (e .g. @aslpeenic ) even though it's in the reply to yours. gonna put in a pr probably.👷