Running @FIPS

FIPS Dashboard

No clue what I'm doing but I'll learn

Testing, please ignore. and yes I'm sharing a localhost URL, your client should know how to deal with it blossom:a94b7005b2f6256e0335b0de05dd6a9ce771c1ac27018a9de2d169538710962d.jpg?xs=blossom.nogood.studio&as=55f04590674f3648f4cdc9dc8ce32da2a282074cd0b020596ee033d12d385185

And now I managed to make an HTTP request that goes from: my laptop -> LAN -> my PC -> UDP -> FIPS test gateway -> other nostrich's server. Its not a direct connection, the HTTP request is getting routed through two other computers. This is crazy... 🤯 Unfortunately the BLE was too slow to support more than pings so View quoted note →

@FIPS blowing my mind right now. I'm pinging my offline laptop over BLE

ffs where is the merge request button on gitlab... I cant make a contribution to ditto because gitlabs UI has more drop down menus than excel

I like that when I login to ditto it only asks to decrypt 3 nostr events and not my whole DM history :) Its another client that's usable without auto-approve

Cleaning out my web bookmarks and I had so many old links to linux articles to remember how to set stuff up on a server... never going to need that again with AI, even local models can answer those questions now

Shilling my own PRs but I want some feedback I've got five new PRs that cleanup some stuff and introduce some new things in blossom. no breaking changes but maybe some more complexity for clients. Either way if you have ideas head over to

GitHub

Pull requests · hzrd149/blossom

Blobs stored simply on mediaservers. Contribute to hzrd149/blossom development by creating an account on GitHub.

and add them or open a PR

Also the /upload endpoint should really be a POST and not a PUT... I should have read the HTTP spec first I guess View quoted note →

Reading over section 9.6 of RFC 2616 I'm not sure why I didn't make the upload endpoint on blossom servers a `PUT /<sha256>` instead of a `PUT /upload`. it would make a lot more sense... 🤔

RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1

v6.1.0 of

JSR

@hzrd149/blossom-server - JSR

@hzrd149/blossom-server on JSR

is published. No breaking changes but it has a lot more specific HTTP status codes based on

GitHub

Add specific status codes to endpoints for clarity by hzrd149 · Pull Request #98 · hzrd149/blossom

The goal of this PR is to get specific about the HTTP codes that can be returned from all endpoints. this should help with interoperability between...

Appreciate feedback if anyone is running it, and feedback on the PR. Id like to get stricter HTTP status codes added to the Blossom spec so we can have better interoperability between servers.

Great episode, and I love to hear what @Sirius is working on. the hashtree stuff sounds like the second phase of blossom I've been waiting for, real chunked files and folders on blossom... Although now I have a lot of homework to do before I can be sure. View quoted note →

Getting nostalgic while playing with older versions of #noStrudel 2 years of noStrudel versions are runnable as nsites https://2tlb607yn9ai420jf20b3ge69so4zeoi0bmj6iri8u8n067hmgsites.nsite.lol/

I also update noStrudels npub-home site to show historical versions :D https://2tlb607yn9ai420jf20b3ge69so4zeoi0bmj6iri8u8n067hmgsites.nsite.lol/ View quoted note →

Went back and compiled a bunch of the old #noStrudel versions and published them as nsite snapshots to test out my ideas in

GitHub

Add aggregate hash and pinned sites to NIP-5A by hzrd149 · Pull Request #2287 · nostr-protocol/nips

The PR adds an optional x tag, a new 5128 pinned site manifest kind, and the upstream &quot;app&quot; tags to NIP-5A The goal with the aggregate ha...

So if you enjoyed old versions of noStrudel you can find them here for now. although be warned, most of them default to loading global which has a lot of spam...

npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez.nsite.lol — site status

Still love the mini nsite list app that @sandwich created that I stole. super easy to find all my nsites I've deployed https://0ygl461f4ecz5thkn8eksa36nepjpij86s83ti8yzokopd3ag5nsites.nsite.lol/

Very happy with

kitty

kitty

If you live in the terminal, kitty is made for YOU! The fast, feature-rich, GPU based terminal emulator. Fast Uses GPU and SIMD vector CPU instruct...

Tab and windowing shortcuts are easy to learn and it lets me resize the panels using the mouse 😁

This will also help agents write clients and servers for blossom. The more I've been working with agents the more I'm realizing that trying to publish libraries and package to help them work with a spec or protocol is the wrong way. Its better to make the protocol very explicit and detailed so they can just implement the part they need. hopefully with less code then pulling in a full library. View quoted note →

Taking full advantage of HTTP status codes

GitHub

Add specific status codes to endpoints for clarity by hzrd149 · Pull Request #98 · hzrd149/blossom

The goal of this PR is to get specific about the HTTP codes that can be returned from all endpoints. this should help with interoperability between...

The idea is to define all the common HTTP status codes and how they relate to blossom endpoints. This has kind of been an unspoken rule for too long that clients and servers should follow HTTP but its much better to actually define it in the blossom spec. #asknostr I would appropriate lots of feedback on this since its a big change. although its not a breaking change

@Sync you need to include some kind of git link or something is your profile. I cant find your source code anywhere....