My contribution to #BLM.

Tubby — Sun, 03 Jan 2021 14:37:57 +0000

Tubbie / let-me-breathe

It has been more than a month since the Black Life Matters protests broke out this time because of the death of George Floyd(RIP) murder and since the very beginning, the thing which got stuck in my mind was that the only reason this case exploded was that there was video evidence!

If the bystanders weren't recording it, this murder would have been justified by police as "use of necessary force" we all know what it would have meant and would carry on with our lives. We would also know that the police's body cam would have mysteriously malfunctioned, hence there wouldn't be any evidence of the crime.

The video shocked me to the core and made me wonder how a human being can be this cruel to another. Another thought which came to mind was because there was video evidence, at least there will be a trial on those police officers but those without will never get justice and moreover, the perpetrators will do it again.

I was afraid that this could happen to me also so I decided to protect myself by recording with my phone camera. But this was cumbersome and buying a body camera sounded a bit absurd to me. Also, I wanted it to save it and still have access if the camera is destroyed, stolen or maliciously deleted. Hence I decided to build one using Raspberry Pi (RasPi).
The idea is simple, record video of specific interval and then video upload it to a file server where I or a trusted person can have access to it. My vision for this project is for anyone to build for themself with as little tech knowledge as possible and with the least monetary investment possible.

For my prototype, I used Raspberry Pi Zero W as the brains and DropBox as free remote file storage. The whole project cost me about 20 Euros (about 25 US Dollars).
As RasPi Zero W has only Wi-Fi, I enable the hotspots from my phone and it connects to this network and uploads the recorded videos.

The program runs as a start-up process and as soon as I connect the power after a brief moment of bootup process it starts recording. The video are recorded in a set of minute/s interval. Currently the videos is recorded without audio as there is no Audio I/O built onto the RasPi Zero W. I have already implemented it with a USB Microphone, but the quality is lousy and implementation a bit excessive for a beginner.

I wish to perfect this soon but I would very grateful for the community take it further or provide some help.
The next big steps for this project I see as of now is having features like

Recording with audio
Voice activated recording
Connecting to the fitness band and to start recording in case of higher heart rate.

If you would like to build one for yourself or would like to contribute or see how bad my code is check out the github repo below ;-)

Tubbie / let-me-breathe

LET-ME-BREATHE

Let me breathe is an open source project to develop a low cost body camera.
Main goal of the project is to transfer to a remote server as soon as possible The Project uses RasberryPi Zero W to use as a module to capture via the camera and upload to a specific remote file storage or a server.

Installation

Requirements for the Installation.

Hardware Requirements.

RaspberryPi Single Board Computer. RaspberryPi Zero W preffered.
RaspberryPi Camera Module.
Power Source. Can be a Power Bank outputting 5V.
MicroUSB Cable.
MicroSD Card. 8GB+ Recommended.
MicroSD card reader. (If needed.)
Raspberry Pi Case. (Recommended if for outdoor use.)

Software Requirements.

Raspberry Pi OS Lite.
Image making tool like
- Imager (Recommended)
- Etcher
A Computer. (Need help with Windows and MAC OS documentation.)

Steps to install.

Insert MicroSD card to your PC.
Use an Imaging tool to create the RasPi OS Lite(32 Bit if the…

View on GitHub

P.S. Please check your local laws regarding the video recording, this might be an offence.

Disclaimer: This post was written in July 2020 and was in draft till now. Due to burnout, procrastinating, and feeling a lack of correct skills for the project this post was delayed. I now feel this should be shared even if the project is in the nascent stage and is not professional enough. I hope some of you can take it further. Thank you!

Optimal way to store/consume scheduled/recurring events

Tubby — Mon, 30 Mar 2020 19:32:20 +0000

I am working on best way to store the scheduled and recurring events. I am taking inspiration from here - https://github.com/bmoeskau/Extensible/blob/master/recurrence-overview.md.

I will be storing any events as RRule(iCal Events - https://tools.ietf.org/html/rfc5545) and duration of the event as separate properties.
The structure will look like this.

class Schedule {
    String rRule; //Varchar
    String startTime; //DateTime
    String endTime; //DateTime
}

With this structure the clients can show the events on calendar without querying the API.

It gets interesting when the events can be modified.
For Ex: Schedule = 'Daily at 10:00, duration 2 Hours' creates an event for everyday. But the user can modify(disable) any particular event. and this change should be stored. For this the above article suggests to use EventException(https://github.com/bmoeskau/Extensible/blob/master/recurrence-overview.md#eventexception) where the modified events are stored.

But in my use case I want to store if the event was successfully completed. (I can mitigate this by saying any event by default is successful, if there was some modification I store it in EventException and need to be fetched from here)

So I would like your opinion if this is the best way to do it? Did you have similar experience and how it was solved.
I am working on it to design a solution which reduces the work for both frontend and backend.

Also is it wise to store the RRule as a separate entity instead of a string?

Forem: Tubby

My contribution to #BLM.

Tubbie / let-me-breathe

Tubbie / let-me-breathe

LET-ME-BREATHE

Installation

Optimal way to store/consume scheduled/recurring events