27 Nov
2024
27 Nov
'24
3:48 p.m.
Dear Sudoroom,
It's been almost three years since this telescreen was set up with Jitsi, on
the wall in sudoroom. A few months ago the computer got taken, so I set up a
new one, and Matty is trying to get the automated software working again so
it's automatic and turns the screen off when no one is joined.
https://sudoroom.org/wiki/Bigtv
How do people feel about the telescreen? Do people like having this in place
so that people can connect with the space from elsewhere? How could it be
improved?
Also a reminder, we have a telephone and the number is I-HACK-AT-386
For a while the telephone was switching off but i recently made something that
automatically reboots it when that happens, so it should be pretty reliable
now.
-jake
---------- Forwarded message ----------
Date: Sun, 16 Jan 2022 18:18:15 -0800
From: ruin mechanic via sudo-discuss <sudo-discuss(a)sudoroom.org>
Reply-To: ruin mechanic <ruinmechanic(a)gmail.com>
To: sudo-discuss <sudo-discuss(a)sudoroom.org>
Subject: [sudo-discuss] Re: Jitsi telescreen setup in sudoroom!
Rejoice in the hacker wizardry of the new Telepresence Portal
Jake and I wrapped it up today and hackerspace futurism has been achieved
the monitor will turn on if any Sudoers join the jitsi chatroom
and it will shut off if everyone leaves the chat
here is the source for the chat client app powering it
https://github.com/sudoroom/jitsi-telepresence-portal
hooray!
-matty/interrupt
On Sat, Jan 15, 2022 at 11:50 PM Jake <jake(a)spaz.org> wrote:
wow, this has progressed a lot!
tonight, in the jitsi chat, which is here:
https://meet.waag.org/turtlesturtlesturtles
matt and me (to the entertainment of everyone passing through sudoroom and
working in there) have been chatting and co-hacking, and i've been learning
npm/node/react web stuff.
basically we installed the jitsi SDK repo and ran it, and then hacked it
to go
to the meeting room we've been using instead of the default setting - and
now
we're adding a function to it to automatically control the screen power
(screensaver) depending on whether someone is in the "room" or not.
we're also sharing a tmux window in the machine (the one controlling the
big
TV) and teaching each other lots of stuff. And neither of us are
physically in
the space!
It's the most exciting saturday night i've had in a long time!
If anyone else is interested in this kind of social hacking, speak up and
i'll
ping you if it happens again. Or just join the jitsi room (linked above)
and
leave it open until someone starts talking to you.
last night (friday night) we had a bunch of people join the chat!!!
including
a couple of people who randomly hadn't seen each other in almost 5 years!
It was basically a party, including whoever was in sudoroom, and like 6
different people who rolled through the jitsi chat.
-jake
On Sat, 15 Jan 2022, Jake wrote:
awesome! I believe this is what Matty is working
on too
https://github.com/jitsi/jitsi-meet-web-sdk
that was so much fun with everyone talking to each other tonight!
-jake
On Sat, 15 Jan 2022, Marc Juul wrote:
> On Wed, Jan 12, 2022 at 11:54 PM Marc Juul <marc(a)juul.io> wrote:
>
>> On Wed, Jan 12, 2022 at 1:37 AM Jake wrote:
>>
>>> I've set up a jitsi terminal on the wall in Sudoroom!
>>>
>>> It's a big TV made by Hitachi, and it has a feature where it can go
into
>>> "power saving" mode when
the HDMI signal is lost. That means the
screen
>>> can power down when DPMS puts the
monitor to "sleep". It has a webcam
>>> that's clearly labeled, and on a hinge so it can easily be aimed down
at
>>> the floor if people are shy, and it
has a Jabra USB speaker/microphone
>>> thing which should hopefully provide good speakerphone
functionality.
I
>>> have the computer setup to start
firefox, and i have firefox set to
open
>>> the jitsi page, where permissions are
already enabled for
webcam/audio.
>>> The only remaining need is to
automatically wake the monitor from
sleep
>>> (using "DISPLAY=:0 xset force
dpms on") whenever there is anyone else
>>> detected in the jitsi "room"
>>>
>>
>>
>> I wrote a short program that can trigger a command based on downstream
>> bandwidth usage:
>>
>> https://github.com/sudoroom/bw-trigger
>>
>
> So it turned out that the library I used doesn't really work for UDP :/
>
> The correct solution is definitely to have a client that joins with
XMPP.
Information is sparse but I found this code that I believe is for
stress-testing that should be modifiable into what we need:
https://github.com/jitsi/jxs
Relevant code in:
https://github.com/jitsi/jxs/blob/master/src/Participant.js
--
marc/juul