Whether To Design Open Source Public Records Equipment

[Karl]

On Sat, Jun 13, 2020, 7:56 AM Zenaan Harkness <zen at freedbms.net> wrote:

> On Fri, Jun 12, 2020 at 09:55:46PM +0000, jim bell wrote:
> >  On Friday, June 12, 2020, 11:06:01 AM PDT, Punk-Stasi 2.0 <
> punks at tfwno.gf> wrote:
> >
> >
> >  On Fri, 12 Jun 2020 05:43:33 -0400
> > Karl <gmkarl at gmail.com> wrote:
> >
> >
> > >> Some of us want to sousveil the authorities,
> >
> > >    well, surveill the authorities all you want. Put a camera in every
> cop's bathroom...
> >
> >  >  But that's very different from 'wearing' some device that records
> everything around you. That is not surveilling the authorities but spying
> on everybody within the reach of your cameras.
> >
> >  >   As a side note of sorts, the argument (just an assertion actually)
> that it's ok to record people on 'public property' is exactly govcorp's
> 'argument' eh?
> >
> > You apparently don't realize that when government does that
> surveillance, it generally only uses that data for the detriment of a
> citizen.  If the information collected is embarrassing to the government
> itself, that information doesn't usually see the light of day.
> > I want to see that pattern changed.
> >       Jim Bell
>
>
> It seems that the ability for randos in public to be able to whip out
> their 'tard-phone and record what's in front of them, is producing a few
> useful 'exposures of problems'.
>
> To this end, an app, "Record and duplicate" could, with one button, and
> "all at the same time":
>
>    - begin recording
>
>    - enable ad-hoc wireless
>
>    - compress the recording to a size "suitable for broadcast to ad-hoc
> neighbours"
>
>    - work out (/ roughly calc) max simultaneous incoming streams this
> device can support ("record my peers" to back up their streams)
>
>    - preference and/or randomize if too many simultaneous "incoming backup
> streams"
>
>    - build a list of peers
>
>    - start sending my stream to some number of peers ("for backup")
>
>    - if extra bandwidth available, forward streams i.e. act as a distance
> bridge/ repeater (this may need nodes, as in/like the bittorrent protocol)
> to share information about peers they are aware of (e.g. node closeness
> based on signal strength)
>
>
> With such an 'on-demand' app, The Authorities may have a harder time
> getting rid of "problematic" recordings.  If that became a real and ongoing
> probem for the deep state swamp, The Authorities would then lean on Google
> to "do more evil" and auto remove or disable the app during relevant times
> and locations - which would be useful for showing folks they do not own
> their phones...
>

You're on the same page as me here.  I like your design and I'm pretty sure
we can solve the google problem separately as you recommended on the thread
I cried to you on.

I guess I like sticking to thread topics to organize things, dunno.

Would you be interested in working on such an app?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/html
Size: 4144 bytes
Desc: not available
URL: <https://lists.cpunks.org/pipermail/cypherpunks/attachments/20200613/55249bd9/attachment.txt>