#[6] π€π hot hot hot
I am pleased to announce another huge feature for Nostrfiles.
https://nostrfiles.dev/recordings/C1NTiH6YbSWBb35tanCr.wav
You can now record and send audio files via Nostr. π€ π
Give it a try at: https://nostrfiles.dev/recorder/
#[2] I am really proud of this new feature - give it a try! π€ π
Cape Town π₯°
Great comment here from raucao:
"I've been thinking about the Nostr architecture and its place on the larger Web a lot recently, reading more of the specs and implementing a simple integration for Kosmos accounts. Since bitcoiners (but at the moment basically noone else) are going to use it anyway, unsolved problems be damned, I think it's worth making things more interoperable and connecting nostr and nostr keys more with federated systems for some easy win-win situations. Also, I'd like to explore using it for chat in Hyperchannel.
One of the main problems I see with the current architecture, especially if or when there is a real influx of millions of people, is that clients cannot really scale in a decentralized way by following more and more relays, which is going to be inevitable when people are distributed across more and more relays. Here's where server-side aggregation (and other functionality) will, if not be outright necessary, at least have the potential to improve performance and UX considerably in my (current) opinion.
So here is also where Sockethub, as a WebSocket-based, encrypted-session-offering, commodity, zero-config, opensource, proxy server could come in!
Let's say I'm on a fairly slow, high-latency connection on my phone and want to fetch someone's profile, or maybe all potential chat messages in a public chatroom, or all timeline updates for the 500 people I follow. I could either go directly to 20 different relays from that connection and wait an excruciatingly long time until I actually (hopefully) get all the data I want, or I could go through a proxy like Sockethub and have it fetch things from all relays it knows it can read from, over a data center connection (or at least a fast home connection).
Sockethub could also filter out unwanted information from pubkeys that don't interest me, or that are on a spam blocklist I follow or whatever, before sending it to my clients, further minimizing traffic and improving performance."
https://github.com/sockethub/sockethub/issues/655#issuecomment-1505434529
Another solution could be that relays are talking to each other and one will set up a relay at home, which will then interact as some kind of proxy to the other Nostr relays, but I as an user don't need to be connected to hundreds of relays, but only one.
But I think such a NIP is not planned or wanted for now.
Great comment here from raucao:
"I've been thinking about the Nostr architecture and its place on the larger Web a lot recently, reading more of the specs and implementing a simple integration for Kosmos accounts. Since bitcoiners (but at the moment basically noone else) are going to use it anyway, unsolved problems be damned, I think it's worth making things more interoperable and connecting nostr and nostr keys more with federated systems for some easy win-win situations. Also, I'd like to explore using it for chat in Hyperchannel.
One of the main problems I see with the current architecture, especially if or when there is a real influx of millions of people, is that clients cannot really scale in a decentralized way by following more and more relays, which is going to be inevitable when people are distributed across more and more relays. Here's where server-side aggregation (and other functionality) will, if not be outright necessary, at least have the potential to improve performance and UX considerably in my (current) opinion.
So here is also where Sockethub, as a WebSocket-based, encrypted-session-offering, commodity, zero-config, opensource, proxy server could come in!
Let's say I'm on a fairly slow, high-latency connection on my phone and want to fetch someone's profile, or maybe all potential chat messages in a public chatroom, or all timeline updates for the 500 people I follow. I could either go directly to 20 different relays from that connection and wait an excruciatingly long time until I actually (hopefully) get all the data I want, or I could go through a proxy like Sockethub and have it fetch things from all relays it knows it can read from, over a data center connection (or at least a fast home connection).
Sockethub could also filter out unwanted information from pubkeys that don't interest me, or that are on a spam blocklist I follow or whatever, before sending it to my clients, further minimizing traffic and improving performance."
https://github.com/sockethub/sockethub/issues/655#issuecomment-1505434529
#[1]
There's nothing like a good afternoon nap π€
Cape Town's Table Mountain, one of the official new 7 Wonder of Nature (left) and Lion's Head / Signal Hill (right).
Such a great adventure visiting both with my loved ones. π

Honeymoon starting soon ππ
Today's #Nostrnoon activity was cleaning Fluffys home π‘
Fluffy the Marimo algae also has two really small babies - hope they will grow as well.


#nn #nostrnoon
At home I am Windows free since years, at work I banned Windows recently. π
Give https://chat.lmsys.org/ from UC Berkeley, CMU, Stanford, and UC San Diego a try.
Blog post: https://vicuna.lmsys.org/
pv βοΈ Inline pics are here π€ Wavlake support upgrade πΆ
You can revisit the 1st of March post and revise whether you managed to quit the birdsite for good this month
#[0]
πΆ Iris updated the https://www.wavlake.com/ embed support for tracks, albums and artists πΆ
π€ If you have issues with Iris these are always worth checking out:
https:/github.com/irislib/faq#try-this-first
https://beta.iris.to (it's always the latest version)
You can report new issues and comment on existing ones: https://tree.taiga.io/project/iristoapp-iris-messenger/issues
Great News - thanks for your developments π€©
Is the Iris.to Android App open source or will it be?
Let's introduce a new Hastag: #Nostrnoon or shortened #nn for lunchtime activities.

Itβs finally here, one of the most common feature requests for the Home Assistant Android Companion app: you can now configure multiple Home Assistant servers.
https://www.home-assistant.io/blog/2023/03/30/android-20233/

#homeassistant #nostrfiles #android
#[1] I am working on #Nostrfiles https://nostrfiles.dev/ which is for just another image uploading service, but I will enhance it with some specific Nostr features soon. π€π½
A Nostrich a Day Keeps the Doctor Away


