What is einundzwanzig-app? 👀

I'm not seeing that comment.

This is because a git repository can't be found at the git.gitter.space address listed in the announcement. nostr:nprofile1qqsf4qmhne6ssp2kcetdf4qc6q4y6lkmu2y2970xm545s7v7ey63snqpz9mhxue69uhkymmnw3ezuumgdacz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqsuamnwvaz7tmwdaejumr0dshs7tcy97?

Happy birthday to me. This stout is absolutely delicious. Nostr, I wish you were here celebrating with me. 💜🫂🤙🏻

Wow!! #gittr is looking real strong.

Weird. I don't recall creating the project Tibes under my account.

Seems that the bunker logging in gittr is not working well 😅

Its on the issues page. Basically just a "calendar" feature like meetstr has. That way I can make a calendar for a group and then send them direct to that link. The issue on github has a link to what I mean because it's hard to describe since it's meta.

Plektos is the meetup killer, don't know how I only found it recently.

Can someone explain what nostr:nprofile1qqs27vuc5hrf8q0d42ygzqywx99axr54azewn2lkggctys7n709mkcqprpmhxue69uhkzapwdehhxarjwahhy6mn9e3k7mf0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcvsunp8 is and how it works?

nostr wins if it stops trying to be a twitter clone and starts being the invisible layer underneath apps you actually want to use. like bitchat for location-based messaging, diVine for entertainment, whitenoise for private messaging, zap.stream for streaming, shakespeare for vibe coding, etc.

it wins by unbundling into 50 different apps that all talk to each other, rather than one giant app/corp that traps you. it's all about the ecosystem.

It's happening, I'm adding promenade signing to flotilla just so people can paste their nsec. Signers are just not there yet.

oh yeah, this is often called "composability" these days, and is the data model strategy used in Go with anonymous struct fields that overload a type with methods from multiple separate other types or interfaces.

Composition > Inheritance

it is related to the principles of Domain Driven Design also, which is about analysing your code to architect it as composable layers.

solves SO MANY BUGS just by applying this analysis to a codebase. almost half the time, i think, the worst bugs come from breaching interfaces and not using encapsulation, creating hidden bindings between two types that often you miss because you didn't look to see. haha.

The result is very reliable & fast so i dont really get the problem here neither with complexity and sharing snippets on that nor PRing progress. Ive contributed to much older code than 2 years before..

Ist faster and working great, not sure what the problem is

Yes, thats what i am saying. Its about discoverability for me.

See nothing wrong in PRing changes so its up to date. Lost and left repos are a problem when ppl want to contribute.

complexity is a goldilocks thing. too simple and too complex are both bad. finding the balance is required. also, often times complexity can be tamed by subdividing the protocol or code into separate components that layer, this is the Unix maxim of "make it do one thing, and do it well" applied to architecture

I'm a bit confused. Are you are saying the extra complexity of having lots of different ways of doing the same thing is OK? And that you made a PR to a project that has only 1 commit posted 2 years ago.