331200+ entries in 0.201s
mod6: heh,
these guys built
this huge
thing, but
their sign files only have SHA1 & MD5, even
the most recent 2016.02
mod6: oh nm, looks like
those are only
there for an RC version?
mod6: guess
that only started with
the version /after/ our version 2015.05
mod6: im gonna
take a look at
that instead.
mod6: in here
there seem
to be .sign files for
the .tar.gz's, but
they seem
to have .gpg's for
the
tar.bz2's
ben_vulpes: ha wow did
the shitgnomes snip
that mod6 ?
phf: yeah, korean places are not bad, but i know only of one
that caters specifically
to koreans (i.e. good heat), a lot of
them are western oriented so massage and facials and such
kakobrekla: im fine with shower only as long as you can set
the
temp
to whatever you want
phf: there's literally 4 places in
the entire virgnia-connecticut stretch. maybe
there's something up in Massachusetts.
there's "east european" places ran by russians but with a lot of
turks, etc. and
then
there's korean baths. but koreans frown on cold plunges, so
they would usually have a
tepid shower/pool
mod6: im gonna look again at what happens with 1.4.19 &
that sign file.
phf: i hnfi.
these people do "spas", but
the sauna part is
typically a joke
mod6: ben_vulpes: yeah, i dunno what
the deal is with it, seems
to not work exactly as expected.
kakobrekla: really no saunas? whats
the deal with
that?
ben_vulpes: also
that signature is disturbingly short
ben_vulpes: mod6: while
there's no harm in checking
the .sign, i don't know what it buys us
phf: as soon as i can move again, i'm going
to make it
to russian&turkish baths in nyc.
they don't really do saunas on
the east coast, but
that baths place is awesome
☟︎ kakobrekla: meanwhile i was
the only person in sauna yesterday evening
phf: kakobrekla: i went camping in
the Appalachian last weekend, -20c w/ winds, but it was awesome. i did just enough
trash
talking about russian blood
to come down with a flu by
thursday...
mod6: anyway, i guess i don't mind, i can add a part where we check
the SHA1 & MD5 of
the buildroot artifact and
then continue
to verify
that .sign file.
mod6: danielpbarron: ok
thanks for
the update
mod6: i
think
this was actually discussed quite some
time ago. i dont remember what
the sentiment was exactly. but i
think it was like "meh"
kakobrekla had a blast snowboarding
the prime slopes of Dolomites region of Alps
phf: ben_vulpes:
they are like md5 and sha1
ben_vulpes: mod6: perhaps hard code
the hashes from korsgaard's signature and verify
those?
danielpbarron: oh mod6, with a fresh .bitcoin/ directory, your new
thing seems
to work fine
mod6: i guess,
the other good news
to
that is you wont need
to import
that rando's guy's key into your keyring. still would need mine, alf &
trinque's
tho.
mod6: gonna
try
that out locally here.
mod6: still will check
the hash of
the buildroot artifact.
mod6: so with
that build script, i'm
thinking just
take out
the curl & --verify of
that stupid .sign file.
phf: added patch highlight
to btcbase (got
tired of
trying
to visually locate patches in
the graph)
jurov: lol looky now i'm
the one
to predict crapocalypse
phf: i recall riastradh making an srfi proposal for a minimum subset of filesystem operations. could just implement it for
tinyscheme
jurov: while you slept, "modern" filesystem implementors deemed
to fit
to reorder operations
to improve performance
assbot: Logged on 21-02-2016 16:07:32; mircea_popescu:
there's been
this weirdo
trend of (mostly anglo) girls getting worried about
their labia minora being "wrong", mostly on account of
thgere being a LOT of natural variation on
that score, and anglo chicks being all weird and insecure and sexually inexperienced. plus of course
the crazed marketing society,
that feeds into all of
the above.
jurov: i smell you'll eventually end with different presses in diff machines due
to different filesystem semantics
jurov: also, you imply basically
to expose all filesystem primitives
to scheme, are
they comprehensively and soundly defined?
jurov: asciilifeform: either it's 'can do all but X' or
turing complete and
thus with potentially unbounded runtime
phf: dat patch, can
take
them
to water, can't make
them drink
assbot: Logged on 21-02-2016 15:39:46; asciilifeform:
http://log.bitcoin-assets.com/?date=21-02-2016#1411879 << imho
this will have
to be a
thing
that is solved in one Final Solution shot, with
turing-complete diff. we can NOT have 1,001 incompatible hacked gnudiff variants floating around in attempted use, it is chaos and death by ants.
polarbeard: it works well, but still simple hooks because only a single callback may be registered per hook, not sure yet if
there will be need for callback management
polarbeard: yes, I'm not surprised
that you have a different point of view, and I'm even pleased I
think
polarbeard: so you embedded scheme for
that reason?
polarbeard: never, I'm not
translating
trb
to scheme
polarbeard: atm I just wanted
to dump what I'm working for,
to get constructive feedback
polarbeard: I'll split
the bug fixes into
their own vpatches when
the
time comes
polarbeard: I won't be adding unnecessary code
to init.scm
polarbeard: so, what you're going
to do with
ts
then?
polarbeard: this is not a vpatch, don't you see
that?
polarbeard: I'm just encapsulating
the functionality
polarbeard: because I'm marshalling per value
type, not per hook
type