<unnamed>

Public Key

npub174tphl6zaczjxvm6k8rrsl7282457apjqf9cm2mrvwev098vz48slylth2

Profile Code

nprofile1qqs024smlapwupfrxdatr33c0l9r4260wseqyjud4d3k8vk8jnkp2ncpz4mhxue69uhhqatjwpkx2un9d3shjtnrdaksz9nhwden5te0wfjkccte9ec8y6tdv9kzumn9wsq32amnwvaz7tmjv4kxz7fwv35hgar09ec82cspz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qzrthwden5te0dehhxtnvdakqzxmhwden5te0vakx2ctndahxzar0wghxgetk9aex2mrp0yh9nehx

Publishing to

gleasonator.dev/relay

Last Notes

2026-10-09 17:39:49 UTC

- reply

Yup, that's the most difficult truth to accept about Nostr — that it'll likely never be anywhere near as popular as any of the centralized platforms, because most people actually WANT to live in echo chambers and go to war with the people who disagree with them.

2026-10-09 03:25:03 UTC

- reply

Haters gonna hate.

2026-09-29 09:55:50 UTC

Just noticed @npub17fe…nzuc finally has full support for custom AND emoji reacts now, including a nifty quick bar with your most frequently used ones. Nice work, guys. :peepoClap:
https://blossom.jumble.social/e719800fa012b96cd486101f42466b8d34cf236ac24ccce9936a06f987d1f9c0.png

2026-09-20 07:29:41 UTC

- reply

Bitchat uses ephemeral messages, relays do not store them in their DB. They only cache them in memory for a few minutes, long enough to potentially enforce an IP rate limit, but that's about it.

2026-09-20 07:14:52 UTC

Hey @npub17fe…nzuc, I'd like to report a bug. When using the comment editor, when you attach an image and enough text to push the "Post" button below the browser's viewport, there is no way to submit it, because the dialog doesn't scroll (the textbox will if you write enough in there, but the button itself remains unreachable).

2026-09-20 07:06:55 UTC

- reply

Basically, it spams every channel with verbal abuse using multiple identities with constantly changing keys, to the point of having vaguely non-sequitur "discussions" with itself. Pretty sure this is all the same guy. Currently he seems to be using variations of Gustavus a lot, but that changes too.
It was even using vanity keys for a while (npubs whose hex representation ends on 4 of the same digit), suggesting that whoever is doing this knows the protocol fairly well.
https://blossom.jumble.social/ade544fe60947d264e076b74e2dae97344c4d64bb9267b8405066798b81586c7.png

2026-09-14 07:33:02 UTC

- reply

https://blossom.jumble.social/97c6d6512789900120af8816ab4578db0ccd4243d4ab3b2b5d457e848e5b6d33.jpg

2025-10-06 18:29:03 UTC

- reply

I mean, you’re not wrong, but this is literally the first thing anyone does when building a new compiler or OS, so it’s only fair you’d do the same.
Still, it’s a great accomplishment, because it separates the men from the boys (and the tools from the toys).

2025-09-26 03:06:21 UTC

- reply

Clearly you have never met my dad.

2025-09-21 05:27:36 UTC

- reply

nsecretary of state

2025-08-28 02:58:57 UTC

- reply

I'm honestly wondering if this was a good idea, at least at this time. I'm sure you had good reasons to do it, and I certainly don't understand nearly half as much about the technical aspects as you do, but being able to find active rooms on a map view was really neat. As was having a choice of a variety of different clients that could all talk to each other.
Spam was a problem, yes, but Nym showed that it was fairly easy to get rid of by simply using a relay that has rate limiting (such as Damus's). I understand that it would of course cause even more centralization if everyone was going to use that, but unless traffic was already causing severe resource strains, wouldn't it have been better to wait until there is a more significant userbase?
A lot of people I talked to had trouble even understanding how it worked at this stage, how are they going to understand that there may essentially be several different versions of the same room on different relays, and depending on which client you use, you might see entirely different conversations?
If it is not possible or desirable to expect other relays to rate limit, couldn't that be also done on the client side instead? For instance, any single account sending more than one message per second is likely spamming, as is anyone sending the same message from different accounts (such as the semicolon troll).
Other alternative clients have tried different approaches — For instance, Nym has a customizable keyword filter, and bitmap.lat has a rudimentary pattern-based filter that worked pretty well that could potentially be ported to the app (you can see what it tests for in `src/lib/spam.test.ts` on their NostrHub).
Basically I'm left wondering whether this move at this time killed all the momentum Bitchat had until now. My experience today was that most rooms on the app are essentially dead, and the ones that are working are those still using the global relays.

2025-04-05 05:19:40 UTC

- reply

How many of those emails are spam?