#timeclock — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #timeclock, aggregated by home.social.
-
CVE Alert: CVE-2021-47966 - Timeclock - PHP Timeclock - https://www.redpacketsecurity.com/cve-alert-cve-2021-47966-timeclock-php-timeclock/
#OSINT #ThreatIntel #CyberSecurity #cve-2021-47966 #timeclock #php-timeclock
-
CVE Alert: CVE-2021-47966 - Timeclock - PHP Timeclock - https://www.redpacketsecurity.com/cve-alert-cve-2021-47966-timeclock-php-timeclock/
#OSINT #ThreatIntel #CyberSecurity #cve-2021-47966 #timeclock #php-timeclock
-
CVE Alert: CVE-2021-47966 - Timeclock - PHP Timeclock - https://www.redpacketsecurity.com/cve-alert-cve-2021-47966-timeclock-php-timeclock/
#OSINT #ThreatIntel #CyberSecurity #cve-2021-47966 #timeclock #php-timeclock
-
CVE Alert: CVE-2021-47966 - Timeclock - PHP Timeclock - https://www.redpacketsecurity.com/cve-alert-cve-2021-47966-timeclock-php-timeclock/
#OSINT #ThreatIntel #CyberSecurity #cve-2021-47966 #timeclock #php-timeclock
-
CVE Alert: CVE-2021-47966 - Timeclock - PHP Timeclock - https://www.redpacketsecurity.com/cve-alert-cve-2021-47966-timeclock-php-timeclock/
#OSINT #ThreatIntel #CyberSecurity #cve-2021-47966 #timeclock #php-timeclock
-
The Time Clock Has Stood the Test of Time https://hackaday.com/2026/01/08/the-time-clock-has-stood-the-test-of-time/ #WillardLeGrandBundy #DanielM.Cooper #OriginalArt #clockhacks #Bundyclock #clockingin #punchclock #punchingin #timeclock #Featured #History
-
The Time Clock Has Stood the Test of Time https://hackaday.com/2026/01/08/the-time-clock-has-stood-the-test-of-time/ #WillardLeGrandBundy #DanielM.Cooper #OriginalArt #clockhacks #Bundyclock #clockingin #punchclock #punchingin #timeclock #Featured #History
-
The Time Clock Has Stood the Test of Time https://hackaday.com/2026/01/08/the-time-clock-has-stood-the-test-of-time/ #WillardLeGrandBundy #DanielM.Cooper #OriginalArt #clockhacks #Bundyclock #clockingin #punchclock #punchingin #timeclock #Featured #History
-
The Time Clock Has Stood the Test of Time https://hackaday.com/2026/01/08/the-time-clock-has-stood-the-test-of-time/ #WillardLeGrandBundy #DanielM.Cooper #OriginalArt #clockhacks #Bundyclock #clockingin #punchclock #punchingin #timeclock #Featured #History
-
Nice little script to convert a Toggl CSV timetracking export to a timeclock file compatible with hledger.
https://codeberg.org/scy/toggl2timeclock
#Toggl #hledger #timetracking #converter #conversion #Python #script #timeclock
-
Nice little script to convert a Toggl CSV timetracking export to a timeclock file compatible with hledger.
https://codeberg.org/scy/toggl2timeclock
#Toggl #hledger #timetracking #converter #conversion #Python #script #timeclock
-
Nice little script to convert a Toggl CSV timetracking export to a timeclock file compatible with hledger.
https://codeberg.org/scy/toggl2timeclock
#Toggl #hledger #timetracking #converter #conversion #Python #script #timeclock
-
Nice little script to convert a Toggl CSV timetracking export to a timeclock file compatible with hledger.
https://codeberg.org/scy/toggl2timeclock
#Toggl #hledger #timetracking #converter #conversion #Python #script #timeclock
-
Nice little script to convert a Toggl CSV timetracking export to a timeclock file compatible with hledger.
https://codeberg.org/scy/toggl2timeclock
#Toggl #hledger #timetracking #converter #conversion #Python #script #timeclock
-
Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇
-
Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇
-
Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇
-
Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇
-
Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇
-
🚀 #annextimelog v0.8.0 comes closer to being well useable: It is now possible to search recorded events with sophisticated syntax:
> atl ls work @home this week
> atl ls last month project=myproject with note='my.*regex'Same syntax as for tracking events with 'atl tr'.
This plays nicely with data export to other formats, e.g. #hledger #timeclock
> atl ls last month -O timeclock | hledger -f timeclock:- bal -D
-
🚀 #annextimelog v0.8.0 comes closer to being well useable: It is now possible to search recorded events with sophisticated syntax:
> atl ls work @home this week
> atl ls last month project=myproject with note='my.*regex'Same syntax as for tracking events with 'atl tr'.
This plays nicely with data export to other formats, e.g. #hledger #timeclock
> atl ls last month -O timeclock | hledger -f timeclock:- bal -D
-
🚀 #annextimelog v0.8.0 comes closer to being well useable: It is now possible to search recorded events with sophisticated syntax:
> atl ls work @home this week
> atl ls last month project=myproject with note='my.*regex'Same syntax as for tracking events with 'atl tr'.
This plays nicely with data export to other formats, e.g. #hledger #timeclock
> atl ls last month -O timeclock | hledger -f timeclock:- bal -D
-
🚀 #annextimelog v0.8.0 comes closer to being well useable: It is now possible to search recorded events with sophisticated syntax:
> atl ls work @home this week
> atl ls last month project=myproject with note='my.*regex'Same syntax as for tracking events with 'atl tr'.
This plays nicely with data export to other formats, e.g. #hledger #timeclock
> atl ls last month -O timeclock | hledger -f timeclock:- bal -D
-
🚀 #annextimelog v0.8.0 comes closer to being well useable: It is now possible to search recorded events with sophisticated syntax:
> atl ls work @home this week
> atl ls last month project=myproject with note='my.*regex'Same syntax as for tracking events with 'atl tr'.
This plays nicely with data export to other formats, e.g. #hledger #timeclock
> atl ls last month -O timeclock | hledger -f timeclock:- bal -D
-
Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).
-
Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).
-
Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).
-
Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).
-
Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).
-
🚀 #annextimelog v0.3.1 has reached the absolute minimum of functionality to call it a time tracker. It can now:
· `atl track`: record past events and attach arbitrary metadata to it
· `atl ls`: list recorded events in a certain time period
· `atl rm`: delete a recorded event
· `atl sync`: sync state with :gitannex: #gitAnnex
· `atl -O timeclock ls`: export data to #timeclock (e.g. for #hledger)@alerque also put it into the #AUR² 🙂 (thanks!)
-
🚀 #annextimelog v0.3.1 has reached the absolute minimum of functionality to call it a time tracker. It can now:
· `atl track`: record past events and attach arbitrary metadata to it
· `atl ls`: list recorded events in a certain time period
· `atl rm`: delete a recorded event
· `atl sync`: sync state with :gitannex: #gitAnnex
· `atl -O timeclock ls`: export data to #timeclock (e.g. for #hledger)@alerque also put it into the #AUR² 🙂 (thanks!)
-
🚀 #annextimelog v0.3.1 has reached the absolute minimum of functionality to call it a time tracker. It can now:
· `atl track`: record past events and attach arbitrary metadata to it
· `atl ls`: list recorded events in a certain time period
· `atl rm`: delete a recorded event
· `atl sync`: sync state with :gitannex: #gitAnnex
· `atl -O timeclock ls`: export data to #timeclock (e.g. for #hledger)@alerque also put it into the #AUR² 🙂 (thanks!)
-
🚀 #annextimelog v0.3.1 has reached the absolute minimum of functionality to call it a time tracker. It can now:
· `atl track`: record past events and attach arbitrary metadata to it
· `atl ls`: list recorded events in a certain time period
· `atl rm`: delete a recorded event
· `atl sync`: sync state with :gitannex: #gitAnnex
· `atl -O timeclock ls`: export data to #timeclock (e.g. for #hledger)@alerque also put it into the #AUR² 🙂 (thanks!)
-
🚀 #annextimelog v0.3.1 has reached the absolute minimum of functionality to call it a time tracker. It can now:
· `atl track`: record past events and attach arbitrary metadata to it
· `atl ls`: list recorded events in a certain time period
· `atl rm`: delete a recorded event
· `atl sync`: sync state with :gitannex: #gitAnnex
· `atl -O timeclock ls`: export data to #timeclock (e.g. for #hledger)@alerque also put it into the #AUR² 🙂 (thanks!)
-
#annextimelog is progressing nicely. It can now:
- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnexeverything stored in a #git repo with git annex metadata. 😊
-
#annextimelog is progressing nicely. It can now:
- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnexeverything stored in a #git repo with git annex metadata. 😊
-
#annextimelog is progressing nicely. It can now:
- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnexeverything stored in a #git repo with git annex metadata. 😊
-
#annextimelog is progressing nicely. It can now:
- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnexeverything stored in a #git repo with git annex metadata. 😊
-
#annextimelog is progressing nicely. It can now:
- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnexeverything stored in a #git repo with git annex metadata. 😊
-
Finishing the day with the most basic feature a time tracker can possibly have: recording a period of time. ⏱️
This is #annextimelog, the :gitannex: #gitAnnex based time tracker I'm making in the hope that it'll suit me better than #timewarrior or plain #hledger #timeclock.
I love adding configurably crazy amounts of debug output (-vvvvvvvv 😉) to my programs and @textualize's rich makes this a bliss!