Are you NICE to your LLM?? https://arxiv.org/abs/2402.14531

The timescales are short but it feels like a lifetime when you’re using it and wonder when the next update will arrive 😆

It's kinda funny to me how short the timescales are that Anthropic is working on. For instance, on their site I read, "since June of 2024, Claude has been the leading LLM for coding." June of 2024 was basically yesterday. Anthropic wants Claude to provide "breakthrough solutions" by 2027. I wonder if we won't become myopic, with everything happening on such short timescales.

Christmas in February!

Wake up babe, new Claude just dropped. https://www.anthropic.com/news/claude-3-7-sonnet

This is not devs fault though, it’s the nature of this protocol. nostr:note1gx5k88dj4mq8nyxu20wzv7pyuly5up8z2nrttxjp876h50k3mkhqukwhx2

slow day on Nostr, or the new norm? 🤔

The same principle applies to mainstream topics on Nostr, tbh.

This is a change from previous versions, yes. I will try a fresh clone to see if that helps. My configuration may have gotten borked.

Who woulda thunk that all i needed to do was to add a 32'' monitor and then like magic... no more mess 🤗

That's past my bedtime 😅

I'll check my settings!

Zapvertising zaps never seem to make it into my Minibits wallet. Where do the sats go? 🤔

@ReplyGuy you a hoe

People are better-looking, now, than when I was a kid, but you can't tell because so many of them got really really fat.

nostr:nprofile1qqsd7ele5ljpzft5tjl84naae5pkj9uqcepa77adwr6ayyy0948uyqqpz9mhxue69uhkummnw3ezuamfdejj7qtxwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tmwwp6kyvtdv9hxcmnxd3uh57t2dpnkswfhxp6rsmtddenhyerew33hqvm2wfkkzcfkxe6nsdpkvankwdm5xgcxxem3w9m8jm3ew3hr7cnjdaskgcmpwd6r6arjw4jsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsavanjs do you have prototypes of your social onboarding we can play with? I've got a couple of friends who might be interested if I gave them an easy on ramp.

Finally got my debugger setup, on my new computer, and I immediately rediscovered why using a debugger is a programming superpower.

What about also allowing 30041 alone? I guess that already forces you to have a structure selection interface.

That would be easier to implement.

Okay, so hard-code everything to 30040/41 for the alpha release?

In the writing of an article, i think we should focus on the 30040/41 pair. Keeps it simple, the idea being 30040/41 is about as basic an object you can create for 'knowledge'. Blogs, docs, etc. can always be broken down into grouped 30041. In the case for composing collages or grouping related ideas from different events, that's when we can think about what the process will be.

Does it necessarily have to be a 30040/41 combination? They will eventually be able to publish wiki pages, too right, or a 30040 that contains a wiki page or another 30040. So they need to be able to define which kind each section should have, with 30040/30041 simply the default. I'm just thinking that it might make sense to go full modularity in the design, from the start. Also probably need to put a help text above the editing field, that explains where you will define a split. Like, what happens with the content in the preamble? Does it go into a summary tag or does it get a preamble 30041? Is the header where you type in stuff that will end up in optional tags? Which tags will you process and how do they need to type them in? Can they see that information in processed form in the preview?

I'd like some design feedback on Alexandria. I'm working on an article editor feature. A screenshot of an early draft is below. The overall goal is to be able to type AsciiDoc-formatted text, preview it in rich text form as it would appear in the Alexandria reader view, then publish it as a cluster of kind 30040 and 30041 events. My thinking is to break the content down into sections. The content of each section will be published as a kind 30041 note. Each section will be indexed by a kind 30040 note, which will reference the content of the section as a kind 30041 and any subsections as 30040 notes. Question: How would you like to preview your published events? I see two options: 1. There are two preview steps: one is a "quick preview" you can see with a click while editing. It doesn't break the content down into 30040 and 30041 events, but it shows you what the nicely-formatted AsciiDoc content would look like. The second preview steps shows the content as it would appear in reader view, after it's been broken down into its constituent 30040 and 30041 events. This preview would have a confirmation dialogue that lets you approve or cancel publishing the events. 2. There's just one preview, and clicking the preview button while editing shows you the content as it would appear in reader view, broken down into 30040 and 30041 events. There would be no separate screen with a confirmation dialogue, and a publish button on the editor page would publish the events. I'd love to hear people's thoughts! #asknostr #alexandria #gitcitadel #nostrdev #nostrdesign

The UX rule of thumb I've heard is "Don't punish the user before they've performed an action." So best practice is to make optional fields optionally visible, and not to show the red stars and such oj mandatory fields unless the user tries to submit the form without filling out all the necessary fields.

Title field is mandatory. Author is optional, even though it'll probably be added for books. Not really clear from the interface. Maybe add a red star next to "Title", or something, or demote author into the Asciidoc header.

I would just do the publish button, tho. No fourth dialog.

LOL changed my mind, after Reading what nostr:npub1494rtg3ygq4cqawymgs0q3mcj6hucvu4kmadv03s5ey2sg32df5shtzmp0 said. Want three steps, like a little wizard, so that they can follow what the client is "doing". 1) Pretty asciidoc preview 2) Kind structure selection dialog 3) Split view with disabled kind labels

So, I'd go for #3: have a pre-selection dialog for the kind pattern (currently 30040/30041s or each kind alone), and have a small drop-down label, above or next to each section, where they can adjust the kind, but that is currently disabled and read-only. (They'll eventually need to be able to add/remove sections, as well, but that's future music.) 30041 alone because they may already have a 30040 and just want to add something new to the list. 30040 alone because they may just want to create an index for things that already exist.

Wow, thats alot of good info, thank you. I'm starting to think it would just be much less complicated to switch to minibits or similar, and not use alby. I gave it a shot because the email they sent me said that custodial alby wallets would be deprecated eventually. Could i still do one tap zaps with minibits?

I've done the same thing: self-hosted on my laptop. The thing is, a Lightning node has to be on to send and receive zaps. Laptops aren't the best for that because they're designed to be easily shut off and carried around. My solution is to have the Alby Hub on my laptop as my personal "bank," and use a separate wallet (Minibits, in my case), to send and receive zaps on Nostr. So I can refill my Minibits wallet from the Alby Hub, then turn off the hub. Or vice versa I can send sats to the hub, then turn it back off. So most of my sats are in the hub and self-custodied, but I'm not using it as my "daily driver." All that being said, to get the hub working with Nostr zaps, you'd have to set it up with Nostr Wallet Connect. Without NWC, it should be able to receive sats over your Alby address as long as the hub has a channel open. However, I think you'd have to manually approve zaps on the hub, unless you connect the app from which you're sending zaps with NWC. And then it would work as long as you laptop is online. I'm still learning this stuff myself, but that's what I've gleaned so far. Happy to chat about it more, if it will help!

I opted for self hosted, on my laptop. I was able to open a channel, but i could not seem to do zaps properly. Maybe a connection issue with node and my lightning address? Although it appeared that it connected. I'm not super techy, so probably just error on my part.

What issues have you been seeing? And what Alby Hub setup are you using? Is it self-hosted?

Well i guess i screwed something up, dammit. I had to switch back over to legacy alby. I will revisit this later. Thanks all of you for helping me test. nostr:nevent1qqsz03lfply6yk8n0pufvtn4hd93gyza8xrjvuy5q8gfqfgu36pre4cpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsgm8ftw7fsae2wc0jxltmhfhwsg8dmfe92xkk50sp93p9zsmwkt7srqsqqqqqpzt79kh

I've been ill or injured for a few weeks now, and it has me feeling pensive. Pensive is an underrated word.