Thread

Did you try it?

Try what?

The new feature. I am hearing that I don't know what TikTok is :) so you might like it.

Try what?

I would call it short form portrait video. Not references to reels or tik tok. is there a kind or tag for this? I think this and/or a similar grid like photo view, needs to be intentional from the user, knowing and marking that the content should be consumed this way, else the feed loads in images of screen shots, or videos meant for landscape.

It uses the NIP-94,.95 specs with a filter for images and videos. It doesn't have too much smartness yes, but we will build it up. :)

Try what?

Why are you sending so many "try what" messages?

what clients implement NIP-94,95 besides amethyst?

so it uses the “tags”: users declare it’s a short form portrait video meant for that feed, or it just loads all your following videos (including say, a screen capture sent to a dev of a bug) into that feed? The later seems less than ideal.

Just Snort yet

For now it includes all other posts, but we can easily filter out... This was just a 4hr coding session.. so lots more to come

would definitely suggest looking to instagram and how they handle having multiple types of feeds, with tik tok it’s all just that one kind. I’m for one not apposed to making nostr more friendly towards the demographic who is more comfortable filming themselves for a second than using text.

I think it's not like tik tok concept!

https://filestr.vercel.app/ by @verbiricha also implements NIP-94.

Nip 94 on servers with hashes being verified and nip95 on relays themselves.

Jesus Christ

So, to get the media it's using HTTP and nostr (NIP-95) right now, innit? Are you planning on using also torrent protocol in the future when a magnet link is defined in the kind-1063 event?

Shouldn't NIP-95 events be unsigned? Or perhaps they could be signed with the private key 1 and then everybody could just skip checking signatures there. And also have created_at set to 0, so the same file will always yield the same event ID?

Hum.. but then relays could change the content, right? That is not desirable. The created at idea makes sense for 1065 (the data event). We use 1064 for headers anyway.

Ohh I see together with created at =0 relays could not change content because the id check would fail.. interesting..

It might take a few days.. lots to refine in this new interface yet.

sweet! can't wait to use it 😁

Most of them support NIP94. NIP 95 is less supported, but it's just a matter of time.