๐š๐šข๐šŠ๐š—'s avatar
๐š๐šข๐šŠ๐š—
ryan@spatia-arcana.com
npub1m64h...uaks
Play Flappy Nostrich @ flappy-nostrich.vercel.app/ Est. 776032 ๐Ÿ’œ๐Ÿซ‚๐Ÿค™
๐š๐šข๐šŠ๐š—'s avatar
Ryan 1 month ago
CKY - 96 Quite Bitter Beings #tunestr
๐š๐šข๐šŠ๐š—'s avatar
Ryan 1 month ago
Do crazy things. See what happens. #FAFO
๐š๐šข๐šŠ๐š—'s avatar
Ryan 1 month ago
HLS & Nostr My initial testing of using blossom as a backend for storing video segments & playlists has been successful, testing single resolution streams packaged as fMP4 segments. The next step will be variable bandwidth streams so video can be flexible depending on the users connection speed. FFmpeg makes this easy by creating the video segments & playlists, only requiring me to map the Blossom hash to the playlist entries after they are uploaded. Future plans: - a native Android app, using @โšก Dee Kay โšก LCe library for compression & segmenting. Likely best for shorter videos due to hardware constraints. - a command line app depending on ffmpeg & nak, useful for larger uploads with access to more powerful hardware & GPU acceleration. I would like input from blossom server providers. With the segmenting aspect of this it will sidestep file size upload limits. I wonder though if the possible bandwidth savings would make this worth it, vs users uploading huge MP4 files and serving them with no optimization?
โ†‘