I remember having tea with a Turkish man and having him tell me with a straight face: "I'm not having any children with this inflation and economy. I just won't."

That cuts deep.

Ghost in the shell vibes

Might be of your interest @kr.

@k00b, I don't know if you are a polymath, but your content consumption surely looks like one's.

I follow you, thanks.

It makes me wonder how coolio would it be to have a kind that is not "follow" but "trust". So that we could truly communicate publicly "I trust this guy".

I think it could the foundation of very, very interesting stuff.

I think the issue might be my understanding of what we mean by "trust" in this context.

Just playing stupid here, how would you describe "trusting" a key?

Either gnucash or beancount.

How do we avoid US dollars funding terrorism and cartels?

How do we avoid terrorism and cartels using physics? Or English?

It's been long since the last time I saw someone fishing love for Hitler's art.

Boiling frog.

Spaniards have this fun one. They say: "With patience and saliva, the elephant put his dick inside the ant".

I think your reasoning is fine, but you're lacking the awareness that there's a lot of people that don't have access to credit with such conditions.

I get your analytics approach regarding materialized views + metabase. That makes sense.

Knowing that's what you are using I think you could appreciate some of the advantages of the approach I'm proposing. For instance, I'm kind of guessing you might be irritated by the fact that with Metabase is hard to version control and build with regular git ways of working (e.g. PR flows). Or not having clear dependency mapping regarding which dashboards rely on which tables of your backend, which means you might blow up some dashboard accidentally when working on the backend database.

Regarding internal/external, I think it could be used for any of the two really.

I could be interested in building hands-on.

What do you think about this:

Should I want to DM you about this, what's the best place?

I'm thinking of something similar to a static site generator. You define s set of queries towards Postgres and visuals with code, check it into git, build it periodically. You can serve the pages publicly or keep them internal. All based on FOSS.

@k00b thinking out loud: could you guys be interested (aka have budget) for developing internal analytics for stacker.news instances as part of the app itself?

Nice! Glad you fixed that.

Don't, you might be able to recover them.

This is their nostr npub: npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv

Theoretically, it can be. And practically, there probably is. There are many situations where this could make sense. For instance, big exchanges that support lightning would probably benefit from having a private LN among themselves to clear transfers between each other without "amateur" nodes in between (and also potentially keeping info private).

But the reality is there is no way to be sure if this is the case. If there's a subnet that is not connected to the "main" net, taking into account all the benefits that would derive from merging into it, it's probably because the operators have a strong incentive to keep things private and away from the public. In which case, we wouldn't know they exist, right?