User:Kim/Special Issue 27/Timekeeping device - Revision history

Kim: /* terminal */

2025-05-24T15:53:39Z

terminal

← Older revision		Revision as of 17:53, 24 May 2025
Line 13:		Line 13:
	: get some local (outside) factors (or the fact that cerealbox will go down in the break?) --> what else is class specific (our graduation/ our study beginn, its a very temporal server)		: get some local (outside) factors (or the fact that cerealbox will go down in the break?) --> what else is class specific (our graduation/ our study beginn, its a very temporal server)

	;uptime		;[[User:Kim/Special Issue 27/uptime\|uptime]]
	: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?		: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?
	:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])		:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])

Kim: /* terminal */

2025-05-24T13:13:04Z

terminal

← Older revision		Revision as of 15:13, 24 May 2025
Line 16:		Line 16:
	: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?		: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?
	:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])		:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])
	:: more links: [https://www.designlife-cycle.com/raspberry-pi lifecycle of a rasberry pi], [https://computer.howstuffworks.com/raspberry-pi2.htm how the pi works w/ component list], [https://flexpcb.org/bcm2835-what-is-it-and-what-does-it-do/ the rasberry pi's specific chip (semiconductor)], [https://~~www~~.~~youtube.com~~/~~watch~~?v=~~WKHKy89QaV0~~ chip factory in taiwan (yt video)]		:: more links: [https://www.designlife-cycle.com/raspberry-pi lifecycle of a rasberry pi], [https://computer.howstuffworks.com/raspberry-pi2.htm how the pi works w/ component list], [https://flexpcb.org/bcm2835-what-is-it-and-what-does-it-do/ the rasberry pi's specific chip (semiconductor)], [https://youtu.be/WKHKy89QaV0?feature=shared&t=481 chip factory in taiwan (yt video)]

	==ideas==		==ideas==

Kim: /* terminal */

2025-05-23T19:39:31Z

terminal

← Older revision		Revision as of 21:39, 23 May 2025
Line 16:		Line 16:
	: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?		: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?
	:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])		:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])
	:: more links: [https://www.designlife-cycle.com/raspberry-pi lifecycle of a rasberry pi], [https://computer.howstuffworks.com/raspberry-pi2.htm how the pi works w/ component list], [https://flexpcb.org/bcm2835-what-is-it-and-what-does-it-do/ the rasberry pi's specific chip (semiconductor)]		:: more links: [https://www.designlife-cycle.com/raspberry-pi lifecycle of a rasberry pi], [https://computer.howstuffworks.com/raspberry-pi2.htm how the pi works w/ component list], [https://flexpcb.org/bcm2835-what-is-it-and-what-does-it-do/ the rasberry pi's specific chip (semiconductor)], [https://www.youtube.com/watch?v=WKHKy89QaV0 chip factory in taiwan (yt video)]

	==ideas==		==ideas==

Kim: /* terminal */

2025-05-23T19:38:09Z

terminal

← Older revision		Revision as of 21:38, 23 May 2025
Line 16:		Line 16:
	: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?		: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?
	:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])		:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])
			:: more links: [https://www.designlife-cycle.com/raspberry-pi lifecycle of a rasberry pi], [https://computer.howstuffworks.com/raspberry-pi2.htm how the pi works w/ component list], [https://flexpcb.org/bcm2835-what-is-it-and-what-does-it-do/ the rasberry pi's specific chip (semiconductor)]

	==ideas==		==ideas==

Kim: /* terminal */

2025-05-23T19:04:50Z

terminal

← Older revision		Revision as of 21:04, 23 May 2025
Line 15:		Line 15:
	;uptime		;uptime
	: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?		: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?
	:: in that sense it would connect community of practices that use the server, its own operations and its material relations		:: in that sense it would connect community of practices that use the server, its own operations and its material relations ([https://youtu.be/k2C4lbbIH0c?feature=shared how are rasberri pi's made video])

	==ideas==		==ideas==

Kim: /* terminal */

2025-05-23T18:44:49Z

terminal

← Older revision		Revision as of 20:44, 23 May 2025
Line 15:		Line 15:
	;uptime		;uptime
	: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?		: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?
			:: in that sense it would connect community of practices that use the server, its own operations and its material relations

	==ideas==		==ideas==

Kim: /* terminal */

2025-05-23T18:43:24Z

terminal

← Older revision		Revision as of 20:43, 23 May 2025
Line 14:		Line 14:

	;uptime		;uptime
	: extend uptime, not only the command but also when was the server initially set up? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?		: extend uptime, not only the command but also when was the server initially set up [https://unix.stackexchange.com/a/762131 birth]? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?

	==ideas==		==ideas==

Kim: /* terminal */

2025-05-23T18:37:12Z

terminal

← Older revision		Revision as of 20:37, 23 May 2025
Line 12:		Line 12:
	: build a timer in the terminal with bash using sleep and ring the bell after selected period		: build a timer in the terminal with bash using sleep and ring the bell after selected period
	: get some local (outside) factors (or the fact that cerealbox will go down in the break?) --> what else is class specific (our graduation/ our study beginn, its a very temporal server)		: get some local (outside) factors (or the fact that cerealbox will go down in the break?) --> what else is class specific (our graduation/ our study beginn, its a very temporal server)

			;uptime
			: extend uptime, not only the command but also when was the server initially set up? and then future uptime: how long will it be running? and then its micro material basis: since when is that here?

	==ideas==		==ideas==

Kim: /* ideas */

2025-05-23T18:30:30Z

ideas

← Older revision		Revision as of 20:30, 23 May 2025
Line 26:		Line 26:
	**<span style="color: lightgray;"> in what ways? (we use texts, rhymes, phrases to map time periods and rhythm – text can age – a log) ...</span>		**<span style="color: lightgray;"> in what ways? (we use texts, rhymes, phrases to map time periods and rhythm – text can age – a log) ...</span>
	** get real time once: then make time depending on different parameters, latency of the server (slower/ faster)		** get real time once: then make time depending on different parameters, latency of the server (slower/ faster)
	* '''opening things up''' micro time scales, layers, material basis, extraction		* '''opening things up'''
			** micro time scales, layers, material basis, extraction

	==references==		==references==

Kim: /* ideas */

2025-05-23T18:30:12Z

ideas

← Older revision		Revision as of 20:30, 23 May 2025
Line 14:		Line 14:

	==ideas==		==ideas==
	* server time		* '''server time'''
	** expand on [https://hub.xpub.nl/cerealbox/~kim/timekeeping-device/uptime2.html cerealbox uptime], make more small api's and interfaces for them		** expand on [https://hub.xpub.nl/cerealbox/~kim/timekeeping-device/uptime2.html 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		** not so much making a clock for cerealbox but more about exploring/ surfacing its (ways of passing, keeping) time
Line 25:		Line 25:
	*<span style="color: lightgray;"> text as timekeeping device [[User:Sevgi]]</span>		*<span style="color: lightgray;"> text as timekeeping device [[User:Sevgi]]</span>
	**<span style="color: lightgray;"> in what ways? (we use texts, rhymes, phrases to map time periods and rhythm – text can age – a log) ...</span>		**<span style="color: lightgray;"> in what ways? (we use texts, rhymes, phrases to map time periods and rhythm – text can age – a log) ...</span>
	* get real time once: then make time depending on different parameters, latency of the server (slower/ faster)		** get real time once: then make time depending on different parameters, latency of the server (slower/ faster)
			* '''opening things up''' micro time scales, layers, material basis, extraction

	==references==		==references==