Avatar
teatwo
3589b793b977c4f025175afd792e7c51d26ef683b45cbc66c56c4d14ad53847e
teatwo is derived from "T2". Author: https://api-docs-30b126.gitlab.io

what happens if changing default app? let's try it

it's still the 6th of this month, but I'm so glued to the US presidential election (and the outcome of WW3...) that the loading amounts is heavy.

I'm not sure if it's effective, but i switched the X app to PWA. I hope Nostr alone will be enough ☝️

IDEAL

- ONE npub with TWO nsec

- As usual by "1 of 2", you sign with one nsec

- another nsec is for recovery, in case you need to revoke the usual nesc

- replace the revoked key to new key keeping1 of 2

- you will sign with new one nec and others keep to verify with the same npub

So you get the key rotation without monitoring revoke list.

The most difficult-to-acquire languages for American recognized by the U.S. Department of State.

Is it the same in the opposite vector? (i think so)

"of" is same for me😉 - "the village of hida"

furthermore, the case of "hida no sato" adds a taste of antiquity and tradition.

今回はこれで良しとしますが次はXのアカウント消させますからね!!

小生のリプにザップしてもらってもいいですか?

It's like creating a public key with multiple private keys, like multisig creates an single address by multiple pubkey, or Shamir creates a single seckey from multiple shares.

I am still studying this, but since it depends on schnorr signature, I think it will be difficult with the current nostr key (though proto NIP-95 exists already). it will have to start from a new key, won't it?

Replying to Avatar calvadev⚡️

nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck, I'm working on finalizing the Amber integration for nostr:nprofile1qqs2xugc5jyguqkj36rk0syv4tmnkjdtmtperttl7x9rqjy3ustdcvcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg6waehxw309aek2mnyd96zumn0wdnxcctjv5hxxmmd9uxa0uz8, with the last thing needed being the decryption methods (NIP-04 and NIP-44). For the life of me, I can't seem to get them to work. I've put in the encrypted text with and without the iv value and the hex pubkey of the sender and receiver; regardless of the combination of those that I use, it always comes back with "Could not decrypt the message". Do you have any idea of what I could be doing wrong? The messages are properly encrypted, sent, and decryptable on other clients, btw.

#asknostr #dev

> the hex pubkey of the sender and receiver

I guess that sender is OK but receiver should be their privatekey, right?

refs: https://github.com/nostr-dev-kit/ndk/blob/d2c323cbb3563d8ccb7e9cd8ff658473362efeb1/ndk/src/signers/private-key/index.ts#L137

🌊⛏️ I had the awesome chance to visit a 50KW Bitcoin mining site in Gunma, Japan, operated by Agile Energy X, a subsidiary of TEPCO Power Grid. Big thanks to the team at nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze who I tagged along with!

The site is operated by TEPCO Renewable & Power utilising 50KW of solar that would otherwise be wasted as the site is currently awaiting grid upgrade and connection.

I think this is a big step forward for broader engagement with power generators about how Bitcoin can help the grid and for understanding the opportunity to participate in this new monetary network.

There is a lot that we can learn from the power of Bitcoin mining to act as both a load balancing and grid stabilisation tool, as well as helping with the ROI and financial planning of new generation assets.

Is the first photo of the machines inside the small prefabricated hut in the second photo?

なるほどです。セルフっぽいLNアドレスセットしてインボイスを引けない人にちょいちょい遭遇するんですがそれぞれ別の原因なのかなー