Urgent.News

What's breaking now, across thousands of outlets.

Tech

What if a security camera could be more than just a camera?

Recently, I've been exploring an open-source project called OpenNVR , and I found the idea behind it genuinely interesting. We usually think of a security camera in a very simple way: Camera → Video → Recording → Search when something happens But a camera is actually observing its environment continuously. A person enters a room. A vehicle arrives. Someone crosses a restricted area. An object is…

Recently, the author delved into an open-source project called OpenNVR, and found its concept intriguing. Traditionally, a security camera operates in a straightforward manner: Camera → Video → Recording → Search. However, a camera's true potential lies in its continuous observation of its surroundings. When a person enters a room, a vehicle arrives, someone crosses a restricted area, or an object is moved, the camera plays a crucial role in capturing these events.

The question then arises: What if we could develop applications based on everything the camera perceives? This is precisely what caught the author's attention while exploring OpenNVR. It's not merely about displaying multiple camera feeds or archiving recordings. What intrigued the author was the developer-oriented aspect - cameras, events, AI models, and applications could form part of a larger system that developers can build upon.

One idea that particularly appealed to the author is the concept of an AI adapter architecture. Rather than relying on a single AI model, different models can be linked through adapters. This opens up a range of possibilities. The developer can experiment with object detection, tracking, license plate recognition, face recognition, scene understanding, or even create their own models.

Moreover, there's the App SDK. It prompted the author to ponder: What if instead of merely constructing another application that simply observes a camera feed, we built something that actively utilizes what the camera sees? For instance, the application could detect something, comprehend the event, and trigger an action. Or, perhaps, it could ask the camera what occurred in a specific area, or even create a completely novel workflow that hasn't been conceived before.

The author also values that OpenNVR is open-source and self-hosted. The ability to retain video, processing, and AI within one's own infrastructure is highly appealing for experimenting with computer vision and edge AI. While the author is still exploring the project, they don't intend to present this as a comprehensive technical analysis or a product review.

Instead, it serves as a thought-provoking piece that challenges the conventional notion of treating cameras as mere video sources. Instead, they suggest that cameras could potentially evolve into programmable sensors for the physical world, a prospect that excites the author as a developer. The author is keen to observe what individuals within the community would develop using this concept.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Rate Limiting Algorithms: Token Bucket vs Sliding Window Explained

Every public API eventually needs a way to say "not so fast." Without it, one misbehaving client, a retry loop gone wrong, or a scraper can consume enough capacity to slow the service down for…

  • Token bucket algorithm maintains fixed tokens replenished at steady rate
  • Consumes one token per request, rejects if empty, credits unused tokens
  • Sliding window uses rolling 60-second period to count recent requests

I Built ReleaseReady: A Simple Tool to Check Your Project Before Release 🚀

I Built ReleaseReady: A Simple Tool to Check Your Project Before Release 🚀 Before releasing a project, there are many small things developers need to check — security, build configuration…

  • ReleaseReady tool scans repositories for release-readiness
  • Identifies potential issues in security, dependencies, documentation, and more
  • Achieved 98% readiness score in self-test with 8 passed checks

Invention of OOPs

1. The problem OOP was trying to solve In the late 1950s and early 1960s, programs were written as long sequences of procedures operating on shared global data.

  • Ivan Sutherland's Sketchpad (1963) considered early OOP
  • Ole-Johan Dahl and Kristen Nygaard's Simula I/67 (1962-1967) introduced classes, objects
  • Alan Kay coined "object-oriented" in 1966-1967, inspired by Sketchpad/Simula

More from Wednesday 30 September →