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.
Public Key
npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn Profile Code
nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspqqq3xamn8ghj7vfjxuhrqt3s9ccn5dpcxcushqru46
Show more details
Published at
2025-09-29T17:19:34Z Event JSON
{
"id": "c03f02424aaa39d37c90639f14f479f711a0977882f34124bce66b67cfbb5ede" ,
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322" ,
"created_at": 1759166374 ,
"kind": 0 ,
"tags": [
[
"client",
"Coracle",
"31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690"
]
],
"content": "{\"lnurl\":\"lnurl1dp68gurn8ghj7em9w3skccne9e3k7tewwajkcmpdddhx7amw9akxuatjd3cz76r0v3kxymmy8s5283\",\"name\":\" hodlbod\",\"display_name\":\"\",\"picture\":\"https://hbr.coracle.social/9d20c2f4e4e5bc3914c02acf08b56742139508df833c3c98c72bda23c2b76409.jpg\",\"about\":\"Christian Bitcoiner and developer of coracle.social. Learn more at info.coracle.social.\\n\\nIf you can't tell the difference between me and a scammer, use a nostr client with web of trust support.\",\"website\":\"stuff.coracle.social\",\"nip05\":\"[email protected] \",\"banner\":\"https://hbr.coracle.social/571c66854bdba58bc77def7b0fcfe2f7b8109a35d7952888a9e4381b9791cec4.jpg\",\"lud16\":\"[email protected] \"}" ,
"sig": "592c17f916a11c556addc17866ff8336fb75096afb212529685e8a7e2b3448ba4854cdf6b3f2b896a11bf62bb97f65edd343531b29b3de17f257e2070ec4e1a8"
}
Last Notes npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Double buffers are one of the coolest programming techniques, and are relevant more often than you would expect npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod That's what it looks like to me npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This is pretty funny #nevent1q…y3l3 npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This is a settings event by Amethyst, don't worry about it npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Cool, I've always been curious about this npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod wrong again npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This is nice npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Isn't that what GMT is for npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod @nprofile…992e pointed UCAN out to me this morning, which is an interesting protocol for bearer token authotization. I can imagine this being useful for nostr, but I'm not sure exactly how yet. Maybe a better way to do relay authorization or social circle-type features? https://github.com/ucan-wg/spec #nevent1q…cmlx npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Thanks, that'll be fixed in the next version npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod > The "e" tag with "mention" marker only ever had a correct meaning: a quoted event, same as "q" tag. I just looked at the commit history, and you're right. I think I got thrown off by this commit: https://github.com/monlovesmango/nips/commit/5733d3b7c1249570d77433f4d416384b028b3d93 Amazing that it happened three years ago and I thought I understood NIP 10 the whole time, but apparently not. I've released an updated version of coracle that no longer publishes e tags with `mention` markers. Thanks for pointing this out. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Thanks, just released a fix that should solve this npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Thank you! That's all very helpful, I will see if I can address this stuff today. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod An important premise of nostr is interoperability, both in technical and social terms. If clients don't run relays their defaults have to be provided by a third party, reinforcing the social cobtract that if you run a relay and don't actively protect it, anyone can connect. Like how opening a connection to port 22 is legally considered hacking, but opening a connection to 443 isn't. It also distributes risk posed to the user and encourages technical ibterop as well. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This looks very cool, would you like to talk about it with me on the @nprofile…yk3s? npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod It sounds like you tried to access the space with a different user from the one you signed up with? Or did you sign in with that user first and then generate an invite code for the dummy user? Invite codes should auto-add members, but let me know if that's not working. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod All it takes is actually deploying the code I tested 😅 npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Ok, so apparently auto-deploy was turned off on Flotilla web, so if you've been confused as to why there aren't any new features and everything is broken, try a hard refresh and look again. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Returning to a project I haven't touched in two months: https://blossom.primal.net/27fba409944a93adf5574fb417c5c81383d93b88e76455ba2ea73272ec3212d4.jpg npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Thanks, unfortunately I don't have a windows computer to test on :/ npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Aaaaand 1.5.2. If your rooms are missing, you should update. #nevent1q…wh73 npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Ah, yes I see, I've tried to fix that numerous times, but it's very hard to get something that looks good on all platforms. Are you on linux? npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod You mean the "show 1 other note" thing? Maybe if you recorded a video that would help npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Flotilla 1.5.0 (and 1.5.1) is out! This release leans into rooms by implementing the various access control flags defined in NIP 29 and in this PR: https://github.com/nostr-protocol/nips/pull/2106. I've added support for room policies and member lists to https://github.com/coracle-social/zooid, which is getting closer to a stable state. Also noteworthy are the addition of space membership lists based on the newly merged NIP 43 for proper two-tier access controls. Most exciting though is the launch of https://hosting.coracle.social, which allows you to set up your own hosted community relay. I fully recognize my own hypocrisy here (I've long said that client developers shouldn't run relays), but I also recognize that it's easier to monetize hosting and support than client software, which I very much want to do in order to help nostr become self-sustaining. To reduce the coupling between Flotilla and Coracle Hosting, I've added a list of hosting options to the "create space" page which lists several alternatives: https://blossom.primal.net/313af33da4e1b7a317f54350af5db3f1dac2b2808ebecdb68bf2516983f76fc0.png I've also open-sourced the infrastructure that powers Coracle Hosting, so you can run your own version of it! If you want to be listed, please contact me and I'll add you to my hosting services page. Here are the repositories in question: https://github.com/coracle-social/metamanager https://github.com/coracle-social/website The neat thing about metamanager is that it includes a chat bot which allows admins to manage virtual relays from a NIP 29 room. This way, Flotilla (or your preferred groups client) actually becomes an admin dashboard! With all that out of the way, here's the full changelog for this release of Flotilla: * Restyle mobile dialogs * Add room membership lists * Add space membership lists * Add edit room form * Support closed/private/restricted/hidden rooms * Add hosting services page * Improve performance and UI * Fix push notifications * Improve error detection and handling * Support invite links on discover page * Add link to landlubber if user is admin * Clear reply/share/edit on escape npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Not sure I'm following, where's the citation? Looks like a normal kind 1 npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Hmmm are you able to tell me what relay this is? What if you log out and back in again? npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Can you link an example? And this is coracle? npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod That makes sense, thanks. Also, I tried to zap you but got a CORS error. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Yeah, gitworkshop seems to be connecting with relay.ngit.dev ok (gitnostr.com doesn't seem to be connecting). When I run ngit sync I get `failed to connect to relay.ngit.dev: Operation timed out; class=Net (12)` npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod It's live now on web and zapstore, android and ios will be a few days npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Don't worry, I'll have different things for you to be frustrated by npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod No, but I am literally releasing an update to fix this as we speak npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Who needs channels when you can have not channels npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod It also auto opens an nwc payment dialog npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I'm aware of those aspects but don't see how that (or the early bugs and founding company) necessarily make it a scam nowadays. The zk tech seems pretty promising to me. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod tell me more npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod FOMO got me. Also, fanfares is trying to open sparrow, which seems irrelevant npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I vibed https://highlights.shakespeare.wtf/ the other day for manual highlighting from print books npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Absolutely, I think that breakdown is the right call. A blossom library could be built separately npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I would entirely skip the networking code, but yes npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod No, it's mostly just the core structures that I use. I could migrate to go-nostr, but nostrlib is genuinely better in this area. I attempted to switch to rely this morning and decided against it for now due to the lack of negentropy and blossom support. I get not wanting to include that stuff, but examples or external libraries would make the process easier (I do think negentropy should be table stakes for relays nowadays). npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod No, that makes sense. fiatjaf's libraries tend to have some super important primitives in them (like the event and filter structs) alongside very opinionated stateful stuff like khatru and nostr-tools' relay connection logic. It would be nice to have a nostr basics library with a much smaller scope that everyone could agree on so you don't have to write adapters between other libraries. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod @nprofile…9n8g I have been getting errors with ngit's relays lately: ``` ➜ nostrlib git:(master) ngit sync ✔ select nostr repository from those listed as git remotes · origin - hodlbod/nostrlib fetching updates... ✘ wss://gitnostr.com connection timeout ✘ wss://relay.ngit.dev connection timeout ✔ wss://relay.nostr.band no new events ✔ wss://hbr.coracle.social/ no new events ✔ wss://relay.damus.io no new events ✔ wss://nos.lol no new events no updates fetching relay.ngit.dev/npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn/nostrlib.git ref list over https (unauthenticated)... list: https://relay.ngit.dev/npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn/nostrlib.git failed over https (unauthenticated): failed to connect to relay.ngit.dev: Operation timed out; class=Net (12) fetching relay.ngit.dev/npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn/nostrlib.git ref list over ssh... list: connecting... ``` Gitworkshop appeared to sync ok, but it gave me an error: ``` "master" expected at 4e8a04c1 (nostr state) but showing 59bd3c29 (git server state) as data not available. Ask mainatainer to run `ngit sync`. ``` Any tips? npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod In any case, if you want it this should be a good start: https://github.com/pippellia-btc/rely/pull/4 npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Do you have thoughts on migrating from go-nostr to nostrlib? npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod test reply npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This is a test comment, trying out new tag generation code npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I keep forgetting to use it, but I'm very tempted to port my current relay project over npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Hmm voyage is actually very wrong, it'dropping the root tag. I don't know about pokey npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Coracle inherits all e tags from the parent as "root" or "mention" as defined by an old version of nip 10. Voyage doesn't do that, so the chain is always broken and coracle's tags are incomplete (I'm not going to crawl the whole conversation just to populate tags). Voyage apparently interprets these mentioned e tags as quotes, which isn't strictly wrong because that's how some people did quotes early on, but it does collide with nip 10, so the only way out would be to switch to q tags for quotes (which is in the nips repo now). In summary, both clients are using different obsolete specs, but voyage is slightly more wrong. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I have calendars, RSVPs wouldn't be hard to add, just hasn't happened yet npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Let me know if you need any help, I'm still working on stability npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod still a huge improvement npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This is awesome, but there are some z-index issues https://blossom.primal.net/7ac69a33cd0927c38c39f121eb236b7c8866500af9fe86118ae0f0f73f711ab1.png https://blossom.primal.net/6b5ad1a58fe9944628958ea8cf4c09a957e577938a69055778370c80a9b406e9.png npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod https://hol.is is a pretty cool option for community relay hosting npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod One of my favorite christmas songs for sure npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I got it right the first time smh npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod When I type "localhost" I generally type "lo" and hit enter, and every single time I start singing "Lo How a Rose E'er Blooming" in my head npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod *backwards incompatible smh npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Just drafted a new NIP 29 PR: https://github.com/nostr-protocol/nips/pull/2106 This adds "hidden" groups, and redefines the "closed" tag to mean something that makes sense. The latter change isn't backwards compatible, so please tag anyone who has a stake in nip 29. @nprofile…64jc @nprofile…9h9m @nprofile…4pak @nprofile…u7dq npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod None of mine (yet) npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Yeah, I think it would be a perfect fit for jumble npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod You have been very quiet lately npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod NO npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod debugging websocket stuff is the very worst, hang in there npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod A pull request I've had open for a year and a half has finally been merged! Thanks to @nprofile…9h9m for adding it to pyramid. https://github.com/nostr-protocol/nips/pull/1079 I actually think this PR is a pretty big deal — it adds relay-level join/leave requests, confirmation, and member lists, as well as invite code generation and redemption. I created it to support relays-as-groups in flotilla, but a secondary goal has always been to enrich nostr as a whole by allowing relays to be more explicit and dynamic about member lists. No longer do we have to hardcode whitelisted pubkeys or wot algos (not that there's anything wrong with that). I talked about this (and other things) at nostrasia almost two years ago. I'm excited to see some very clear progress on that goal! You can watch my talk here: https://www.youtube.com/watch?v=R-5DHymkfzw&t=1s npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Here's a useful snippet for using your secret key on a website that only supports extension login (useful for testing stuff in a private window): import('https://cdn.jsdelivr.net/npm/@welshman/signer@latest/+esm').then(mod => { const secret = 'your hex secret key here' const signer = mod.Nip01Signer.fromSecret(secret) window.nostr = { getPublicKey: signer.getPubkey, signEvent: signer.sign, } }) npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Zooid is a multi-tenant relays-as-groups relay based on nostrlib, frith is a single tenant relays-as-groups relat based on the old khatru. Once zooid is up to par I'll archive frith npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Hex, I believe Amethyst does the same https://github.com/coracle-social/welshman/blob/3132b8c59aa97ceb92ab2c0bf5abaa4911584607/packages/util/src/Blossom.ts#L225 npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod 100% npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I think there should be at least *some* pathfinding, drawing the lines exactly straight doesn't seem in the spirit of the game npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod No, you're all wrong, it's Nostr npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Nice to hear, thank you! npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I'm not focusing on lists, I'm focusing on communities right now. Anyway, ideas are cheap, someone has to put in the work to make a product that's really good and which other people want to interoperate with. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod That makes sense, probably doesn't solve the underlying problem so do let me know if it crops up again. I'm releasing another version that should improve things a bit more as well. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod - Figuring out how to scale them and avoid race conditions when updating - Choosing specific kinds that are clear, but can be used for multiple reasonably similar use cases rather than proliferating or overloading kinds - Deciding on a good way to build feeds based on lists (also lots of dueling standards/philosophies here) - Once that's all done, add lists to clients in a way that's feature complete and interoperable This is a much bigger lift than it looks like. No one has really "owned" lists and built a 100% complete implementation. Coracle is like 70% there, primal maybe the same, but both basically suck for actually using lists. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Yeah, lists are important. Unfortunately everyone keeps reinventing them without solving them (c.f. "follow packs"). At the same time, people mostly complain about software being flaky, and I think devs are solving that. It's the kind of thing that takes a lot of time and experimentation given the novelty of the protocol. We'll circle back to the features in due time I'm sure. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod shiny thing syndrome, combined with people getting serious about their core value prop means the stuff listed is still going to be a while. I'm bullish, people seem to be approaching product development more seriously nowadays (which results in slower pace of development). npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Yep, I use it to sync my indexer with a few others. Outbox model is somewhat more complex though, replicatr is intended to help fix missing note parents and stuff like that (although I can't help wondering if it's a band-aid solution). npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I just released a new version to web, can you refresh and see if it loads your threads now? npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod It's probably because he closed his laptop or something npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I don't think it would be bad to just add a `path` tag to that event, but I'm not really sure how people are currently using it, or how bad not having a path would be. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod There is this: https://github.com/nostr-protocol/nips/blob/master/94.md which can be used to map hashes to names. rclone looks great, and nostr would be a natural fit. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod https://fountain.fm/episode/e2Ub6SVUpp0ME9R1zIPb npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Neat! I like negentropy, welshman/net has support for it, and is actually what powers replicatr npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This guy gets it npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Because npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod But secretly you do npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Social media is for saying funny things that you don't mean npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod If you have questions I will always reply noncomittally If you disagree with me I will ghost you npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Nevermind, github converted my release into a draft for some reason. It should work now. npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Oh, weird, it got converted to a draft so only I could see it. Re-published it, now it should work npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod They should still be there, but flotilla now does feature detection before deciding whether to show the tab. I'll look into it npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod @nprofile…056v it worked for me yesterday but now I get the same error npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Only if you ask permission first npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod No? That link works ok for me npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod "social contract violation logged" lol npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod I think today was a new record, I released new versions of FOUR different products npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod Flotilla got a little bit better today. The new 1.4.0 version brings a new experimental idiom for creating events/goals/threads, in which all content types are posted to chat rooms, but are visible in a dedicated view as well. I've also added some things that people generally expect from chat rooms, including up/edit, member lists (very beta), and customizable room icons. Here's the full changelog: * Allow "editing" chat messages * Check for room create permission * Re-work space navigation * Show all messages in non-nip29 chat * Improve synchronization logic * Add connection status to space menu * Add icon picker to room create component * Improve mention suggestions * Improve storage adapter and relay list performance * Fix modals * Add room deletion * Fix zapper loading * Add support for relay/group member lists and join/leave events npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn hodlbod This service replicates everything else