
I do that elsewhere, but I use the repository to keep the UI responsive. I might have to do something more though to ensure updates take properly.
🔔 This profile hasn't been claimed yet. If this is your Nostr profile, you can claim it.
EditI do that elsewhere, but I use the repository to keep the UI responsive. I might have to do something more though to ensure updates take properly.
There was some goofiness with the relay read/write flags related to second-granularity timestamps (if you clicked too fast coracle kept the old version of the event). I've fixed this in the next release.
Thanks, sounds like something is up, I'll take a look
This is Coracle? I just tested it and it is sending the kind 10063 to my write relays correctly. It doesn't create one if you don't change the field, but it doesn't sound like that's the case here
It hides that fact that you use tor from your isp
It was all my wife
Yes sir
Coracle is probably one of those clients 😅
Yeah, I never got around to an implementation because I was pretty busy at the time with other things
Combining `p` , `e` , `t` , and `word` mutes into a single list is so stupid. In order to properly support any of these features, you need an interface for two separate scenarios (private and public mutes). If you want to support all four, you need eight separate inputs. A perfect case study in why it's annoying to overload event kinds.
Both of those rejected protected events (events with a `-` tag). I have a fix for this in the next release
The editor library I'm using is 90% great, 10% buggy and impossible to fix
Yeah, communities can be an on-ramp for people. But the apps have to be good first. NIP 72 has the most implementations, but the spec is kind of garbage from a moderation stand point. It's fixable, but also only applicable to reddit-type communities (and has all the same problems with tyrannical moderators).
Community apps feel like the new nostr gold rush, everyone keeps building new ones that all work completely differently. I agree with their importance (obviously), but it seems like this has the potential to fragment things more than ever, just because communities are a rorschach test. Everyone also has their own libraries and preferred development stack. What if we just all agreed to start from scratch and work together to create something new? It probably wouldn't work because we're all so disagreeable, but one really good community app would be better than 10 incompatible ones.
Location is in there because flotilla has an optional location field on the calendar event form, which takes any string. That's it.
Yeah, that's valid. But it's also individual developers' responsibility. Lots of us have dropped support because incompatible dm standards is better than leaky dms
Ok, I have a vague recollection of that. Sort of a cheap shot tbh
You're clearly not listening to what I'm saying
If you haven't already, give flotilla.social a try
Join us
Just made a website which tracks nostr projects I've created that are approximately useful: https://stuff.coracle.social/ Maybe they will be approximately useful to you too.
This was really fun
Christian Bitcoiner and developer of coracle.social. Learn more at info.coracle.social. If you can't tell the difference between me and a scammer, use a nostr client with web of trust support.