Avatar
Ingwie Phoenix (aka. birb)
5e336907a3dda5cd58f11d162d8a4c9388f9cfb2f8dc4b469c8151e379c63bc9
[ENG/GER] NOT a bitcoiner/stacker/maxi. I am here to have a damn good time! Rabbithole conniseur; I enjoy random stuff. :D Ex-Furry, (close to) blind, hobby developer/sysadmin, waifu enjoyer, long hair fetish (#hairjob). I sometimes talk about NSFW stuff; because fucking is fun =) (DMs always open.)

Sometimes, I really /am/ a birdbrain: too, easily, exciteable. ovo

Meanwhile:

(To be fair, the disk labeled "Daten" is old, crappy, and has a lot of SMART failures reported... so it's usually only there to act as an intermediary for transfers, temp VM storage and the like. But it's still functional!)

nostr:note1vr4nu0zqwldqd8mtfqtnx8ngwhcgg3nfz9spj03mur2ugu87zl2szm4v40

Iunno! Just kinda shooting into the blue o.o

But, I would expect that work-balancing between nodes would improve efficiency and throughput. If Nostr grows, so do need the relays. They are the sole backbone of Nostr - the better (and faster) the relays, the smoother the Nostr experience becomes overall. By leveraging a cluster, work can be split and distributed, improving compute and resource usage. At least, in theory.

As for the DB, I think that kinda depends? AFAIK Discord uses a Cassandra Cluster precisely because of that - to improve access to and from the DB - so it acts monolithic, but really isn't. So they probably use replication and clustering within that Cassandra cluster as well.

But, that said, I am just spewing random thoughts into the world. Ya never know! Might strike gold. =)

This looks soooooo good. It's what I had hoped of NATS to be, but way better!

https://github.com/goware/disque

I am somewhat itching to implement a relay-cluster ontop of this.

https://github.com/antirez/disque

Imagine: some servers just listening, others just constantly running generic spam filters, and some working to store and optimize, perhaps get stats or something... o.o

This feels so goddamn nerdy.

I want to put this on ALL my systems now XD

https://github.com/MHNightCat/superfile

Drop me anywhere into Japan and I am happy to explore my way around start to finish. Just leave me my phone and a charger, perhaps my ID. Everything else I'll attempt to manage. ^-^

Personally, diversification is what I feel like is still missing. The coinage here is ultra strong - makes sense, considering how and why this started, really. But the prejudice towards crypto is /real/ - and a real problem also.

The current audience for Nostr is techbros and coiners. Unless we find a way to diversify and slightly de-niche our platform, it will stagnate.

The past months, a lot of focus was put on wallets - and I get it, Lightning was one of the core parts of Nostr and the improvements there - such as with zap splitting, the whole system of zap.stream and whatnot - are amazing. But wallet's aren't "cool", yknow? They're "neat".

Also, missed opportunities.

- Reddit: Nostr communitys hardly work. If we had implemented a better system than kbin/lemmy, we could've literally exploded.

- Yuzu: The decentralized nature of Nostr would've been a great way to let the Yuzu fork maintainers stay under the covers and keep delivering their software. They don't know how to do CI/CD on a node only accessible through tor; but we could have helped. I tried my part on Reddit to invite them, including via DMs, but I was usually ghosted. We need to be "louder". Not obnoxious, but able to be heared.

I love Nostr and I definitively intend to stay and build on it - but right now, I don't see any of my artist friends joining (peeps designing their OCs, furry artists or just general painters that I know) or any reason why someone trying to go away from Twitter to not just join Threads or BSky. Threads can talk to some Mastodon instances now and BSky lives off of lofty promises - but their client works, is /ridiculously/ fast (click "Follow" on BSky, Snort and Primal - you'll see what I mean) and currently has no real stigma to speak of. Nostr is full of coiners. People are wary of coiners. Sucks and sad but... yeah, its a thing. :/

I realize this is far more than "just my two cents" but... eh, this is why I nostr; I can just rant for ages! :D

Kubernetes is a clusterfuck.

So, it's a c9k =)

I swear, the amount of github issues i have produced since switching to k3s is actually a little insane...

Man, if docker-compose could utilize swarm, this'd actually not be a problem lol. I swear, docker-compose + swarm would legit be a great strat to just have throwaway-able deployments without the k8s/cloudpeople-bullshit. But, hey, i'm far too deep into this now. LFG? O.o...

Well fuck. Keycloak actually... works. And does what I want. And, what... o.o fuck. xD

Well, last problem! When this is solved, I have my auth shit down.

https://github.com/oauth2-proxy/oauth2-proxy/issues/2639

Fucking finally. Keycloak works. x.x

all I hear is a wet fart. -.-

Podcast time with LTT WAN Show! ^-^

Its sunny and warm outside. So... perfect!

OIDC but Nostr. o.o

I want that.