:H::e::n::k::y:!!'s avatar
:H::e::n::k::y:!!
Henk.Tech
npub1600y...889v
Sysadmin | AI Entertainment Enthousiast | Game Server Operator | Liberal (as in Liberty) Nationalist (each country has a right to be sovereign and should not impose their will on other countries) - There is only a paradox if you don't admit it See me post with a really long address on mastodon? That's a bridge. My real profile is : https://ditto.pub/@henk.tech My webhost blocks some requests behind proof of work, if my NIP-05 errors for you then you can verify it manually. I unfortunately can't disable this.
Day 3 of toying around with Mixstr, this day I am doing it on the cheap. No more Kimi for most of it and avoided Claude entirely. The big stuff was good to get it off the ground along with MKStack that shakespear used in the background, but for maintaining it I don't need them for a lot of things. Locally I got my 3090's hacking away at the code and only if they fail at something important do I need to borrow kimi a bit. I noticed for example that if you clicked on a hashtag it would break since there was no page dedicated to the hashtag, implementing hashtag pages was simple for 27B and it basically one shot them. It also oneshot the notification change where notifications now get dismissed persistently across Mixstr sessions. And it oneshot a fix where people you blocked no longer appear in your notifications and comments. All that stuff for free from a nice local model powered by KoboldCpp :D But I also noticed Mixstr was missing a LOT of profile events. That one was tricky to fix and also very important, so for that one I used some of my remaining credits for Kimi. Even then it was a good long back and forth before a proper solution was found. But now I can be sure that profiles are complete, not initially since its still Nostr but over time as it keeps verifying and loading. With 27B being so useful at many of this I can make it do things I think are simple enough for it but that are not important enough for me to want to spend credits.
#asknostr I made a proof of concept Nostr web client and I am curious if there is any interest in this. Its made with @Alex Gleason 's shakespeare and that adds up quick so certain bits are placeholders. Right now I recommend testing it with alt accounts. Many things are missing such as remote signers, zaps (I don't know if as a newer dev its a smart idea for me to add those myself with AI) and the login flow isn't what i'd like yet. But, this is a unique client and I hope this proof of concept is appealing, here is the idea: - Its a very basic client by default, just a follow feed, search and DM's nothing else. - It has highly customized lists for the side panel, you can make your own ones, name it whatever you want, and then mix the sources together that you want. If you want one that does a keyword search, adds a few hashtags and an RSS feed on top? You can! Want a relays feed? You can! Maybe you want two relay feeds combined? You can! - Lists use NIP-44 so they are hopefully private (Correct me if this is not working in practise, since the idea is that you can follow people privately). - If its worth liking then it is worth spreading, the idea is that if you like or reply to something it automatically rebroadcasts the event to your own relays to help spread the word and for people who see that you just interacted with something to be able to see what that something is. - You can mark DM's as deleted, nostr doesn't support this but at least they are hidden and not cluttering your DM inbox. Currently only NIP-17 is supported. So far I spent $60 on the idea and it should be in a place where even though it may be rough or experimental I think the core idea comes across. You can try it at https://mixstr.pages.dev for yourself and let me know. Is this worth continuing? If so, would you be willing to chip in with PR's or help me fund the vibe coding?
The best thing about vibecoding as a user with strong opinions about how nostr should work is that you can tell it to do those ideas. Ideas such as auto rebroadcasting events when you like them. The worst thing about vibe coding is that the AI isn't you and does things that you are strongly opinionated about you'd never have done. And then you spend credits on fixing it.
Vibe coding nostr apps is fun, but will it actually work before my credits run out?
@Alex Gleason shakespeare is a work of static page art! But it desperately needs some AI API controls so I can prevent it from looping. Me being able to set the context , max output, epetition penalty, etc. Now I have to rely on server side overrides.
Relay ops, I have made a tool (which out of fear of it being a nuke if its public I won't release yet) that forwards all events it comes across to relays I define as the destination. Any of you fancy being the target of this test? I am curious if you notice a difference if the script targets you as a destination in terms of new posts on your relay. If you are super big it probably won't matter, but i'd love to test this on something that isn't my local strfry. It wont do historic events and its all signed by the original authors so no ban evasions. But before I blast this on a relay I wanted to #asknostr 's ops first as I don't know who likes a nice cozy quiet relay and who wants to be the next nostr band for a limited time.