#pest | 2023-02-11

09:29

signpost, is book/paper hoard from cause or towards a purpose?

09:29

the essential feature i was aluding to is the fact that barret paper is then referenced from http://www.loper-os.org/?p=2842

09:30

phf

http://logs.nosuchlabs.com/log/pest/2023-02-11#1023047 << i actually sent this last night as part of the conversation that was happening, but it got lost in aether, and only bumped because i sent another message in the morning

09:31

dulapbot

Logged on 2023-02-11 09:26:38 phf: signpost, is book/paper hoard from cause or towards a purpose?

09:31

phf

i guess instead of spamming with addresscasts it would've been more useful for stations to periodically emit prods

↖

09:33

phf

asciilifeform, is the idea of threading that you can just explicitly say "netchain of this message is this other message that i'm `responding` to"?

↖

09:35

phf

i think you suggested somewhere that you don't do "response" as such, and just add netchain visualization to the client. have you thought about adding an explicit flag for "this is a response" messages?

↖

09:38

phf

i recon it's not too hard to make a client be smart about it, even without an explicit "response" flag. if you're within some arbitrary netchain skip limit (5-6 messages), then the client can feel free to show an antecedent message as a "hint"

09:38

09:29	phf	signpost, is book/paper hoard from cause or towards a purpose?
		↖
09:29	phf	the essential feature i was aluding to is the fact that barret paper is then referenced from http://www.loper-os.org/?p=2842
09:30	phf	http://logs.nosuchlabs.com/log/pest/2023-02-11#1023047 << i actually sent this last night as part of the conversation that was happening, but it got lost in aether, and only bumped because i sent another message in the morning
09:31	dulapbot	Logged on 2023-02-11 09:26:38 phf: signpost, is book/paper hoard from cause or towards a purpose?
09:31	phf	i guess instead of spamming with addresscasts it would've been more useful for stations to periodically emit prods
		↖
09:33	phf	asciilifeform, is the idea of threading that you can just explicitly say "netchain of this message is this other message that i'm `responding` to"?
		↖
09:35	phf	i think you suggested somewhere that you don't do "response" as such, and just add netchain visualization to the client. have you thought about adding an explicit flag for "this is a response" messages?
		↖
09:38	phf	i recon it's not too hard to make a client be smart about it, even without an explicit "response" flag. if you're within some arbitrary netchain skip limit (5-6 messages), then the client can feel free to show an antecedent message as a "hint"
09:38	signpost	might as well answer though. I put the hoard together because I can’t predict later what I might want to read, and expect to have further impositions of control over to what I have access. hoard gets read, but I have far more than I will likely finish.
09:39	signpost	got plenty of dead tree if they cut the power, and plenty of ammo if they cut further.
09:40	phf	so it is towards a purpose? not saying that's bad, just trying to see if hoarding can be framed as anything but
09:41	signpost	drives plenty of other experiments in self-sufficiency, like self-hosting openstreetmaps. will post more of these things in time.
09:41	signpost	the purpose/cause distinction gets murky in cases like this involving bets about the future
09:43	signpost	but I wouldn’t argue against someone saying “dude that’s just your religion, and you’re carefully describing it in reverse”
09:46	signpost	one can dig for the cause of anything. Aesop writes the ant and grasshopper because of the looming eschaton, say.
		~ 40 minutes ~
10:26	signpost	one question is whether the object's there already visible to a john of patmos. rest of us catch up later.
10:28	*	signpost been chewing on that book a lot lately, and not because "eee ww3". thing might be the picture of all* world-collapses, and a map through them.*
10:28	signpost	should say *just because.
		~ 1 hours 45 minutes ~
12:13	asciilifeform	http://logs.bitdash.io/pest/2023-02-11#1022968 << currently not specified when, precisely, emit prods. oughta be periodic, i.e. some % of what'd otherwise be 'ignores'
12:13	bitbot	Logged on 2023-02-11 09:31:18 phf[jonsykkel]: i guess instead of spamming with addresscasts it would've been more useful for stations to periodically emit prods
12:14	asciilifeform	http://logs.bitdash.io/pest/2023-02-11#1022969 << correct.
12:14	bitbot	Logged on 2023-02-11 09:33:31 phf[awt\|deedbot]: asciilifeform, is the idea of threading that you can just explicitly say "netchain of this message is this other message that i'm `responding` to"?
12:14	asciilifeform	http://logs.bitdash.io/pest/2023-02-11#1022970 << iirc brought this up previously; concluded that not need explicit flag
12:14	bitbot	Logged on 2023-02-11 09:35:42 phf[awt\|deedbot]: i think you suggested somewhere that you don't do "response" as such, and just add netchain visualization to the client. have you thought about adding an explicit flag for "this is a response" messages?
12:17	asciilifeform	http://logs.bitdash.io/pest/2023-02-11#1022964 << asciilifeform certainly keeps warez hoard (the proverbial 'over9000 scans no one read'(tm)) and will certainly add it to pest fileshare when we've the latter, but raw hoards aint imho particularly useful as such
12:17	bitbot	Logged on 2023-02-11 09:29:25 phf[awt\|deedbot]: signpost, is book/paper hoard from cause or towards a purpose?
12:18	asciilifeform	it's something one 'mines' a) serendipitously, in spare time b) when actually investigating sumthing
12:20	*	asciilifeform recalls u. eco's answr to common q 'didja actually read yer 1e5 bookz', 'lolno, wai would i keep'em around if already read'
		↖ ↖
12:21	signpost	yup. omnia vanitas, also.
12:22	signpost	amateur librarianship is better than netflix and rotgut
		~ 4 hours 26 minutes ~
16:48	unpx	http://logs.bitdash.io/pest/2023-02-10#1022960 <<< yes, it should, but I cannot find a suitable structure for a catalog because it's either too vague or too rigid.
		↖