That is the easy part:
.oO° (¬ ) +1593187261.426237 °Oo.
will bring you just to 2020-06-26T12:01:01.426237. It is about one year in future.
A bigger problem is it will get executed on storing or on consuming the tag? And then we will still need some microseconds to implement the backend.
I'm against executing on consuming because then we will be shuffled around every time somebody consumes a time travel tag. On the other side, :S imagine a really evil person put a script in the crontab storing each 5s the same time. Although, we need to investigate if the cron script still will work with the time travel.
So after thinking another second, I think time travel is not the best option, we should discard it.
How about time stretching? Because at least I'm only interested in more hours per day. I try still to reduce sleeping hours to win some time and then I burn it with ideas like that :/ shame on me
We should work on that! :D
Have a great day!
Yeah, I don't know, what sort of markup do we put on time travel? :P
You too :D
That is the easy part:
.oO° (¬ ) +1593187261.426237 °Oo.
will bring you just to 2020-06-26T12:01:01.426237. It is about one year in future.
A bigger problem is it will get executed on storing or on consuming the tag? And then we will still need some microseconds to implement the backend.
I'm against executing on consuming because then we will be shuffled around every time somebody consumes a time travel tag. On the other side, :S imagine a really evil person put a script in the crontab storing each 5s the same time. Although, we need to investigate if the cron script still will work with the time travel.
So after thinking another second, I think time travel is not the best option, we should discard it.
How about time stretching? Because at least I'm only interested in more hours per day. I try still to reduce sleeping hours to win some time and then I burn it with ideas like that :/ shame on me