#DM on #smesh is now a thing.

Smesh

A user-friendly Nostr client for exploring relay feeds

foar all yoar dmmy goodnuss

ꜰreeᴅom. ɪn ᴘʟaɪn sɪɢʜᴛ.

if you want connectivity while in transit with no nonsense, i can definitely recommend getting a pixel, installing grapheneOS and using yesim.app for data #esim that just work all over the place. works well in eu anyway. the local cheap options from hrvatska telekom (t-mobile) are kinda crap. not sure which provider yesim uses but it works better on LTE than the HT 5g where i am, probably to do with being in a bit of a dead spot. i think they use A1 as their provider, who are obviously behind on the 5G rollout. around the edges, 4g works better, it's still 2.4ghz or so and slower but i get 5gbit symmetric on LTE where on 5g i get like 700kbit/4kbit. so overall, it's an upgrade for me. roaming on portuguese vodafone was adequate but i want to stop paying them and this esim works much better here.

new proverb just dropped: ɢɪᴠᴇ ᴛʜᴇᴍ ʙʀᴇᴀᴅ ᴀɴᴅ ᴄɪʀᴄᴜꜱᴇꜱ ᴀɴᴅ ᴛʜᴇʏ ᴡɪʟʟ ʜᴀɴɢ ᴛʜᴇᴍꜱᴇʟᴠᴇꜱ View quoted note →

starting to get settled into the new

Smesh

A user-friendly Nostr client for exploring relay feeds

app - still lots of work to do to get messaging working nice but it kinda works now.

i think

Smesh

A user-friendly Nostr client for exploring relay feeds

now has fully working dms, probably a little wonky and slow yet but i think it's almost usable now.

i think

Smesh

A user-friendly Nostr client for exploring relay feeds

now has fully working dms, probably a little wonky and slow yet but i think it's almost usable now.

#smesh has very slow DMs now, they sorta work, sorta not, much work to do on them yet

No longer need to run amethyst on my phone, I has https://smelt.mleku.dev Will have a native signer soon too. It's mostly done writing, now for debugs and tweaks.

announcing wss://archive.orly.dev/ - a relay fed by an aggregator that is eating the entire nostrwebs. no idea how long it will take to get everything but then after that, it will stay up to date and be a solution for "note not found" by adding it to your client relay list.

oh yeah. wss://relay.orly.dev/ is now running on a single core 6gb ARM as the only service on the VPS. should be a lot more reliable running now, and the web address

ORLY?

lets you log in and access the UI. only my follows can actually do very much. bunker signer with background service coming soon, integrates with

Smesh

A user-friendly Nostr client for exploring relay feeds

client, a jumble fork, using Cashu Access Tokens to get anonymous access to the relay for bunkker rendezvous with the signer in your client. both install as PWAs so this means nsec isolation (safe nsecs) without any nonsense on mobile. and when more clients support this protocol, we can move auth to the http layer of the stack using cashu tokens issued by relays to regulate access without making identifiable connections between traffic and identities.

new client just dropped

Smesh

A user-friendly Nostr client for exploring relay feeds

forked from jumble, cleaned up a lot. has initial support for CAT but not fully working yet. i'm going to put a signer into the orly web ui console, simple place to put it and no rigmerole with forking an android app. it will be a signer on mobile as well as access to your relay ui

git.mleku.dev

next.orly.dev/docs/NIP-XX-CASHU-ACCESS-TOKENS.md at main

next.orly.dev

a cashu cryptography access control system that preserves anonymity completely if combined with use of tor.

ʀᴜɴɴɪɴɢ ᴍʏ ꜰᴏʀᴋ ᴏꜰ ᴊᴜᴍʙʟᴇ ɴᴏᴡ, ᴀʟʀᴇᴀᴅʏ ʟᴏᴀᴅꜱ ᴏꜰ ʙᴇᴛᴛᴇʀ ᴛʜɪɴɢꜱ - all settings except for single/double pane are synced across logins to the same npuub - ugly bottom bar is replaced with a side drawer of the full labeled menu in mobile phone sizes (768px and smaller). i am building an auth extension that uses time-limited cashu tokens issued by the relay in the web UI interface, which can be accessed using an extension signer on desktop. this shows a qr code of the token which the client can then scan and store alongside the standard bunker strings. it puts this token in a http header, and the relay recognises this and allows the user to connect to do nip-46 messages (mainly, kind restricted). it will be build so it can be used for any context, so it could also replace auth completely, and it's cashu, because all the cool kids like cashu. cashu vouchers. i'm sure i'm not the first to talk about it on nostr but i was so close to figuring it out back in 2013, i just didn't bump into chaum. by using standard cashu format and algos, i leverage what exists, and create an access token that does not identify the user, only the validity of the token. this might actually be a new nip altogether, one that i may not even have much trouble getting added. only caveat is that it probably needs a token request protocol as well. i was just using nip-98 for that. well, yes, that is fine, has to be there, so i'm making a spec NIP-XX Cashu Access Tokens, the token issue protocol, and the http header auth protocol. this is an actually useful and non-cumbersome form of cashu cryptography usage. it could be used for anything, i'm just making it into an extensible, programmable firewall that allows time based service acccess, which is the simplest and easiest to plan with. the pay part is outside of the domain of the access control, and time limited tokens are the standard for a reason, and because of blinded signatures, this works purely as an attestation from the relay that the user has valid access granted, without identifying other than the time window of the subscription. this is to allow any others, i guess it also needs a metadata/configuration. for now just starting with something simple and if it seems like it needs more, i will add, only add, never take away.

ɪ am ᴅesɪɢnɪnɢ a casʜu ᴛoᴋen ʙaseᴅ auᴛʜ ᴛo aʟʟow reᴛaɪnɪnɢ ᴛʜe 𝔞𝔫𝔬𝔫𝔶𝔪𝔬𝔲𝔰 nɪᴘ-46 ʙunᴋer ᴛraꜰꜰɪc, ʙuᴛ wɪᴛʜouᴛ ᴛʜe sᴘam vuʟneraʙɪʟɪᴛʏ. ɪ suᴘᴘose anʏ reʟaʏ couʟᴅ ɪmᴘʟemenᴛ ɪᴛ ʙuᴛ ORLY? wɪʟʟ ʜave ɪᴛ soon, as ɪ am usɪnɢ ɪᴛ ᴛo enaʙʟe usɪnɢ ᴛʜe reʟaʏ wɪᴛʜ nɪᴘ-46 wɪᴛʜouᴛ ʟeᴛᴛɪnɢ everʏone use ɪᴛ, nɪᴘ-46 ɪs ʙuɪʟᴛ on a ᴘremɪse oꜰ reʟaʏs wɪᴛʜ ɢɪɢaʙɪᴛs oꜰ ᴛraꜰꜰɪc caᴘacɪᴛʏ, ᴛʜɪs oʙvɪousʟʏ ɪs unsuɪᴛaʙʟe ꜰor a ʜome-ʜosᴛeᴅ connecᴛɪon on 100mʙɪᴛ or ʟess. ᴀɴᴅ ᴛᴏ ᴜꜱᴇ ᴄᴀꜱʜᴜ ᴀꜱ ᴀ ɴᴏɴ-ᴍᴏɴᴇᴛᴀʀʏ - ꜱᴘᴇᴄɪꜰɪᴄᴀʟʟʏ ʟɪᴋᴇ ᴀ ᴢʜᴇᴛᴏɴ ᴏʀ ᴄᴏᴜᴘᴏɴ. ɪᴛ ɢɪᴠᴇꜱ ᴍᴇ ɪᴅᴇᴀꜱ, ɪꜰ ᴛʜɪꜱ ᴄʀʏᴘᴛᴏɢʀᴀᴘʜʏ ɪꜱ ɴᴏᴛ ᴇxᴄᴇꜱꜱɪᴠᴇʟʏ ᴄᴏᴍᴘᴜᴛᴇ ʜᴇᴀᴠʏ, ɪɴ ɢᴇɴᴇʀᴀʟ, ᴡʜɪᴄʜ ɪ ᴄᴀɴ ᴛʜᴇɴ ꜱᴡᴀᴘ ᴏᴜᴛ ᴜꜱɪɴɢ ʟɪɢʜᴛɴɪɴɢ ᴋᴇʏꜱᴇɴᴅꜱ ᴏɴ ɪɴᴅʀᴀ ᴀɴᴅ ᴜꜱᴇ ᴛʜɪꜱ ᴛᴏ ʙᴜʏ ꜱᴇꜱꜱɪᴏɴ ᴛᴏᴋᴇɴꜱ ᴡɪᴛʜ ᴄʟɪᴇɴᴛꜱ - ᴜꜱɪɴɢ ᴋᴇʏꜱᴇɴᴅꜱ. ɪ ʜᴀᴅ ᴍᴀᴅᴇ ᴀʟʟ ᴛʜᴇ ᴀᴄᴄᴏᴜɴᴛɪɴɢ ꜰᴏʀ ᴛʜᴀᴛ ꜱʏꜱᴛᴇᴍ ʙᴀꜱᴇᴅ ᴏɴ ᴅᴀᴛᴀ ᴀᴍᴏᴜɴᴛ ʙᴜᴛ ᴛɪᴍᴇ ʙᴀꜱᴇᴅ ꜱᴜʙꜱᴄʀɪᴘᴛɪᴏɴꜱ ᴀʀᴇ ᴍᴜᴄʜ ꜱɪᴍᴘʟᴇʀ ᴀɴᴅ ᴏɴʟʏ ɴᴇᴇᴅ ᴏɴᴇ ᴘᴇʀ ɴᴏᴅᴇ.