サイゼリヤに貢献しにきてる。つまり食べている
僕のハックは、わかめサラダと小エビのカクテル頼んで、わかめサラダのトッピングにしてる
takuya(iqbqioza)
_@iqbqioza.com
npub1taku...qwf4
I'm a frontend and backend developer based in Niigata, Japan. I built nostrfy, an engine for running Nostr relays. The internet is for everyone, not big tech.
I built a software:
nostrfy
https://github.com/iqbqioza/nostrfy
bondar
https://github.com/iqbqioza/bondar
I'm operating a relay:
wss://relay.nostrfy.org
.
Going forward, nostrfy will take a more proactive approach to phasing out features that have been deprecated by Nostr NIPs, by putting them behind flags that default to false.
Letting outdated features stick around indefinitely can hinder the evolution of Nostr. When old relays remain unmaintained, client developers also struggle to maintain compatibility with them.
This may come with some pain, but I want relay-side developers to take the initiative and help everyone thrive on a newer, more modern foundation.
If we don’t take responsibility for this, who will? As a relay-side developer, I want to take responsibility and do my part in moving the ecosystem forward.
今日はメンクリ行って薬だけもらう
teppay アプリで色々と撤廃して欲しいのありそう
I'll try it out soooon
View quoted note →
個人的にこれだけは言える。
日本国内でもっとも利用規約に同意するのがめんどくさいのはJR。利用規約は最下部にいかないと次に進めないし、しかも運送約款もまとめてるから異様に長いんだよなあ。
My Transparency Report ⚡
This is my own initiative to be transparent about how I use the sats I receive.
⚡ Total zapped in the last 30 days: 64.5k sats
Where the sats went:
Thanks to your zaps, I was able to cover another month’s server costs for wss://relay.nostrfy.org.
What I’d like to fund next:
As more sats come in, here’s what I’d love to put them toward:
• An Android device for debugging — to test, troubleshoot, and improve apps in a real-world environment.
• Building new services and apps — especially projects that help people build a livelihood around zaps and make Bitcoin-native living a little more viable.
Thank you for every zap. ⚡
Every zap makes a real difference. Thank you for helping keep things running and making future experiments possible.
I want to keep sharing regular, transparent updates on exactly where your sats go and what they make possible.
My life is the experiment. Your zaps help make it happen.
Let’s see what we can build with this.
Good morning everyone!
Good night everyone
まじコロス... コロス...
おちょくりだした Gemini
View quoted note →
View quoted note →かわいいイラストをお願いしたのに思い通りじゃなかったから感想言っただけなのに、言っただけなのに... 共感してくれよぉ...


LOL
I dont abandoning Nostr🫂


Does anyone want to help build a new protocol?
As a developer of Nostr relay servers, I'll continue contributing to Nostr and nostrfy. However, I'm concerned that reaching consensus and establishing stable standards through NIPs will become increasingly difficult.
I'd like to start a separate project, independent of Nostr, and aim to build a simpler, more stable, and extensible protocol from the ground up.
This isn't about abandoning Nostr. I still believe in the project and will continue supporting it. I just want to explore a different approach to protocol design and standardization.
It's still an early idea, but I'd love to hear from anyone interested in discussing it or helping build it.
Anyone interested?
cc: @Gigi
WORD5 #745 4/6
🟪⬛⬛⬛⬛
🟪⬛🟪🟪🟪
🟪⬛🟪🟪🟪
🟪🟪🟪🟪🟪
WORD5
As the lead developer of the Nostr relay engine nostrfy, I’ve submitted six PRs to the NIPs repository, each addressing ambiguities and clarifying areas where the specifications were unclear. I hope they’ll all be merged.
Hopefully, these clarifications will help relay developers implement the protocols correctly without having to guess or interpret ambiguous specifications on their own.
I went through a lot of pain trying to determine whether the issues I encountered with nostrfy were caused by bugs in my implementation or ambiguities in the NIPs themselves. That experience is exactly why I wanted to make these improvements.
#nostr #asknostr #dev
View quoted note →
GitHub
NIP-29: define state reconstruction semantics and same-second tie-break by iqbqioza · Pull Request #2506 · nostr-protocol/nips
Group state is only well-defined for events as they are accepted: the child-list rules in the Subgroups section and the "latest of kind:9000/9...
GitHub
NIP-45: define exactness of COUNT results by iqbqioza · Pull Request #2507 · nostr-protocol/nips
approximate is currently defined only as an optional flag a relay MAY send when it uses probabilistic counts, so a client cannot tell whether a res...
GitHub
NIP-43: define the join/leave freshness window and relay verification by iqbqioza · Pull Request #2508 · nostr-protocol/nips
Join and leave requests must have created_at "now, plus or minus a few minutes", but the window is not a number and relays are not told t...
GitHub
NIP-59: refuse re-storing deleted gift wraps by iqbqioza · Pull Request #2509 · nostr-protocol/nips
NIP-59 tells relays to delete kind:1059 events that p-tag the signer of a NIP-09 deletion or a NIP-62 vanish request, but nothing prevents the same...
GitHub
NIP-62: clarify re-admission after a vanish request by iqbqioza · Pull Request #2510 · nostr-protocol/nips
NIP-62 requires paid relays and relays that restrict who can post to honor a request to vanish regardless of the user's status, but it does not...
GM
一部の人がAndroidのLinuxにnostrの入れて動かしているけど、持ち運びできるリレー、、!クールだ
Can I buy real raw honey with sats payments?
View quoted note →
(Screenshot) Running Android on GNOME Fedora Linux Workstation 44

