Anyone?
#tunestr #music #audio
nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg any idea who would have tips, I feel like it’s a “Home Studio 101” situation 🙏🤙 nostr:note1nv4mufdlxalxd5kh72fqgp0qzcnqpmgzq659qeacmzjnm5wrs38swnjyp0
Music production nerds, I want to set up an audio interface on a different wall than my computer & desk. It’s not a long distance, but it’s longer than any standard USB cord. I probably need 5-6’ of total cable length.
I’ve read it’s a bad idea to just use a USB extension. What do ppl typically do in these scenarios, convert to USB-over-Ethernet? And if so, can I go Ethernet directly into my computer ‘Dock’, or do I need converters on both ends?
#AskNostr
Stay safe brother
Sorry to perpetuate the US political clown show…
But if someone could pls link the absurd video of Kamala same “unburdened by what had been” 1000x, I would appreciate that.
Yes. I’ve been to a few other city’s BitDevs, and all are great with their own flavor. But you can’t top the original.
It may not be “fun”, but nothing beats the o.g. NYC BitDevs
Sure. My note was meant to an oversimplification.
The point is most ppl would never have had a reason to care before Nostr.
#Nostr - it’s #PGP but with a reason to care.
Ok – so Signal is great. Good encryption, etc. Obviously, the main thing that we want to improve there is the centralized coordinator in the middle.
My original proposal was an adaptation of the Signal protocol for Nostr. https://github.com/nostr-protocol/nips/blob/2169fab971591d0b4a450ef08aeb6301c5d2a0da/104.md
But I got lots of feedback on that one that 1) group messaging needs to be first class and 2) multiple device support needs to be first class. Both of these are actually the same thing - supporting groups.
With the signal protocol, the way that the symmetric encryption works, when you're in a group, you're effectively creating a DM to every member of the group, encrypting it separately, and sending it out. Signal makes this feel like less of a big deal because they do some tricks on the server side to make it less heavy for the client.
In the nostr version of the signal protocol, you have no server to do work for you, so your device has to do all that work itself.
With MLS, because it's using a different data structure (binary trees) for managing encryption keys and users in a group, you go from a situation where group scaling is a linear problem (each new user in a group adds the same amount of work for all clients) to a log problem (where each new user in a group adds wayyyy less work for all clients).
There are also other benefits of MLS.
1) it's about to be an internet standard (like TLS, etc) so we conceivably get interoperability with other networks/clients
2) it's built to allow for the use of multiple ciphersuites and the graceful change/upgrade of the ciphersuites over time.
The only drawback is that it's very complex and very new. My work so far on getting MLS to Nostr has been focused on updating dependency libraries to allow for support of schnorr signatures over the secp256k1 curve (what nostr - and bitcoin - uses). I'm very convinced this is the right long-term solution for private messaging on Nostr but it's going to take a bit longer to get it probably ready for implementation.
If you haven't see it already, you can follow along with what I'm doing in my weekly posts. Also, if you're interested in working with me on all this, that'd be awesome.
nostr:naddr1qvzqqqr4gupzq9eemymaerqvwdc25f6ctyuvzx0zt3qld3zp5hf5cmfc2qlrzdh0qqxnzdejxy6rzwf5xvmnwveh25uk9n
Incredibly bullish. Thanks for these details.
Where can I find more about MLS becoming an internet standard?
I wish I enjoyed pot, it gives me anxiety. I do enjoy a mild edible now and then
The #Ethereum roadmap nostr:note135nxwur653c8l0uj8hwvg5a2xr04vl6jtam9z08z0nq9gfxfc5ws0qfyfe
He’s too much of a click bate influencoor… he prob won’t be on Nostr until it’s mainstream