Now I get it, the Dutch translation is really bad lol

After filling a nsec, its returning forbid alerts

But for using a PWA this is not a convenient solution

Thx for the heads up with Nowser tho 🤙🏻

By the way, it's unfortunate, but phpBB UI would not work on a phone, and in fact we need a native phone app that is able to browse these NIP-29 forums. Can 0xchat do that? I don't know, but we need more apps. I know Flotilla and Chachi can be used on a phone, but if you used a cheap old phone like me you would know that isn't a good idea.

北美也上映了《哪吒2》，今天兴高采烈的带着5岁娃去电影院。但娃处于中文原声听不懂，英文字幕看不懂的尴尬境地。还好视觉特效拉满，娃还是认真看完全程，今年暑假继续带回国补中文。

Giftwrapped notes to selected people

看了场老人音樂會，歌手75，觀眾老頭老太居多。串場聊的是死亡啦，人生啦，也是蠻有趣的。

搞不懂了哈哈😂，我觉得是公钥格式的问题。 本地验证是用直接生成的full public key验证的所以结果是valid。传到relay的pubkey是hex格式公钥，好像是full key的32字节x坐标而已。 不知道是不是这么复杂

print(type(json_hash)到结果是class ‘bytes’.

是不是要字符串str才是正确的？

I can generate the correct event_id, but always get bad signature. Any wrong with my sign?

from ecdsa import SigningKey, VerifyingKey, SECP256k1

# create event id

event_id = json_hash.hex()

print("event id:", event_id)

print("evnt id length:", len(event_id))

# signature the json_hash

signature = sk.sign(json_hash)

#convert to hex

sig_hex = signature.hex()

print("sig:", sig_hex)

print("sig length:", len(sig_hex))

import json

import hashlib

import hmac

import time

import random

import websocket

import chardet

import logging

# 设置日志级别和格式

logging.basicConfig(level=logging.INFO, format='%(asctime)s [%(levelname)s] %(message)s')

# Nostr公钥

nostr_pubkey = ""

# Nostr私钥

nostr_privkey = ""

# JLPT N1文法列表

n1_grammar = [

"こんにちは",

"美味しい",

"おはよう御座います",

"サヨナラ",

# 添加更多JLPT N1文法...

]

# 事件标签

tags = []

# 事件类型

kind = 1

# Nostr Relay网址列表

relays = [

"wss://relay.damus.io",

"wss://nos.lol",

"wss://nostr.mom",

"wss://relay.coinos.io/",

"wss://offchain.pub/"

]

def send_nostr_message():

try:

# 选择随机的JLPT N1文法

content = random.choice(n1_grammar)

# 生成事件创建时间

created_at = int(time.time())

# 生成事件数据

event_data = [

0,

nostr_pubkey,

created_at,

kind,

tags,

content

]

# 序列化事件数据

event_json = json.dumps(event_data, separators=(',', ':'))

# 计算事件ID

event_id = hashlib.sha256(event_json.encode('utf-8')).hexdigest()

# 计算事件签名

event_sig = hmac.new(nostr_privkey.encode(), event_json.encode('utf-8'), hashlib.sha256).hexdigest()

# 生成Nostr事件

event = {

"id": event_id,

"pubkey": nostr_pubkey,

"created_at": created_at,

"kind": kind,

"tags": tags,

"content": content,

"sig": event_sig

}

# 以JSON格式显示发送的内容

logging.info("发送的内容：")

logging.info(json.dumps(event, indent=4, ensure_ascii=False))

# 发送事件到多个Relays

for relay in relays:

try:

ws = websocket.create_connection(relay)

logging.info(f"成功连接到 {relay}")

ws.send(json.dumps(event))

logging.info(f"成功发送事件到 {relay}")

ws.close()

except websocket.WebSocketException as e:

logging.error(f"连接到 {relay} 失败：{e}")

except Exception as e:

logging.error(f"发送事件失败：{e}")

# 每小时运行一次send_nostr_message函数

while True:

try:

send_nostr_message()

time.sleep(3600)

except KeyboardInterrupt:

logging.info("程序终止")

break

except Exception as e:

logging.error(f"程序运行失败：{e}")

Nice 🍀 Thank you for de Feedback 💪

Hi Dashu, great work! Are there any instruction how to use the nip46 bunker on iOS? Couldn't find it.

嚴格說比特幣挖礦的耗電是最有效率的

因為它是每塊晶片整塊晶片做同步的同樣種計算，散熱也相對於容易設計。比特幣挖礦工作內容永遠一樣

AI不一定，記憶體的供電需求跟處理器不一樣，而且工作內容沒辦法同步因為它是不斷的流動，整台不一定同時啟動。散熱設計比較難

在同樣的體積的比較，比特幣挖礦會用比較多電🧐