This unfortunately broke BPIP's parsers, since (Recently) is not a valid datetime. We'll try to get it corrected as soon as possible.
If the parsed value is "(Recently)" you can handle it in some custom way.
Or if the parsed value is not in the expected datatype, you can handle the problem in a particular way. You can do the same for any other input received from any third party.
It seems when other members are probably going on with their life activities, PowerGlove is definitely busy making patches. Once again thank you PowerGlove for this addition.
Too bad he only gets merits, and not tens of thousands of bitcoins. :/
If you are referring to the bitcoin theymos received years ago, the USD value of that bitcoin was only a few hundred dollars, probably well below the FMV of the time necessary to run the forum plus the operating costs. He happened to keep that money in bitcoin and see massive capital gains.
Anyone else, yourself included could have just as easily bought a few hundred dollars worth of bitcoin at the time, and would have seen similar gains if you held on for all these years.
So if I monitor a profile that was last active more than 3 days ago, and it's status switches to "(Recently)", I know it's became active right at that moment.
They will have been active between the last time you looked at the profile and the current time. Unless you are constantly refreshing their profile, you won't have an exact time.
Also, if profiles are refreshed too frequently, or if what you are describing is being used to pinpoint the date/time of last activity too frequently, the last active date can be cached, so it will only ever update every x amount of time.
I'd like to correct a misconception that I keep bumping into before it becomes too widespread:
While most of the patches I've posted to date were done on a free-time/voluntary basis, theymos and I did recently come to an arrangement, and I am now paid for the work I do on Bitcointalk.
Good for you!
