GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing indieweb.org — video 🎥 video is a type of post whose primary content is a video file. Video can consist of recorded movie, animation, titles, typically with audio. It has growing support on the indie web. Video posts are supported by several silos. See also: WhyVideo posts are popular on general silos like Facebook, media silos: Instagram, TikTok, Snapchat, YouTube, Vimeo, Flickr. Vine was an early video silo which became subject to site death. Post videos on your own site instead for all the usual reasons. HowHow to markupUse an h-entry as always, and then an HTML5 Simple example of a video with a single source and a poster image. Note only the video src will be picked up by microformats parsing (currently, there are discussions to do something special with the poster attribute in such cases). <video class="u-video" controls="controls"
src="http://ben.example.com/camcorder.mp4"
poster="http://ben.example.com/camcorder.png">
warning text only for browsers that do not support the video tag
</video>
Alternatively (with separate source element from poster frame, and fallback img tag for browsers that do not support the video tag) this provides a way of mf2 parsing the poster image as a featured image for the video: <video class="u-featured" controls poster="http://ben.example.com/camcorder.png"> <source class="u-video" src="http://ben.example.com/camcorder.mp4"> <img src="http://ben.example.com/camcorder.png" class="u-photo" /> </video> Alternatively multiple formats for the same video can each be provided as a u-video, though it’s unclear if any consuming application would treat these as different formats for the same video, or more likely, different videos in a multi-video post: <video controls="controls"> <source class="u-video" src="http://ben.example.com/camcorder.webm" > <source class="u-video" src="http://ben.example.com/camcorder.mp4" > warning text only for browsers that do not support the video tag </video> How to POSSETo POSSE video, you may want to consider the following destinations:
Bridgy Publish supports POSSEing video posts to Twitter, Facebook, and Flickr. IndieWeb ExamplesThe following indie web sites have video posts. Aaron Parecki
Previously, video support was limited to autolinking mp4 files and animated GIFs since 2013-04-25, e.g.:
The video files themselves appear to have one-off named (undated) permalinks at the same domain, and are only shown/visible/posted within the context of short notes posts. Shane Becker
The video files themselves use datestamped indieweb subdomain URLs of the form:
Ben Roberts
Christian Weiske
Ryan RixRyan Rix (rrix) is able to embed both local video elements and YouTube videos in to Arcology since 2016-4-24. - YouTube videos are provided by adding a `YOUTUBE-URL' to a post - Embedded <video> posts are handled by using Org-mode attachments to add a video file (ogv, mkv, mp4) to the entry. Sebastiaan Andeweg
Barnaby Walters
Past ExamplesThe following examples all worked at the time of publication (and often for years later), yet as of 2022 appear to be broken (either 404 for the permalink, or 404 for the video resource there). If the permalinks are fixed to work again (including showing the videos therein), they can be moved back into the main examples section above. Ben Werdmuller
Each video has a link to the file itself, in case it cannot be played in an embedded state in the browser. Tantek
Temporarily (24h) the markup used an extra "u-photo" in addition to u-video as a hack to test whether Bridgy Publish's photo support would work for POSSEing video to Twitter and Facebook (which did not work at the time, hence Bridgy issues 572 and 573 were filed, and subsequently implemented!). Kyle MahanKara Mahan uses Red Wind to post video since 2015-12-13.
Services ExamplesPestagrampestagram translates instagram video posts into indieweb video posts since 2015-08-18, e.g.
Unmungunmung turns video podcast feeds into h-feed with video posts, e.g.:
Proto video examplesExamples resembling but not quite video posts. Barnaby WaltersBarnaby Walters uses Taproot to post very short silent looping videos in the form of animated GIFs on his site since 2012-12-18, e.g.:
The video files themselves in general appear to have one-off named (undated) permalinks at the same domain, and are only shown/visible/posted within the context of short notes posts. There is no explicit markup to indicate a video post, or that the img gifs are animated. BrainstormingVideo Upload UXA simplest-case Indieweb video system might work like the following:
The size implications of video files created by modern devices (see below) may mean that some video files cannot be uploaded; this is particularly true from mobile connections, or where the user's web server configuration cannot be altered (the default is often very low). It's possible to detect the size of files to be uploaded using Javascript, and perhaps warn the user about files that might be too large. Animated images / GIFsSome animated image files may be considered to have movie-like properties. These can be uploaded like standard images. POSSE Internet ArchiveIt may make sense to POSSE your videos to the Internet Archive. They have a specific service/site for this. See Also: Timestamp linksInspired by Youtube, video posts could have some JS code which parses the content for timestamps, makes them clickable, and moves the playhead to that location when clicked. Ideally, detect and auto-link them server-side to make them linkable (maybe even webmentionable? with video-synced comment display?!), then the client-side code just looks for a ?t= query string parameter and moves the playhead accordingly. Silo ExamplesThe following silos support video posts (with limits)
Alt textSome silos let you add alt text to videos. (This is maybe a bit of a misnomer, since the HTML BlueskyBluesky's video upload UI has a clickable Captions and alt text label under the video. When you click it, you get a text box to enter alt text, and an upload form for uploading a When you publish a post with alt text, it's not rendered in the UI, but it's included in the HTML in a   MastodonMastodon's video upload UI initially shows the text ⚠️ ALT after you upload a video. If you click on it, you can enter alt text and change the thumbnail. Once you publish the post, Mastodon puts your alt text in the    ReferenceVideo formats and compatibilityVideo formats have two components: the codec, which is how the media content is encoded (typically separately for both video & audio), and the wrapper, which can be thought of as a file envelope that the video sits in. By far the most common video format is h.264 MP4 (video encoded using the h.264 codec and saved in an MP4 envelope file). This is also referred to as AVC, or MPEG-4 Part 10. Recording devicesTypically, devices save at a vastly higher bitrate than is strictly necessary, in order to make their cameras seem like they take footage at the best possible quality. This has a number of adverse effects when it comes to actually using that footage: the files are often too big to send, and you can't simply upload a video file as-is and expect users to be able to stream it. A 5 minute iPhone video can easily clock in at 1gb in size. (The iPhone will then tell you you've got to wait for wifi to upload it.) Most consumer devices record h.264 MP4 video; however, a vast array of incompatible video codecs and envelope formats exists, particularly when professional video equipment is taken into consideration. .3gp video is commonly created by older devices. Web supportTo make matters worse, supported video formats vary by browser. While many browsers support h.264 MP4, this is patent encumbered. As a result, some use the WebM envelope format with VP8 video and Vorbis audio streams. Firefox now delegates to the operating system for MP4 support, but there's no guarantee that this exists. Web video often doesn't truly stream: it's simply downloaded progressively to the browser, which can begin playing it before the download is complete. Real streaming servers are available, which can adapt the bitrate of the stream to match the recipient's bandwidth. To truly support HTML5 web video, platforms should think about:
However, uploading a video file from your device and serving it from your web server is often sufficient. If you choose to compress the file further, it's worth considering whether to transcode manually, using one of the many available applications across all platforms, or to integrate an open source encoder like FFMPEG or Handbrake on the server so as to generate friendly streaming versions once your video has been uploaded. If you are accepting videos from third parties, you may wish to consider the legal implications. YouTube, for example, always archives the exact file that was uploaded, even though it serves a transcoded version to visitors. That way it can prove that it was not the originator of any copyright violations. Ben Werdmuller works on latakoo, a service that provides apps to compress the video before upload (making for faster uploads from, eg, mobile devices and shared Internet), but it should be noted that this is a paid service that does not explicitly provide Indieweb support. (It does, however, have an API.) There is also encode.com which compresses video that you host on your own website, they have a paid per usage service, a monthly plan and a free watermarked trial to test their API. - I ([tomasparks]) have had an free account for years. There is certainly scope for an indie video app that records video, modifies it in the app, and uploads it to the location of the user's choice (or even makes it available for the user to download and re-upload). Bit Rate and File SizeWhen transcoding video to prepare it for upload to your personal site, the three parameters which have the largest effects on video quality and file size are codec, size (e.g. 720p, 1080p, etc) and bit rate. In the process of posting this 1:43 video, Starting with a 1080p 50fps 10Mb/s QuickTime Movie file exported from DaVinci Resolve weighing 133MB, here’s how varying the following parameters in Handbrake affected the transcoded video:
Based on these tests, for short (<5min) videos intended to be hosted on personal sites, the following Handbrake/ffmpeg settings are likely a good starting point, resulting in approximately 14MB per minute of 720p video:
FAQOpen realtime videoQ: Are there any non proprietary ways to do realtime video on the web? A: Yes! WebRTC Is an embed a video postQ: Is an iframe embed, like of a YouTube or Vimeo, a video post? A: No. With just an iframe, you have no video file to point to. u-video is for the actual video file, not a script that does something to do something, nor an iframe that loads something to load something. Also, video posts should be your video, something you recorded, or animated yourself. See Also
Retrieved from "https://indieweb.org/wiki/index.php?title=video&oldid=106218" |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |
