The beta version of the Alexandria library: https://next-alexandria.gitcitadel.eu/about Our project homepage is: https://gitcitadel.com Join our relay: https://theforest.nostr1.com/ Our Lightning wallet is: https://getalby.com/p/gitcitadel
Silberengel @Silberengel - 34m
Yeah, that's been a goal of my Contact page rewrite. Have you heard of "Five Lines of Code"? https://dev.to/kanani_nirav/the-five-lines-of-code-principle-why-less-is-more-in-programming-31j6
Silberengel @Silberengel - 37m
Yeah, we just need the API-level. 🤙
Silberengel @Silberengel - 2h
Absolutely. We're finally a large enough team that we can break down into topic-teams, and each subteam just needs to coordinate ticket-priorities with the others, rather than everyone needing to know everything about everything. I am so relieved. You can't even imagine. 😂 I was getting ground to a pulp, for a while. It's such a massive undertaking.
Silberengel @Silberengel - 4h
Feeling especially blessed by our backend dev team, this week. I don't understand half of what you are saying, but I can tell that y'all understand each other and I can see the tickets opening and closing, and the stuff getting fixed, upgraded, migrated, and built. That gives me one less thing to break my own head over. 💕 So, shout out to: nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h and a "get well soon" to our newest addition.
GM I know that many of you are wondering why we're breaking our heads eeking out performance improvements, ironing out minor bugs, juicing up the backend, redesigning workflows, restructuring the code, etc. etc. etc. But we don't just want the app to _be_ good, we want it to _do_ good. A reading and publishing app can only do good, if it finally levels the playing field for all readers and publishers. Everyone, everywhere, of any means, and using any hardware or mobile/Internet plan, should be getting a first class user experience, access to the most basic and the most cutting-edge functionality, with powerful analysis, backed by a large and stable team of topical experts, scientists, engineers, support staff, and fellow writers. Taking part in the Great Conversation shouldn't be a matter of wealth or influence. And we want to make sure, that it isn't. 👇🏼 Don't make me tap our sign.
Silberengel @Silberengel - 13h
I'm suggesting we skip the publication "type" Tag and use the "M" tag. Then changes to the M tag would alter the reading view configurating and style sheet.
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku
I don't know if we need replaceable, since that's actually a relay function, not an aspect of the use case, and it can be calculated from the kind. Should maybe do meta-data/index/blog meta-data/index/academic meta-data/index/book And etc.
Do you have an example event for #communikeys? I could publish one for theforest and then you'd have another a realistic example.
Silberengel @Silberengel - 15h
We're reducing the highlighting, and moving to more deliberate selection of particular blocks. Find it irritating, to scroll through a book and have things flashing at me. Yeah, there's going to be multiple interactions possible.
Yeah, that's why we've locked write capabilities, until we're done. It's just supposed to give people something to look at and explore a bit, so that they get the general idea. Tricky, demoing in the alpha stage.
Don't tease. I'll faint and fall right off the chair, when the ToC finally works again.
Silberengel @Silberengel - 21h
You're just reminding me of why almost all OpenSource is useless trash.
Silberengel @Silberengel - 1d
GM and Happy St. George's Day!
That's always the "vibe-coding smell": hysterical or aggressive reactions to bug reports. Bug reports are a normal part of supporting software. All software has bugs. That shouldn't upset you.
And when I point out bugs, I often tend to get ignored or receive defensive reactions. Which suggests that they don't understand their own code well enough to figure out what went wrong. I think they're hitting the vibe-code ceiling.
I think they just don't test anything. They hack around wildly, deliver and basta. And they don't have a team to help with testing and reviews.
Almost all Nostr apps. The ones that have microblogging.
Building a social feed has been an interesting experience. I thought it would be really hard because the kind 01 apps are such a mess, but it's not. I now have no idea why the kind 01 apps are such a mess.
Yes, we're also going to focus on building extensions, but for OpenDev as the first one, since we'd be using that ourselves. If you made a generic Nostr API, then we could just expand upon that, with more implementations, like Jira and OneDev. You would have to structure it to be expandable, with a field mapping system, of some sort.
