# wide Published articles for wide. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## SwiNOG 40: Deploying Precision Time Protocol across WAN DevFeed: [SwiNOG 40: Deploying Precision Time Protocol across WAN]() Original publisher: [Read original article]() Published: 2025-09-23T05:33:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Protocol (disambiguation)]() Tags: [infrastructure](), [network](), [precision](), [protocol](), [ptp](), [synchronization](), [time](), [wide](), [worth-reading]() ### AI overview The article discusses deploying Precision Time Protocol across a country-wide WAN to achieve nanosecond-level synchronization between cities. It states that this requires dedicated infrastructure and points to a SwiNOG 40 presentation by Oliver Ettlin for more details. ### Source excerpt Is it possible to deploy Precision Time Protocol across a country-wide WAN network and reach nanosecond-level synchronization between cities? It's definitely not trivial and only works over dedicated infrastructure; for more details, watch the PTP in WANs (video) presentation Oliver Ettlin had at SwiNOG 40. ## Lab: Using IS-IS Metrics DevFeed: [Lab: Using IS-IS Metrics]() Original publisher: [Read original article]() Published: 2024-11-12T05:58:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [IS-IS]() Tags: [blog-post](), [is-is](), [netlab](), [wide]() ### AI overview The article introduces a lab exercise on IS-IS metrics and notes that wide metrics were standardized in RFC 3784 in 2004, while many vendors still default to narrow metrics. ### Source excerpt It's time for another "the vendor IS-IS defaults are all wrong" blog post. Wide IS-IS metrics were standardized in RFC 3784 in June 2004, yet most vendors still use the ancient narrow metrics as the default setting. Want to know more? The Using IS-IS Metrics lab exercise provides all the gory details. ## What's on My Desk? DevFeed: [What's on My Desk?]() Original publisher: [Read original article]() Published: 2021-10-24T08:30:00Z Content type: opinion Language: en Sources: [Gunnar Morling]() Topics: [Large Screen](), [samsung](), [macOS]() Tags: [cameras](), [computer](), [conferences](), [covid](), [curved](), [evaluation](), [monitors](), [personal-experience](), [samsung](), [screen](), [ultra-wide](), [wide](), [work]() ### AI overview A personal account of improving a home computer setup for remote work, online calls, and recording conference talks. The article discusses a curved Samsung ultra-wide monitor and briefly introduces other setup components, including cameras, lighting, and audio equipment. ### Source excerpt Table of Contents The Screen Compute Cameras Work in Progress: Teleprompter Lighting Audio What's Next? I've been working from home exclusively for the last nine years, but it was only last year that I started to look into ways for expanding my computer set-up and go beyond the usual combination of having a laptop with your regular external screen. The global COVID-19 pandemic, the prospect of having more calls with colleagues than ever (no physical meetings), and the constantly increasing need for recording talks for online conferences and meet-ups made me reevaluate things and steadily improve and fine tune my set-up, in particular in regards to better video and audio quality. ## Every Camera, Every Angle on Android DevFeed: [Every Camera, Every Angle on Android]() Original publisher: [Read original article]() Author: GameChanger Published: 2021-09-20T14:49:50Z Content type: tutorial Language: en Sources: [GameChanger]() Topics: [Android](), [API](), [Streaming]() Tags: [android](), [apis](), [article](), [camera](), [camera2](), [camerax](), [streaming](), [ultra-wide](), [video](), [video-streaming](), [wide]() ### AI overview This article explains how GameChanger implemented ultrawide camera streaming on Android. It describes the differences between physical and logical camera setups and the challenges of selecting the correct camera sensor through Android's multi-camera APIs. ### Source excerpt At GameChanger, video streaming has become a huge part of our business and thus our tech stack. But as a small company that practices shipping often, we can't ship everything feature complete from day one and thus video streaming launched with the ability to only stream from your default rear camera lens. But as we know, ultrawide lenses on phones have become common place and sure enough, customers began writing in, asking to be able to use their ultrawide cameras to stream their event. Baseball and softball fields are actually quite wide and it makes a lot of sense to be able to capture more of the field. So in time, ultrawide streaming became our priority and thus we engaged in battle with one of the most brittle Android APIs we have seen... Streaming in the olden days Well, not really in the olden days, because we are using the most up to date APIs, but before we implemented ultrawide streaming, selecting the camera we wanted to stream with was generally pretty simple: private fun CameraManager.chooseCamera(teamId: TeamId) = cameraIdList.filter { id -> val characteristics = getCameraCharacteristics(id) val capabilities = characteristics.get(CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES)!! characteristics.get(CameraCharacteristics.LENS_FACING) == CameraMetadata.LENS_FACING_BACK && capabilities.contains(CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE) } .mapNotNull { id -> val characteristics = getCameraCharacteristics(id) val cameraConfig = characteristics.get(CameraCharacteristics.SCALER_STREAM_CONFIGURATION_MAP)!! val (width, height) = arrayOf(1280, 720) cameraConfig.getOutputSizes(MediaRecorder::class.java) .filter { it.width <= width && it.height <= height } .maxByOrNull { it.width * it.height }?.let { id to it } } .map { (id, resolution) -> CameraArgs(cameraId = id, width = resolution.width, height = resolution.height, fps = 30) } .firstOrNull() TL;DR: Basically, get the first rear camera that supports 720p. Note the cameraId--an