flancian/garden
0
0
Fork 0
mirror of https://github.com/flancian/garden.git synced 2026-08-08 07:26:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

autopushed

Browse Source
This commit is contained in:
Flancian
2022-10-23 21:07:41 +02:00
parent 321d992931
commit 1246b97892
1 changed files with 12 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
journal/2022-10-23.md
+12 -6
View File
@@ -21,15 +21,21 @@
- [x] buy automatic feeder - [x] buy automatic feeder
- [ ] book appointment with the veterinary - [ ] book appointment with the veterinary
- #push [[2022-10-24]] - #push [[2022-10-24]]
- turns out it's phone only! call [[tomorrow]] - turns out it's phone only! call [[tomorrow]]
- [ ] write - [[agora doc]]
- [ ] edit - [ ] edit
- [ ] write - [ ] write
- [ ] edit - [ ] edit
- [ ] write
- [ ] write - [ ] write
- [[catharsis]] wise
- went back to [[flaneur]] in [[merveilles]] after more than a year; it felt nice to be back.
- I want to catch up with some threads there
- [[agora development]] - [[agora development]]
- [ ] ship one improvement? - [ ] ship one improvement?
- auto pull social after some seconds? - auto pull social after some seconds?
- auto pull stoa in empty nodes? - auto pull stoa in empty nodes?
- [ ] bring up twitter bot - [ ] bring up twitter bot -> [[fix bot for ivo]]
- it was up, for some reason Ivo's post is not being seen. might need to write a 'scrape one user' "one-shot" mode -- maybe doing per user timelines is actually a good idea. - it was up, for some reason Ivo's post is not being seen. might need to write a 'scrape one user' "one-shot" mode -- maybe doing per user timelines is actually a good idea.
- this is not the first time the bot has issues with Ivo's posts. I have no idea why they're not showing up in the bots' timeline -- according to the Twitter API anyway. The bot is following Ivo, I checked.
- writing a [[one shot]] mode which takes a timeline to scrape+react to (if we haven't reacted previously) sounds like a reasonable next step at this point; it'd also make [[catch up]] better to have this code.