Uh... No. I'm not sure what devs you are referring to, but... No.

Reply to this note

Please Login to reply.

Discussion

CICD DVMs and Kanbanster devs litterally implement the features I request and bugs I submit within the same week I submit.

Cool.

That's 3.

I mean what else do you want? As a dev, I need a place to track work, a place to store work, and a place to run work. I guess you can add a place to talk about work, but that clearly already exists.

All the rest of the things needed to build nostr stuff. Like, most code it still on github. Friggin ew.

We also need a calendar system that can be integrated into any nostr client. That's VERY sorely lacking.

It's easy to get off GitHub, already, (other than as a mirror), with a self-hosted gitserver and Nostr repo event.

Then why has that not been done for anything of real import like the nip repo?

Because they like GitHub.

because they are all homosexual

calendar points in the right direction

we need email, calendar, private video/audio conference, client facing support logs, issue boards, kanbans, document repo systems, blogs, threaded discussions for fans and devs, crowdfunding integrations, instant messaging with threads and that functions as CLI for most of the above as well

probably some accounting systems would help also, bonus points they are bitcoin native

Do we email, though? I'd rather not...

email and instant messaging are the same thing in my opinion

They should basically serve the same functions, yes.

this fact alone hints at an architectural issue in both instant messaging on nostr and the pop/imap protocols

they are instant messaging, yet they pile up like forever data that 99.999999% is completely worthless

this is why my idea of proper instant messaging (including large, richtext messages) should be cached but not archived, and for the most part, deleted

that is, it's primary conveyance is pure relay, no caching... caches are specialised relays that you set up to subscribe to catch your messages and store them for later... if everyone had some kind of "chanserv" for their messaging (including everything, really) you could cut out the whole relay list concept altogether and instead replace entirely with outbox where for most cases you simply send your messages to the relays where other users will read them, and those relays will be subscribed by their home and office chanservs that will archive and make these accessible to the users via the relay only relays that do middleman service

there's a whole vision i have in there about that, maybe that does give you some hint at it tho

Put it this way. The houses exist, but the rooms are just bare walls.

We consider these all useful prototypes for defining the event structure and helping people understand the functionality, but they're not enterprise systems.

That's a serious 🚩, sir.

You're talking to the person who sent nostr:nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9nhwden5te0dehhxarjv4kxjar9wvhx7un89uqaujaz back to the drawing board on something tiny, like logins, for the fifth time in a month.