tynan

as many tokens as it takes. building

[tynan @training_loop]

@marchoeffl yup. maybe i should talk about this more but content deduping allows us to drastically cut down the total reads to s3 from a node. plus it’s much faster

[tynan @training_loop]

eventually everyone gets the same idea:

s3 is cheap, durable, and infinite. so why not put your filesystem on s3?

here are some rules for how do to it

[tynan @training_loop]

@metcalfc you should have seen our first attempts at trying to do gc on this thing

[tynan @training_loop]

@wgm752 i can map petabytes of data but can’t find my keys

[tynan @training_loop]

@aniketmaurya @madhavjha still cheaper than deleting user data

[tynan @training_loop]

@gp_0013 @Melt_Dem return of the lich king

[tynan @training_loop]

same idea for TRIM.

a guess trim records two things (a) the hole in the disks own logs which the guest ack waits on and liveliness note in the host's gc logs.

space accounting should never sit in the write path.

[tynan @training_loop]

the 'fun' part of content addressing is that dead names can come back, i.e. a new write can hash to an object you were about to delete.

so anything that reuses a key resets the time to retirement.

[wyatt marshall @wgm752]

really fun blogpost from the Halluminate research team: https://t.co/n4DPOwtrJB

we had frontier open and closed source models choose between yes or no on all the California state propositions from last week's election

the results will surprise you 👀

great work team

[tynan @training_loop]

@lotusfracture they train on the fourier series of your data

[tynan @training_loop]

@technoHimbo you need to reallocate some of your polycule spending to shrimp welfare research