2026-07-07 (Tuesday) Journal
Day summary: Today’s RSS activity: 1 item(s) from infosec.exchange including “Working on tempolocus, a tool that analyses time-series activity patterns to infer a user’s likely location.In @ail_project, we work with a large volume of social-network time series. Estimating users’ locations from these patterns is often a manual task.I prototyped a Python module that combines potential locations with yearly activity signals, such as vacation periods and public holidays. It is still at an early stage, but it is already producing promising results with weekly time series.Ideas, feedback, and improvements are welcome. tempolocus is planned for integration into AIL Framework 7.1.#cybersecurity #threatintelligence #threatintel #opensource https://github.com/ail-project/tempolocus”.
Hourly activity:
hour 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23
pulse . . . . . . . . . . . . . . . . @ . . . . . . .
count 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
Working on tempolocus, a tool that analyses time-series activity patterns to infer a user’s likely location.In @ail_project, we work with a large volume of social-network time series. Estimating users’ locations from these patterns is often a manual task.I prototyped a Python module that combines potential locations with yearly activity signals, such as vacation periods and public holidays. It is still at an early stage, but it is already producing promising results with weekly time series.Ideas, feedback, and improvements are welcome. tempolocus is planned for integration into AIL Framework 7.1.#cybersecurity #threatintelligence #threatintel #opensource https://github.com/ail-project/tempolocus
- Source:
infosec.exchange - Time:
16:02:25 - Summary: adulau@blakley:~/git/tempolocus$ python3 -m tempolocus samples/weekfull-chan1.json –format text -n 10 –holiday-profile public-worker input_type: weekly_timeseries confidence: 0.220 activity_type: mixed-time (0.009) assumptions: - Hourly buckets are interpreted as UTC; timezone candidates are offsets that make the activity look locally human. - Weekly data cannot distinguish all IANA zones sharing the same offset, and daylight saving time is not inferable without dates. probable_countries: 0.970…