# format A set of structural, syntactic, and semantic conventions for representing and processing digital objects or serialized data. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Preparing Codename One for Android 17 and API 37 Migration DevFeed: [Preparing Codename One for Android 17 and API 37 Migration]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-17T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Android](), [migration](), [Security](), [format]() Tags: [android](), [apis](), [format](), [migration](), [security]() ### AI overview Codename One prepares for Android 17 and API 37 by adding platform compatibility checks, fixing API-level parsing and build-tool handling, and testing a new system-rendered location button. The article also describes moving PEM parsing and task removal into shared security-sensitive platform handling. ### Source excerpt API 37 checks and a system location button prepare Android migration. PEM parsing and task-clearing exit put more security-sensitive platform and format handling into Codename One. ## Video Streaming Protocols: 6 Preferred Formats for Professional Broadcasting DevFeed: [Video Streaming Protocols: 6 Preferred Formats for Professional Broadcasting]() Original publisher: [Read original article]() Author: Jon Whitehead Published: 2026-09-02T09:35:50Z Content type: tutorial Language: en Sources: [DaCast]() Topics: [Streaming](), [Protocol (disambiguation)](), [Latency](), [Low Latency](), [WebRTC](), [Playback](), [format](), [data]() Tags: [data](), [format](), [latency](), [low-latency](), [playback](), [protocols](), [streaming](), [the-video-experts-blog](), [video](), [video-streaming](), [webrtc]() ### AI overview This guide explains six video streaming protocols used in professional broadcasting: HLS, RTMP, WebRTC, SRT, RTSP, and MPEG-DASH. It compares their purposes, strengths, limitations, latency, compatibility, and suitable use cases. It presents HLS as a broadly compatible delivery default, RTMP as an ingest standard, WebRTC for real-time two-way interaction, SRT for one-way broadcasting over unreliable networks, RTSP for surveillance and IoT, and MPEG-DASH as an open alternative with limited Apple support. ### Source excerpt By Dacast Editorial Team | Reviewed by Jon Whitehead, COO at Dacast | Updated September 2026 A video streaming protocol is the set of rules that governs how video data moves from your encoder to your streaming host to the video player your audience watches on. Common examples include RTMP, HLS, WebRTC, and SRT, each [...] The post Video Streaming Protocols: 6 Preferred Formats for Professional Broadcasting appeared first on Dacast. ## Using Provocations to Shake the Status Quo DevFeed: [Using Provocations to Shake the Status Quo]() Original publisher: [Read original article]() Author: The NYT Open Team Published: 2025-07-22T16:23:11Z Content type: opinion Language: en Sources: [New York Times]() Topics: [Users](), [format](), [context]() Tags: [approach](), [design](), [engineering](), [figma](), [photography](), [process](), [recipe](), [ux-design](), [visual-hierarchy](), [visualization]() ### AI overview A case study of how NYT Cooking used high-fidelity design provocations to rethink recipe cards. The approach prioritized photography, flexible recipe information, a modernized format, and a more streamlined evaluation process while keeping the project scope controlled. ### Source excerpt The bold approach NYT Cooking used to define a strategy for recipe cards.Illustration by Ben Denzer By Jayne Lee In The New York Times Cooking, "cards," or the containers that represent our content, are the first impression of our brand. They're the window into our recipes and users rely on them to evaluate and choose what to cook. NYT Cooking users are particularly attracted to our appetizing food photos. In every research session, participants get distracted by a delicious-looking dish while answering the moderator's questions. People tend to browse with their stomachs first and then see if the recipe specifications meet their personal criteria (For example, do I have enough time to cook this?). A problem we encountered: our beautiful photography was muddied by the page's gray background. The white card containers sitting on top of the gray page forced your eyes to focus on the container instead of the photo. The visual hierarchy was at odds with the preferred reading and browsing order of our audience: photo first, then recipe information. Recipe information varies, so the card needs to afford that variability. Using containers forced us to keep our cards the same height, resulting in unnecessary whitespace. Since the cards were so tall, this limited the amount of recipes a user could see at once, increasing the time users scanned for recipes. We needed to highlight our photography, modernize the format and streamline the recipe evaluation process. While designing solutions, I realized that I had more questions than answers. Answering each question would have significantly bloated the project scope. Some examples were: What order of recipe information is most helpful when deciding between recipes? Are recipe bylines important? Which presentation of ratings is more effective? Because the priority was to update the format rather than improve comprehension, and to avoid bloating the scope of the project, I started with design provocations over design specs. Because ## Lessons Learned: Playing Elevation of Privilege DevFeed: [Lessons Learned: Playing Elevation of Privilege]() Original publisher: [Read original article]() Author: Adam Published: 2021-09-28T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [format](), [screen](), [Slack]() Tags: [format](), [screen](), [slack]() ### AI overview The article shares lessons from an Elevation of Privilege play-to-learn session. It explains that the cards prompt broad thinking about potential problems, help maintain attention in remote play, focus dominant participants, and give quieter team members more opportunity to contribute. It also recommends starting with a few rounds and using the findings iteratively. ### Source excerpt We learn while we're having fun. Some takeaways from a recent play to learn session. ## Reversing printf-as-a-VM service in Google Quals 2020 DevFeed: [Reversing printf-as-a-VM service in Google Quals 2020]() Original publisher: [Read original article]() Published: 2020-08-30T00:00:00Z Content type: tutorial Language: en Sources: [mahaloz.re]() Topics: [Reverse Engineering](), [C](), [format](), [Google](), [Ghidra]() Tags: [c](), [ctf](), [format](), [game](), [ghidra](), [reversing](), [vm]() ### AI overview This writeup explains how a Google Quals 2020 challenge implemented a virtual machine using C printf format strings. It covers reverse engineering the program, identifying the format-string instruction set and registers, and beginning to analyze the relevant format specifiers. ### Source excerpt Solving a virtual machine implemented inside format strings found in the printf library in C with @kylebot. ## On the Pan-Genome DevFeed: [On the Pan-Genome]() Original publisher: [Read original article]() Published: 2019-07-12T07:10:21Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [Computing](), [file](), [format]() Tags: [biology](), [computing](), [dna](), [file](), [format](), [formats]() ### AI overview This article explains how human genome references represent a mixture of people rather than one individual and how the FASTA file format cannot encode population-level genetic variation in a single sequence. It introduces the pan-genome as a broader representation that captures genes found in some but not all organisms. ### Source excerpt In this post I want to shine a light on an important development within the world of DNA which shows how much DNA and the world of computing are now intertwined. It turns out we share important problems, like in this case: file formats. Note: I expect to be posting more DNA material as part of my efforts to write a book on this fascinating subject. If you enjoy reading about DNA, you might like the links/presentations/videos found on this page. ## GoReleaser Docker support DevFeed: [GoReleaser Docker support]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2019-01-11T00:00:00Z Content type: release Language: en Sources: [Carlos Becker]() Topics: [Docker](), [configuration](), [format](), [version]() Tags: [configuration](), [docker](), [format](), [release]() ### AI overview The post describes a more flexible Docker configuration format planned for the next GoReleaser version. It supports multiple binaries, image names, registries, and tags in one build, along with extra files, build arguments, image-name templating, and push control. Multiple-platform support was still missing and expected before version 1.0. ### Source excerpt The next GoReleaser version will have a more flexible Docker configuration format. In this post we'll explore it a bit. ## A New Visual Identity for Droidcon NYC 2016 - touchlab DevFeed: [A New Visual Identity for Droidcon NYC 2016 - touchlab]() Original publisher: [Read original article]() Published: 2016-05-25T14:08:48Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Icons](), [format](), [Code]() Tags: [community](), [design](), [droidcon](), [elements](), [icons](), [layout](), [modular]() ### AI overview The article explains the creation of a new visual identity for Droidcon NYC 2016. It describes a flexible, modular pictographic system built from primary glyphs representing conference themes and promotional purposes, with glyphs that can be combined for session topics and other uses. ### Source excerpt Droidcon NYC is moving to a new venue with a somewhat new format, and a renewed focus on including design in the lineup. Read more.