User:Kim/Special Issue 27/Timekeeping device: Difference between revisions
< User:Kim | Special Issue 27
(→ideas) |
No edit summary |
||
| Line 26: | Line 26: | ||
* [https://solar.lowtechmagazine.com/power/ Lowtech Magazines Server stats] | * [https://solar.lowtechmagazine.com/power/ Lowtech Magazines Server stats] | ||
* [https://solarprotocol.net/ Solar protocol] Server stats over time | * [https://solarprotocol.net/ Solar protocol] Server stats over time | ||
==cereal time== | |||
$ timedatectl | |||
outputs | |||
Local time: Mon 2025-05-19 19:13:43 BST | |||
Universal time: Mon 2025-05-19 18:13:43 UTC | |||
RTC time: n/a | |||
Time zone: Europe/London (BST, +0100) | |||
System clock synchronized: yes | |||
NTP service: active | |||
RTC in local TZ: no | |||
Revision as of 20:16, 19 May 2025
tests
can be found on cerealbox timekeeping-device/
terminal
- ping
- to graph (graphic) visualizing length of seconds
- traceroute
- time (cmd)
ideas
- server time
- expand on cerealbox uptime, make more small api's and interfaces for them
- not so much making a clock for cerealbox but more about exploring/ surfacing its (ways of passing, keeping) time
- this is also on labour, questions of service, maintenance
- in the room are also expectations: for services to run smoothly, total availability, fast (and direct) delivery
- how do we interface with server (time) ?
- text as timekeeping device User:Sevgi
- in what ways? (we use texts, rhymes, phrases to map time periods and rhythm – text can age – a log) ...
references
- Lowtech Magazines Server stats
- Solar protocol Server stats over time
cereal time
$ timedatectl
outputs
Local time: Mon 2025-05-19 19:13:43 BST Universal time: Mon 2025-05-19 18:13:43 UTC RTC time: n/a Time zone: Europe/London (BST, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no