Event JSON
{
"id": "978aa97bdf513d074c30730d420afab9c67458d9f9c282dc03b823bfcd4313de",
"pubkey": "b67b88d83988dcf25b2c1932b3817a5be6565d09933ffa6d21ea3669d5f5adc8",
"created_at": 1732083245,
"kind": 1,
"tags": [
[
"p",
"9d6742ff43235eb568c0bc55fa8acf7e004ca06a7c9e0c3da2b089a098b769b9"
],
[
"e",
"40d66382644966960f51ecdfd07e86b934df92b80527d08754c709a393c73790",
"",
"root",
"9d6742ff43235eb568c0bc55fa8acf7e004ca06a7c9e0c3da2b089a098b769b9"
],
[
"proxy",
"https://mastodon.social/@puhuri/113513807593742442",
"web"
],
[
"proxy",
"https://mastodon.social/users/puhuri/statuses/113513807593742442",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.social/users/puhuri/statuses/113513807593742442",
"pink.momostr"
],
[
"-"
]
],
"content": "For important cases, my crontabs live in a file under versin control. Then I just I replace it with 'crontab crontab-for-this'. \nAFAIK the edit option existed in 4.3 BSD (first time I used cron) but for some reason I opted using file under my home directory. Could be that the default editor was vi (or ed) and using emacs was much easier.\nBut yes, for odd jobs in random computers I just kick crontab -e.\nnostr:npub1n4n59l6ryd0t26xqh32l4zk00cqyegr20j0qc0dzkzy6px9hdxusru6ax6",
"sig": "2300684813a3bdd43d7dc073f7df3ff9d8355277ae107ffd760390555436eb01216497119904d49df7622e97c572e8dfc7a9568742d854f002aad7379c9e2960"
}