i bet if you mmap'd a big file and then dirtied a ton of pages and then exited and watched the file on disk, you'd see writes occurring after the process exits as well.
i would say, be generous with yourself in terms of tracking showing up at all since that alone is huge (and most important for sustaining the behavior). if you notice that you're slipping and showing up late too often, maybe create another habit for being on time?
i don't understand the rationale behind cheating one's own self improvement journal. what's the end game?
Self-destruction, via small acts of self-sabotage.
Next day, your inner critic and saboteur tell you something along the lines of: "You shouldn't go today - you're tired, there's so much work that you should do instead, and you're not even doing the gym actually/properly (AGAIN), just look at yesterday, you couldn't even do 25 min, you've cheated and have now tainted it". Even though it was the same exact voice that led you to do it yesterday.
i don't think that computer vision gates or even an ai agent trying to enforce accountability are going to help all that much in that case. maybe try a therapist or a real-life accountability partner.
I’ve tried it all. No real life partner can be there on the hour (most accountability partner systems work on a daily/weekly basis). “Friends” definitely don’t work.
An automated measurement system is the way to go. Like the poster above you said, the “cheating” rarely happens in a binary Yes/No situation or me going into a log and editing it (that would obviously be silly). It happens in the rolling measurements, the 22mins vs 25 mins hard day gray zone situations
yeah in that case, use a binary for "did you do it that day?" and a measure for "how much of it did you do that day?". loop habit tracker supports both, i bet this one does too. a built-in stopwatch to make time tracking specifically easy would be cool.
i have done things like "do x at least once three times a week" and then had a separate counter for how many times. it's good to track intensity or progression, but i think the most value comes from "did you do it at all that day?" and then sticking to a plan that involves n days a week.
the finer grained tracking can contribute to "i am not on target, so maybe it doesn't matter" sort of thinking where maybe the most valuable thing is "i am setting time aside n days a week and sticking to at least attempting the activity on that schedule."
i wonder what they're all up to. i imagine some are scraping datasets for pre-training, others are probably real-time scrapers looking for security bugs, even more still are agents working on coding tasks and looking at the kernel. also interesting to think about solutions: does everything need to be optimized now for weird access patterns that proliferated ai creates? do the ais need to have behavior trained in to be better netizens? is this the end of anonymous browsing and the beginning of an era where one has to attach an identity to all requests? or the end of community hosted free information services more broadly?
i still think this should be solved at the protocol level. if you want to access the adult stuff, you have to staple a non-identifying zk-proof-of-age to your http/spdy/etc requests, otherwise it all just operates as usual.
The default state should be adult. Kid devices should have something special on setup that makes them kid devices.
Or even better, don't have anything like that at all anywhere other than in front of the screen. I really don't see how it is a good thing for a six year old to interact with the Internet in any way.
this is exactly what these weird operating system age tracking laws are codifying which is terrible. it forces consumer operating systems to become trusted computing bases that don't work for the consumer.
upgrading to adult content when a credential is provided at the protocol level rather than forcing the operating system to track the state means that consumer operating systems don't have to be secured against their own users.
san francisco had that cool, edgy, gonzo art scene happening in the 90s. also survival research laboratories and their famous pitching machine, the omnicircus, chicken john, laughing squid, critical mass/commute clot, santarchy/santa con (before it became the weird frat thing it is today). similar things in brooklyn in the '00s like the madagascar institute, black label bike club, idiotarod, etc.
in the 2000s, there was kind of an interesting tech meets countercultural art thing where a lot of the more interesting tech people would pour their disposable income into interesting burning man art projects (nimby's ddi, jabba's sail barge) but it does seem like in recent years with the real sf affordability crisis that came with internet business actually taking off the creativity went down and the money seeking people showed up. i guess that's also true of sf (and brooklyn) more generally.
it was a fun time. i was a swe intern in the mid 90s and would marvel when the engineering team would disappear to the desert for a week and come back with colored hair. my boss drove a psychedelic school bus to work sometimes. in south of market on 6th street in sf, there was a building that had furniture welded onto the exterior like it had all come to life and was trying to escape the building.
the internet is home to plenty of predatory cesspits, but the real stuff is still there too. it's not as convenient or addicting as content that doubles as a funnel for the ad machines, but the real spaces and media that aren't dominated by the advertising industrial complex still exist- just like in other forms of media that preceded the internet.
last time i built a crud app (oh maybe about 24 years ago) i made it a point to do this. i remember watching the payroll people fly through their terminal mode vax vms applications with such speed and dexterity that it would make any unix admin well versed in the art of the command line blush and it made me think "oh yeah, all these 90s point and click guis got it all wrong. if people are required to make heavy use of a system at work, they would prefer a learning curve followed by speed, comfort and dexterity over an easier learning curve that trades dexterity for discoverability."
it was a webapp framework, but... all browsing/listing screens included row ids and a focused text box- so that typing the row id and enter would select. all action buttons had an underline to signify which ctrl-shift hotkey triggered them. all edit screens defaulted focus to the first editable textbox and at no time was the mouse actually necessary. finally, load times were optimized to target 75ms.
amusingly, the user feedback was "the keyboard control is pretty good but can you please make it faster."
what i thought was chrome ended up being critical to the users not being miserable.
reply