hso-20210408
hs.org regular monthly meeting
started 2021-04-08 18:00 UTC

meetings index: https://wiki.hackerspaces.org/Meetings
previous meeting: https://pad.land/hso-20210318

used jitsi: https://talk.fdn.fr/hackerspaces20210408

present:
    dcht00, zeno4ever, jo, lomanic, aria


Table of Contents
1 ***
1.1 [!] WIKI/BUG -- wth are all map markers doubled :)
1.2 [K] looking at mapall.space
1.2.1     contributions @ wiki
1.2.2     how it works
1.2.3     [!] WIKI/BOT -- mapall.space bot: D's proposal
1.2.4     [!!] WIKI -- explore designating wikibot as bot
1.3 [R!] CENSUS/BOT -- spaces to check manually
1.4 [!] CENSUS -- updates +aimee?
1.5 [!] WIKI/BUG -- filters in "recent changes" doesn't work
1.6 space.api
1.6.1     [!] >dcht00 —— talk to spaceapi about "exchanges" and "hackbases"
1.6.2     other nice space.api projects
1.6.3     [!] let's establish contact with spaceAPI
1.6.4     [!] "promoting in the USA of spaceAPI would be cool"
1.7 [!] PRIVACY -- the page is not GDPR compliant
1.8 [!] PRIVACY/PROTOCOL -- have a clear log policy
1.9 [!!!] ADMIN/SEC -- mediawiki version update
1.10 [!] WIKI/IDEA -- it would be interesting to see all spaces that closed
1.11 [~] SERVICE -- what's up with signal.hackerspaces.org
1.12 [K!] SERVICE/ACCESS -- twitter @hakerspacesbot
1.12.1     [!] ideas to improve @hackerspacesbot
1.13 [!!!C] ADMIN/SEC -- making a server account for backups
1.13.1     [!!] you can just "frost the key"
1.14 [!!!] ADMIN/LIST/BUG -- d's mail to tech@ didn't arrive
1.14.1     [!] ... check logs for mails
1.15 [!!!] WIKI/BUG -- image upload doesn't seem to work 
1.16 [!!] ADMIN/WIKI/BUG -- redirect old style wiki broken links
1.17 [!] SERVICE -- make a DASHBOARD, as a checklist for features
1.18 [!] SERVICE/DECISION -- deprecating jabber
1.19 [!!!] DECISION/ADMIN -- change hackerspaces.org landing page to redirect to wiki.hackerspaces.org
1.20 [!] DECISION/PROTOCOL -- maintaining services and admins
1.21 [E!!] PRIVACY/SEC/PROTOCOL -- admins list: public or not public


***

[!] WIKI/BUG -- wth are all map markers doubled :)




[K] looking at mapall.space

https://mapall.space :
    * doesn't force SSL! >zeno4ever [Done, redirect to https]
    * how does https://spaceapi.io/ work?:
        → you have to make a descriptor file and open a PR to the GitHub project where a centralized list of spaces is maintained to add your space! https://github.com/SpaceAPI/directory

~20 visitors/day






    contributions @ wiki

https://wiki.hackerspaces.org/Special:Contributions/WikiBot

You can see what:
    "update to update" = space is still active, no change, just added comments
    "update to inactive" = changes ACTIVE→SUSPECTED INACTIVE (status specific added for Wikibot!)


    how it works

bot (in principle) makes changes 1/every year, after 1 year of no changes on the wiki page
(+) it sends a ping to the people
(-) it leaves some trash behind in the page :)



    [!] WIKI/BOT -- mapall.space bot: D's proposal

add two new fields:
    * last changed, non bot
    * last changed, by bot

let's:
    * think about it
    * can semanticwiki make a "last changed by non-wikibot"
    * [...]



    [!!] WIKI -- explore designating wikibot as bot

that might also solve the "recent changes"
>david








[R!] CENSUS/BOT -- spaces to check manually

the bot does automatic "active" or "passive" checking for spaces

procedure info & decision it needs manual intervention with:
    https://mapall.space/hswikilist.php :


[!] CENSUS -- updates +aimee?

seek to get some update / status :)
maybe making an interview?
>david

* how to check recent updates without the bot?
* could bot not flip the "last updated"?
* could you also show residencies?
* [...]


[!] WIKI/BUG -- filters in "recent changes" doesn't work

https://wiki.hackerspaces.org/Special:RecentChanges
(saw a hint somewhere it might be about "job queues"!)




space.api

https://spaceapi.io/
killer feature = "is space open right now"


    [!] >dcht00 —— talk to spaceapi about "exchanges" and "hackbases"

###
where do they meet? https://matrix.to/#/#spaceapi:matrix.coredump.ch
who's a contact'



    other nice space.api projects

heatmap of when spaces are open
https://spaceapi.vanheusden.com/

zeno4ever also maintains 
https://hackerspaces.nl/



    [!] let's establish contact with spaceAPI

would be nice to include them in some talk



    [!] "promoting in the USA of spaceAPI would be cool"




[!] PRIVACY -- the page is not GDPR compliant

and that's not only a legality ... these laws have a function



[!] PRIVACY/PROTOCOL -- have a clear log policy

we're currently not really dropping logs
should we?



[!!!] ADMIN/SEC -- mediawiki version update

current version is EOL.

how does the procedure do?
do we have/do staging?

jo:
    * i did it before, but don't remember exactly how :)
    * php was updated recently (to something like 7.3 or 7.4)
    * there's really no staging



[!] WIKI/IDEA -- it would be interesting to see all spaces that closed

A) via the bot:
    also to double-check

B) just in any way:
    to have insight into patterns


https://wiki.hackerspaces.org/Special:Contributions/WikiBot

Look for hackerspace status of "suspected inactive", this is only set by the wikibot!



[~] SERVICE -- what's up with signal.hackerspaces.org

https://signal.hackerspace.org
is cname to https://signal.sonologic.net

no idea how it works or who does that?:
    -> gmc is a dutch hacker, zeno/dave know where to find him kind off

but sounds pretty cool



[K!] SERVICE/ACCESS -- twitter @hakerspacesbot

using tweetdeck.
jomat had access:
    spread to @dcht00 and xeno4ever (@daveborghuis)


    [!] ideas to improve @hackerspacesbot
:
    * co-write and maintain (on these meetings) posting policy → new pad!
    * twitter lists:
        * all hackspaces
        * per language, area, topic, etc
    * retweet international events (especially if they offer online participation)
    * [...]



[!!!C] ADMIN/SEC -- making a server account for backups

it will be borg
so "push"

    [!!] you can just "frost the key"
>david
>jo

(will continue in private)
dcht00: command="cd /home/bbackup/repos/my.server.example.com/;borg serve --append-only --restrict-to-path /home/bbackup/repos/my.server.example.com/",no-port-forwarding,no-X11-forwarding,no-pty,no-agent-forwarding,no-user-rc ssh-rsa AAAAB3...
> .ssh/authorized_keys



[!!!] ADMIN/LIST/BUG -- d's mail to tech@ didn't arrive

(Sent 20210407 20:52 GMT)

    [!] ... check logs for mails

#semaphore
jo: "lots of emails rejected by icloud"





[!!!] WIKI/BUG -- image upload doesn't seem to work 

(this seems for a few months already)



[!!] ADMIN/WIKI/BUG -- redirect old style wiki broken links

http://hackerspaces.org/wiki/Page 
→ Redirect to https://wiki.hackerspaces.org/Page, with what's used as a web server



[!] SERVICE -- make a DASHBOARD, as a checklist for features

like...
* mailing lists
* image upload
* wiki
* wiki maps
* planet
* [...]




[!] SERVICE/DECISION -- deprecating jabber

* it's dead for 2 years already
* it wasn't really used before that
* there's no way to get the data
* it would be interesting for somebody that used it, to write a report/history of it:
    how many people used it
    was it ever really active
    ___________
    "it was metalab's server ... most people had accounts there"
* [...]


→ decided: we retire it in the various communication pages & links



[!!!] DECISION/ADMIN -- change hackerspaces.org landing page to redirect to wiki.hackerspaces.org

like back in the old days

* it used to be directly to the wiki, why did this chage? (archive.org confirms this  https://web.archive.org/web/2014/http://hackerspaces.org/ )
* dates are wrong, most links are wrong, and anyway, it should be a part of the wiki so it's easily editable

→ we decide to change this back :)

how?
A) redirect
B) "proxy pass" 

→ we decide for redirect.



[!] DECISION/PROTOCOL -- maintaining services and admins

https://wiki.hackerspaces.org/Staff
we seem to have many services & admins that we don't know, haven't heard from in a while, or aren't sure if we can even reach.

→ decided to do: "the dutch approach" ;)
    send one mail, give a month time frame to answer,
    if they don't, sorry.

→ also: rename the "retired staff" part to "idle" / "inactive"



[E!!] PRIVACY/SEC/PROTOCOL -- admins list: public or not public

A) all
B) those who want
C) nobody, just write down tech@

we're thinking:
    * maybe have "single point of depreciation"
    * but also, it's nice to be famous lol...

→ solution:
    "people to talk to" section
    so people can find you
and murder you in saal B









(Site generated by E2H, an "Etherpad hypermedia" project by @dcht00). Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.


Edit Site

Edit CSS