Mazin

Used to play poker now I build things and fly planes.

🍷 relay: wss://nostr.wine
🎥 relay: wss://creatr.nostr.wine
Filter and API: https://docs.nostr.wine
Translations: https://translate.nostr.wine

Public Key

npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

NIP-05 Address

_@mazinkhoury.com

NIP-57 Address

mazin@pay.nostr.wine

Profile Code

nprofile1qqsrmpp2lmx4u2fl9zmxy7fnwp9rlwxwz5a2j8tep2c376n494z2gtgpzamhxue69uhkxetvd3shytnwdaehgu3wwa5kuegpzamhxue69uhkxun9v968ytnwdaehgu3wwa5kuega6gx5u

Publishing to

cellar.nostr.wine

creatr.nostr.wine

Author Public Key

npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

Show more details

Last Notes

2025-05-23 03:39:47

- reply

Nostr.wine is a one time fee. Some of our other relays are subscription based. You can check if you’re registered on our website https://nostr.wine by signing in.

2025-05-21 15:48:47

We registered the 🍷 nostr.wine domain name on February 2, 2023 and I setup a nostream (shoutout to @npub1qqq…n47m) paid relay on it the following day.
The pay-to-write price was 888 sats and bitcoin was in the 20k range. Back then my rule was if you sent me your admission invoice, I’d pay it for you. The fee was just a spam deterrent and we were just starting to experiment with nostr.
Paid relays were just getting started as a concept back then and there were lots of new ones popping up daily. I think I signed up to at least 15 other ones, maybe more. They had modest one-time fees and I viewed these more as donations to support relay operators than as an actual payment for a service.
Seeing some of the other relay prices and performance, we decided to migrate to Strfry (thank you @npub1yxp…qud4), build our own custom BTCPayServer integration, and raise the price to 8888 sats.
Spam was just starting to become an issue on free relays so users started to experiment with reading ONLY from these new paid relays. They were spam free but they were also missing a lot of the content users expected to see.
Enter 🍷 filter.nostr.wine - our custom bridge to free relays, without the spam. Truthfully, @npub1qlk…lf5y and I built Filter for ourselves. We wanted to avoid reading directly from several free relays but without losing access to the free-relay content we found interesting. We also wanted to be able to write our events to those free relays without connecting to them.
Filter.nostr.wine is an aggregator relay that pulls events from the largest free relays in real time and broadcasts user events back to those relays. When our users view their global feed on filter, we automatically apply a follows+follows filter to the feed so that you’re only viewing notes from your extended network.
Since Filter was a heavier relay to run that offered valuable functionality outside of normal note storage/retention, we decided to make Filter a subscription service and give nostr.wine users a few free months to help with the transition. We also raised the nostr.wine price to 18888. We weren’t sure if anyone would be willing to pay an ongoing fee to use it, but we gave it a try and nostriches supported us.
With this support, we were able to add NIP-50 search, add new global views (all vs your network), and add NIP-65 broadcasting. We also reinvested some of the sats back in to nostr. We paid out 4 seperate bounties to nostr client developers to integrate NIP-42 client authentication.
Towards the end of last year, we made a large change to our aggregator data pipeline. “Purgatory” was released to combat new user spam without losing coverage of real users. You can learn more about filter.nostr.wine and the rest of our services here: https://docs.nostr.wine/filter/readme
We want to thank all of you who have supported us throughout our first 27 months of operation. This is not our full time job but it’s our passion project and we are dedicated to providing the most reliable paid relay on nostr.
Here is to another 27 months🍷💜

2025-05-21 14:14:33

- reply

To clarify my poorly worded post: Send invoices (payment requests) to our customers wallets directly, not request invoices from them.

2025-05-20 23:17:05

- reply

Yes! The subscription is for filter.nostr.wine and you can learn about that relay here: https://docs.nostr.wine/filter/readme
Signing up to nostr.wine gets you 1 free month of Filter to try it out.

2025-05-20 20:20:55

- reply

Taking only a quick look it appears they don’t use ephemeral events and mostly use giftwrap DMs to communicate so I don’t think so.

2025-05-19 00:37:10

- reply

Gotta be something like that just couldn’t find any documentation anywhere.

2025-05-19 00:33:06

What app is responsible for these ephemeral events with “peerId” in content? Absurd amount of events like this for the last few months.
{'content': '{"peerId":"D8tp0LvNCiVVVxVLUidg","offer":{"type":"offer","sdp":"109,217,57,20,176,24,225,136,120,225,50,232,201,72,37,118$D0zURFzRQw1HSd+YTlsRuwVn+5F8afEIc5hsPwz2hFahTnEk6xz4y/pt017hi1gUDBeU3cb8neIdwL02Es3RBgsyCbdpQx/O2liE0YzN4Qqw1+Bg2+/e74IVrLtgDiT21prPnq40xU9AOpgeXU2zoO28c2Uo23id4MJ1zIxkieY40GwAlTIpBrtycUUjigffCyW6RyW0fXPNEv0TRELHteM+Tn0WPgIkP3oF3TKP1pdn0jPK5KXAyX9YwHrhTckqD8MOqpXWJe2SuIAVow3FkAzWc6HmrZ/oTU21XLjgeg4hsXa7W5eV9qgrF2y53/rTg/du9dWTLW7HtMDBi0CXVtP+RulzGfPuAm9dLFfRjQLIcilwgf4u8+W8uYGOgnRFHdIsayrIp3XazFfPBPCFMAGdM1i9pXsRzA44QA+UdpDVoy2zc2hIeximIF3baM35EMiBh5V3IO2Ky/APuMsW1hrLAnAm6zZqaQk5ExCtXI7Ja7nTZRpLDbsWLdIIpeaZMvndQdlki58XIMdYOzQFsPY8hMNjycne5iQGIUboR7tAdzaVUYRIpRz/W/bgJRUrdClDFquO7bRNU8n1nLbKosMTf7YbSaBJ79W1kGLwfjY8c/lFqvPDhT0LGhpaIU8IMjzy3YSf0gh8FPzO85yid28PiMVNtzC98pweSaEtZPQVj4AYYwb7PZGmcOEVmazTu8yWMPzzsNgZUiqix63Qo7zAMHiPsxdFQhDJkXiiZfQpfnFhj30y99STnYeOORLgyIHPf0BexgAdia9/qkUPkDGZK1KH5A4or8aNWidU0+NzPCZLJKkMrXf3MSM7HkfZQrhZMY/NRXMUd9Ro8F7idiTtGvn8xxrcYqY5SLcop3ypdAcIEybnckNG91/8H6gCWEXH2Pn6zTK3qnF72J4myE/ei6CatyOXQwsR82obvP/ZjJJ2kfqlnp28CI768oEXwiHMNU4HxTVD6lBl6Q5GOsNSqWlVPSnPJiTGYD+w8V0X0oIkFl5PIkhu4z9NUjiql7QhDVLOzlMfmb5wD8pJs5w6jzqZada/HRF1UMkdYyiMAZ5aog=="}}', 'created_at': 1747612813, 'id': '1ac795e5a057fee8fb4e6d3ecfc41e9fc207fdb98ea991ab9d2a4a8157b2bf18', 'kind': 22732, 'pubkey': '9cea2f788a3006bfef93b48c5a42211f706b9e005b88419ec7e765feb8da2926', 'sig': '0835a6f794a4be96df246594484a716dffb76022e90245d0736f3782ec71b6c1bfa208c4323b7787a3031c806f397ee880c396011d6a06c93f1d8cdcd9072dbb', 'tags': [['x', '5f3i1q5e4g6qb1p456h221c1s6d29k5o62j47']]}

2025-05-03 20:23:25

- reply

Thank you! Appreciate your support 🍷

2025-05-03 16:01:43

It’s been so long since I’ve seen any reply spam that I didn’t realize it was still happening 😂
Blissful ignorance provided by filter.nostr.wine 🍷

2025-05-02 14:14:51

- reply

Non ephemeral events was my biggest complaint so thank you for addressing that.
I still think the design adds round trips and latency so it needs to be used carefully. Throwing things like search in to DVMs (instead of using NIP-50) makes no sense to me. Content discovery should probably have a special REQ/prefix instead of using DVMs. Then clients could just use relays normally and get events in one query.
If the DVM is just creating extra steps around talking to a relay it probably isn’t useful.

2025-05-01 20:45:40

- reply

🍷💜

2025-05-01 13:51:40

The call/response design and storing every single note is absolutely insane. We had to block most DVM kinds from our aggregator.
#note1pd4…m8dg

2025-04-30 16:24:04

- reply

Unfortunately, primal still doesn’t support NIP-42 authentication so filter does not work at all. They are one of the only clients that doesn’t support this.
In addition, primal doesn’t read from your relays anyway, only their caching layer so the use would be limited anyway.

2025-04-28 13:05:32

- reply

I don’t think it’s fair to assume those relays went down because they couldn’t sustain the infrastructure with their one time fees. Many of the people who hosted these relays lost interest and left nostr. Many of them had no technical ability to fix a relay if it went down. Many of them were using nostream which didn’t scale well.
The longevity and reliability of a relay is more about who is running it than how much it costs. Good admins run good relays. Free or paid. The time commitment is more about passion for nostr than making money. I can’t see that changing in the near future.
People who enter this space to “make money quick” will exit extremely fast when they realize how little money is available.

2025-04-28 12:59:11

- reply

🙄 people have been saying this for 2 full years. Let them keep talking and we’ll keep relaying.
I’m willing to bet nostr.wine will outlast all of the people who don’t understand our business model.

2025-04-25 02:10:44

Experimental support for multi-user AUTH is now available on nostr.wine and inbox.nostr.wine 🍷
https://github.com/nostr-protocol/nips/pull/1881

2025-04-14 14:26:59

Happy Monday! Spent the weekend chasing down bugs in a full rewrite of a large web app. The real user traffic always exposes weaknesses. Hopefully no more melt downs 🤞

2025-04-09 00:29:25

- reply

Yes - that challenge is exactly why we needed to evolve our approach. If you’re interested, this photo shows how our “purgatory” data pipeline works today.
Welcome only looks for new user posts within a very short period of time after the creation of their kind 0 event. Since their posts are often stuck in purgatory during that period of time, welcome misses their posts when they are later added to our relay. I could make changes so that these new user events are also sent to the welcome relay at that time.
https://i.nostr.build/61SaCp4c3Ns5TjZu.png

2025-04-09 00:14:37

- reply

When we introduced the new data pipeline for our aggregator it significantly reduced what welcome.nostr.wine will ingress due to the way it was built.
I haven’t spent any time updating it as many clients added hashtags to initial new user note prompts and it seemed less valuable.
If there’s still interest in that relay I can take a look at what needs to be done to update it.

2025-04-06 01:07:23

- reply

Ok - figured it out. That event is one you replied to, not one that you authored. Amethyst automatically rebroadcasts events when you reply to them. Your notes are on nostr.wine and not affected.

2025-04-06 01:05:44

- reply

I’ll take a look and see if I can figure it out. Hang on!

2025-04-05 17:40:09

- reply

It’s not about data. There are browser, OS (open files), and mobile per-app limitations that prevent opening an unlimited amount of websockets. Even in a perfect nostr world with only reliable high performance relays you will start to bump in to these limits in most places as you exceed 200-300.
As we do not live in this perfect world, I suspect the practical challenges of managing hundreds of different connection and response times with varying reliability in a performant way with an acceptable UX will not be trivial either.

2025-04-05 14:20:26

- reply

If you can build a performant client that connects to 400+ relays when trying to load your following feed I’ll build a nostr church in your name.

2025-04-04 21:29:10

- reply

I’ve only used nostr.wine relays (with most importantly filter.nostr.wine) for ~2 years. I don’t read directly from any free relays. For our aggregator behind Filter, we use a data pipeline we call “Purgatory” to strike a balance between coverage and new pubkey spam. There are tradeoffs but I’m quite pleased with the results we’ve seen thus far. https://i.nostr.build/61SaCp4c3Ns5TjZu.png

2025-04-01 12:05:28

- reply

Nostr.wine has been around for 2 years and I’ve answered many questions - trust me.

2025-04-01 11:54:31

- reply

And honestly it’s the opposite for me. I don’t respond because I think it’s good for the name recognition. I respond because it’s frustrating to have people spread falsehoods about your product(s). It leads to more user confusion and more time wasted answering questions.

2025-04-01 11:52:27

- reply

I read nostr everyday and you tagged me - but you (or anyone else) can keep an eye on https://api.nostr.wine/search?query=nostr.wine if you’re interested 🤣

2025-04-01 11:44:53

- reply

There will always be accounts that blur lines of automation/real. It’s up to users to decide if they value that content not me. Aggressive repetitive spam is what concerns me.
DM spam is harder to “see” but easy to address as an operator. You could rate limit DMs for new sign ups and only slowly increase those limits as time passes without reports.

2025-04-01 11:25:33

- reply

Not really. The reason they are challenging to block on free relays is they can create infinite pubkeys. On nostr.wine each one they create is 18,888 sats. What good is that if everyone mutes you after day 1 of spamming?
Filter.nostr.wine addressed this with our Purgatory data pipeline (quite successfully) since it reads from free relays and does not have the same advantage as nostr.wine.

2025-04-01 11:15:44

- reply

I have a business outside of nostr. So does Katie. We are obviously not living off nostr.wine. We are donating our time and will likely never recoup anything near what we’ve already invested.

2025-04-01 11:11:14

- reply

Brother - there is either spam on the relay or not. If there is provide me with some IDs, if not stop saying there is. The rest is a separate discussion.

2025-04-01 11:05:30

- reply

I’m replying to both of you in a thread filled with inaccuracies.

2025-04-01 10:58:16

- reply

For some reason the same handful of people are always telling me my relays are broken or full of spam when they have never been. Please send me IDs if you have a real concern - don’t just spread nonsense.
Of course we take spam seriously and of course we limit who can post replies to nostr.wine
Our pricing model has been quite successful and we continue to be the largest and most reliable paid relay on nostr 🍷

2025-04-01 10:52:47

- reply

(And never on a paid relay of any sort)

2025-04-01 10:52:01

- reply

And you are 100% certain they are on nostr.wine? I haven’t seen one in legit 6+ months.

2025-04-01 10:47:20

- reply

I’m not seeing it at all so I need some event IDs to look in to it.

2025-03-31 20:51:41

- reply

Not sure what you’re on about as usual. What spam are you seeing? Share some event IDs.

2025-03-27 12:15:07

Filter.nostr.wine was just down for ~100 minutes. The issue has been resolved and everything is back up. Apologies for the inconvenience.

2025-03-20 14:46:19

- reply

Thanks for the kind words Dawn! We appreciate you 🍷

2025-03-11 03:22:21

- reply

Hey - I’ll send you a DM and we’ll figure it out!

2025-03-04 15:45:03

- reply

I can manually delete your events if you’d like but without deletion requests it’s possible for them to be rebroadcasted and stored again.

2025-03-04 15:22:56

- reply

We may eventually but I don’t have any timeline atm. You can send individual delete requests for events.

2025-02-25 15:39:32

- reply

We could also argue the PR not getting merged killed mutiny. Both equally fair 😂

2025-02-25 15:38:09

- reply

What model are you using for nsfw detection? We’ve tried a few of the lightweight ones and found them to be really poor on average.

2025-02-25 15:31:23

- reply

Hahah yes but if you read the actual proposal you can’t believe any of these “possibilities”.
The entire purpose is to simple reduce an extra roundtrip from the onboarding process. Instead of having to leave our site, go to your NWC wallet, create and copy a URI, then come back and paste it to us all you have to do is scan a QR code from our website and approve the request on your wallet.
Do you really think this flow improvement killed mutiny? Who knows indeed lol

2025-02-25 15:18:38

- reply

The implementations that worked at the time were listed here: https://github.com/nostr-protocol/nips/pull/851#issuecomment-1879569550

2025-02-25 15:11:54

- reply

I too get the same vibe. He has no interest in arguing in the NIP trenches.
Give me your finished spec and I’ll implement it. I feel the same way the vast majority of the time.

2025-02-25 15:09:50

- reply

Well 2 of those implementations were Mutiny Wallet run so the proposal has died with them it seems. They were the only wallet provider that supported it. Alby used to say they would implement it (and presumably would if it had been merged). Now it feels fully abandoned.
We have just moved on with using the flawed onboarding flow and as such virtually no services interact with NWC at all.
I don’t think it can be merged as is anymore unfortunately. I think Alby is working on some other flow now 🤷‍♂️

2025-02-25 14:39:42

- reply

Ben did a lot of nagging back when he was actively trying to get it merged. He responded to a lot of feedback and kept pushing it for months.
There isn’t even much constructive feedback in the thread just a lot of confusion. The proposal was (more or less) ready to merge from the beginning and was quickly supported by multiple implementations (both on wallet and service side).

2025-02-25 14:23:09

I’m sad https://github.com/nostr-protocol/nips/pull/851 never got merged. We built a nostr.wine NWC service that relied on this improved onboarding flow in December of 2023. At the time Mutiny was leading the effort.
I don’t understand why it wasn’t merged then when we had 4 working implementations. It is the only reasonable NWC on-boarding flow I’ve seen for services (like nostr.wine).

2025-02-12 15:25:47

- reply

Appreciate the kind words!
I usually try to build some revenue generating part in to the MVP and then focus on the projects where there is user demand.
I’ve never applied for or taken any grants or VC money (on nostr or any other outside project) so this forces you to focus on revenue and some type of business plan earlier.
Doesn’t always work but helps to keep me from going too deep down a rabbit hole that nobody is willing to buy.

2025-02-06 17:59:17

I need to go clean the plane but having some serious motivation issues.
What’s your strategy for getting out of the house on lazy days?

2025-02-06 17:47:13

- reply

Heh - actually the regex in the php library doesn’t even validate if there is a reason phrase, only that there is a space after the status code. That regex leaves a lot to be desired and it’s an easy fix for them!

2025-02-06 17:39:30

- reply

We took a long look at this today. There are multiple layers of our tech stack that do not support reason phrases anymore. There are some ways for us to hack it back in, but given that reason phrases are optional and not required by any other client or the spec, this would be a considerable amount of work with limited gain.
It seems like this php library doesn’t do anything with the reason phrase besides check that it exists so perhaps it should be made optional there?

2025-02-03 18:25:25

https://media1.tenor.com/m/DKB4fw7EACwAAAAd/true-correct.gif #note1dlm…5g9q

2025-02-01 21:05:26

- reply

Any idea what the issue is? We updated it when they added CLOSED.
When a REQ is sent that requires AUTH and the connection isn’t authenticated, we send an AUTH challenge and a CLOSED with "auth-required: this relay only serves private notes to authenticated users"
I believe that is the expectation in NIP-42 - unless it changed again.

2025-01-31 18:50:44

- reply

I’m open to it but have concerns about moderation. Hosting media has more legal complications. I’ll do some research 🧐

2025-01-30 23:25:43

- reply

https://youtu.be/_3gD_lnBNu0

2025-01-30 19:51:39

- reply

https://youtu.be/r90Xw3tQC0I

2025-01-30 14:54:35

Still trying to process last nights DCA mid-air. Horrific. https://youtu.be/CiOybe-NJHk

2025-01-28 01:56:27

- reply

Thanks @npub1kms…tjep
Right now the creator tools are only available through the web with a browser extension or bunker login. You can use nostore on iOS as a browser extension with safari or nsec.app as a bunker.
On the user side, the content is designed to be consumed through whatever nostr client the user prefers. Our website is just a proof of concept.

2025-01-24 15:07:55

- reply

One of my favorites

2025-01-24 14:54:09

- reply

We made something like uptime robot but specifically for nostr relays called @npub1wsg…mlse
Not public like nostr.watch though. More of a tool for relay operators to monitor uptime and req/write latency.

2025-01-20 19:29:41

- reply

👋 🖼️

2025-01-20 19:20:11

Awesome to see some new faces today.
Welcome to #nostr friends 👋🍷

2025-01-15 02:27:35

- reply

Yessir 🫡 🍷

2025-01-11 23:11:12

- reply

Thanks for the kind words! Let me know if you have any questions @npub1tla…x3y7

2025-01-10 02:56:56

- reply

Yeah. Ended up being an expensive bounty we paid for a partial implementation 😂

2025-01-09 16:03:36

Moving my plane in to a shiny new hangar today 🎊 https://i.nostr.build/GJ4ifb2bndup5IPa.jpg https://i.nostr.build/tkVthZ26aM8HX41S.jpg https://i.nostr.build/VaWtNAxCBkU55wJV.jpg

2025-01-06 15:01:45

Purgatory helps us keep filter.nostr.wine free from spam while aggregating events from large free relays.
New users still have a way in and we preserve their events in purgatory so that when they are approved all their event history is immediately available on our relay. #note1dcq…edem

2025-01-05 16:15:23

- reply

https://www.nytimes.com/2024/11/27/upshot/airlines-flight-times-padding.html

2025-01-05 16:11:48

- reply

Worse! Lots of extra time packed in to those flights. That’s why you almost always arrive early when you leave on time.

2025-01-05 15:49:37

- reply

Also travel time per leg already includes so much extra taxi/dep/in route delay/arrival/taxi time that the 70-80% on time metric is a scam to begin with.

2025-01-04 00:59:47

- reply

Let me know if you have any issues! It’s been stable for nearly a year now I think.

2025-01-04 00:49:02

👋 https://i.nostr.build/q3RTiGkGGvSrpjCO.jpg

2025-01-04 00:47:10

If you run a relay or care about the uptime of one… #note1r49…jf0r

2025-01-03 16:09:18

- reply

We don’t have any intentional restrictions on those kinds. What kind of notice/error are you seeing?

2025-01-03 16:07:47

- reply

Done! There is now an initial alert event if the new relay is down + an “unknown” white circle instead of the red down indication on your dashboard.
I also added 3 months of PRO to your npub so you can see the read/write query times as well + more history. Thanks for trying it!

2025-01-03 15:14:50

- reply

I’ll have to double check but I believe the logic is you only get notified on changes, so that makes sense if it is still down.
More of a reason to add a third unknown status. I’ll do that today!

2025-01-03 14:58:59

- reply

Brief restart in progress to update that machine now that we are talking about it :)

2025-01-03 14:53:47

- reply

There is also a known bug where if the application breaks for any reason it triggers an offline/online alert for all the relays. Usually less than one a month. Besides that it’s been mostly stable for a year.
I’ll fix a few things when I get a chance though! Let me know if you have other ideas or issues.

2025-01-03 14:51:36

- reply

Good suggestion - there’s a good amount of work that needs to be done to professionalize this but I am currently the main user and it works good enough for me :)
I have limited time to dedicate to nostr so I try to focus on our more regularly used products.
It is working for me at the moment. 10 min checks happen on the XX:X0.

2025-01-03 14:10:57

- reply

@npub1wsg…mlse is free 😉

2025-01-01 01:50:35

- reply

🍷🍷

2025-01-01 01:50:28

- reply

Appreciate that - thanks for the support 🍷

2025-01-01 01:50:03

- reply

🫂 🍷

2025-01-01 01:49:50

- reply

🍷💜

2024-12-31 23:55:32

- reply

🍷🍷🍷

2024-12-31 23:53:43

Happy New Years #nostr
Really proud of the reliability across all of our nostr.wine products this year. Let’s run it back next year 🥂

2024-12-24 23:38:37

Merry Christmas and Happy Holidays friends. 🎅🎊

2024-12-20 16:09:33

- reply

That's exactly it and I figured that was the case after you said that. I just deployed a change and extended your account for you. I also DM’d you the details!

2024-12-20 15:55:32

- reply

Thanks Daniel. @npub1k6f…tryn I’ll take a look for you in a few min and send you a DM.

2024-12-10 00:52:36

Good evening nostr. Climbing through 19k feet this evening on my way across the pond ✈️

2024-12-03 12:17:54

- reply

This design has been working well for our aggregator. Not a solution for every public relay of course.
#note1dcq…edem

2024-12-02 03:35:29

- reply

Thanks for the kind words 🍷

2024-12-01 20:51:30

- reply

Thanks for the awesome review! I’m really glad to hear it’s working for you as intended. Let us know if you ever have feedback/future feature requests.

2024-11-20 23:05:22

- reply

Welcome 🍷

2024-11-11 21:55:27

🍷 Glad to hear you like it - sorry it took us so long! #note1qhc…usax

2024-11-11 15:08:03

- reply

Thanks @npub17nd…950x
I’ll send you a DM and we can chat further!
@npub1cre…feh6 is far from perfect and is certainly not a YouTube replacement but it’s a MVP we’ve built to showcase paywalled content on nostr through a relay (wss://creatr.nostr.wine) that works(ish) out of the box on most popular clients.
The website is basically just a micro client example for subscribers/fans/viewers and a place for Creators to manage their files/posts.

2024-11-06 05:54:45

- reply

Hey - I can see your account is active and you your notes are being archived on cellar. Those errors you’re seeing are likely because Amethyst tries to rebroadcast the notes you are replying to when you respond, and those events are being rejected - not yours.
We need to improve this so we ignore messages that aren’t from the authenticated user. I’ll take care of that later this week. But don’t sweat the errors - everything is working for you and your notes.