Hi pd, hi all, I'm not so happy with published recordings without asking about it or at least announcing it in the certain session.
Though publishing recordings might help to 'spread the pil21 word'^^ it would require much effort in editing and indexing the stream. It could be sustainable to publish some shorter excurses of some PilCons, but I would like to have a talk before, as I totally agree with razzy's view, that PilCon 'is also about socialization and trust-building'. I like the idea to publish the console history. Or to use the old 'script' command line tool, which beneroth brought up in IRC. (of course I have troubles to understand what script does ... a few keystrokes produced megabytes of recording file when trying it without reading the man page before ...) In either tool, we could try to type significant comment lines to seperate different topics and make them easier to find when browsing through. If someone who could not take part in the PilCon reads afterwards the history or script file - could then specifically ask in the mailing list, so that he/she won't get lost of any PilCon topics. Greetings, Olaf On 22.09.21 20:28, pd wrote: > Hello, > > I don't have a stablished opinion because don't know so much about > current platforms and services. So I really don't care while enjoying > good service during the meeting. > > As far as I know, twitch deletes video recordings after a while and this > may be an advantage or an inconvenient > > I think the better platform would be that on which Alex feel more > comfortable. > > I still think it should be a good idea to record the meetings and > publish them in a video repository such as youtube, vimeo or a similar > one. I've done a test recording a meeting and publishing it in vimeo > and I see it's possible, the problem is I cannot attend every meeting, > it would be great having several people who could cover the recording. > > One problem is the duration of the meeting that ends in a long video > file, difficult to upload, in my tests it exceed the length allowed by > youtube. You always can remaster the video changing quality or size or > even cutting it in pieces but all this is quite tedious. > > greets. > > > On Wed, Sep 22, 2021 at 11:49 AM O.Hamann <o.ham...@gmx.net > <mailto:O.Hamann@gmxnet>> wrote: > > Hi Alex, > > would be great to have shared Tmux via SSH again in PilCon meetings! > > It would be no problem to provide a payed Zoom Meeting Room without the > need of reconnecting after 40minutes, but I'm not sure what the > community thinks about not using the selfhosted (many thanks to > beneroth!) Jitsi server. > > What do others think? > > Or could it be a way, to announce certain 'screenshare-required PilCon > Session taking place on ... ...' if necessary, but in general continue > with jitsi and ssh terminal? > > What about other (commercial) solutions, which promise more data > security, like www.teamviewer.com/en/meeting > <http://www.teamviewer.com/en/meeting> ? > > I can't technically judge, what teamviewer claims (see below), but in > general European or Germamny based companies have to obey more rules > concerning data and privacy awareness, I think. > > They say: > "Unlike other online meeting tools, TeamViewer Meeting provides a GDPR > and HIPAA compliant platform with RSA 4096 public/private key exchange > and 256-bit end-to-end encrypted videoconference calls, designed to > protect sensitive, highly confidential information. Lock meetings and > add meeting passwords to keep uninvited guests out of private > discussions." > > > For me it would be worth a few bucks per month to provide a stable > screen sharing session for our PilCon Meetings, but I also would like to > *not* exclude anyone because of choosing inacceptable tools. > > What do you think? > > Kind Regards, > > Olaf > > > On 21.09.21 11:27, Alexander Burger wrote: > > Hi all, > > > > yesterday's PilCon was a bit chaotic. Sorry for that! > > > > I found out why the shared Tmux via SSH did not work. It was a > file permission > > problem. Should be OK next time. > > > > Screen share in Jitsi is a persistent hassle. It locks up for some > clients, and > > sharing from my Android phone sometimes does not work at all, and > sometimes gets > > incredibly slow. Any ideas? > > > > Please send me questions for the next PilCon a few days earlier, > so that I can > > search for examples and use cases! > > > > ☺/ A!ex > > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de > <mailto:picolisp@software-lab.de>?subjectUnsubscribe > -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
