Date: 2019-10-22
Location: The Internet
Who: Danilo, Raphi, Timm
Previous meeting: 20190611-telco.md Next meeting: 2020-01-28 20:17 CET
- Status
- Geekend
- HSTS
- Validator API
- Github Bot
- Directory View
- Dockerfile linting
- Api field
- Website content
- Next Meeting
Danilo
- Get new website online
- Add a warning on our website that spaceapi.net is deprecated
- Upload Twitter-Password to Gopass
- Watchtower:
- Auto-update?
- Get rid of chatty messages?
- Wait for upstream:
Timm
- DNSSEC
- Waiting for provider to add DNSSEC support to the control panel
Raphi
- Getting started guide (SpaceApi/website#30)
We kind of used the CCC Camp as Geekend and worked on the website (it's online! 🎉).
Thing we will need to prepare:
- Agenda. So that we can work productively
- Location
- Coredump,
(47.23597, 8.84096), https://www.coredump.ch/kontakt/
- Coredump,
- Date
- Food
- Announce on chat, ML (hackerspaces.org) and Twitter
Should we enable HSTS + Preloading?
- Every service would only be available over HTTPS / TLS
- Are there use cases where a limited embedded device needs to access the directory via HTTP?
- An ATtiny won't be able to run TLS
- A small ARM will be able to run TLS, but can't do certificate chain verification
- A niche use case?
- Encrypt everything, because encrypt everything! 🔒
- If someone has a use case, we can still disable the redirection and wait for the preloading to expire. Preloading headers don't apply to embedded devices, only to browsers.
- Add OpenAPI schema (Timm)
- Add error information to output
- For that, maybe switch to the Go implementation
- Add an endpoint where an URL can be validated directly
- Work in progress: A bot which checks directory PRs for common problems: https://github.com/SpaceApi/github-bot
- Example: SpaceApi/directory#112 -> https://githubbot.spaceapi.io/pullrequest/112
- TODO: Convert that output into a nice GitHub comment
- Maybe create a nicer directory / space overview?
- Timm is working on something.
We have a lot of custom Dockerfiles:
- website
- validator
- ...
Running a Docker linter during CI for these would be nice.
Goal is to provide a smooth upgrade path between API versions. An endpoint could declare compatibility for multiple versions.
Isn't just having multiple endpoints easier?
Why not both approaches? 🤷♀️
We should improve the website -> https://md.chaospott.de/spaceapi-content
Meetup at Chaos Communication Congress
Next Meeting: 2020-01-28 @20:17