Pulling LW tags sometimes pulls an old version
Closed this issue · 8 comments
https://aisafety.info/questions/8C7W/
https://docs.google.com/document/d/1CoeLLw-Rz8CT4FLO5KkngSDrR8-px98WBrC1f7ykd1w/edit
https://www.lesswrong.com/tag/optimization/history
Note that it pulls from something that is close to what is in the history, but there does not seem to be an exact match. I have not tested if it does it all the time or only this once.
I am also told that we currently cannot pull tags from the Alignment Forum, this would be a nice fix while we are at it.
Now it just pulls nothing
There are a couple of things going on here.
- The LW system has changed over the years, and some tags are using an older version for storing data - I updated the code to use a fallback to fetching the html rather than markdown for these
- Alignment forum tags should now be supported
- The Coda contents only get updated when a gdoc changes. This means that when an editor supplies a tag link to use as content, then it will be fetched once and left alone until that gdoc file changes again. This is to say that it doesn't track LW tag updates. It would be possible to implement that, but it would be a lot of work so I don't want to right now... That being said, if you think it valuable it can certainly be done
add a space or whatever to any tags you think should be updated. Alternatively, you can manually force a full re-parse of all documents here: https://github.com/StampyAI/GDocsRelatedThings/actions/workflows/run_parser.yaml (click "Run workflow" and change "Whether to force a reparse of all answers" to "true")
This makes sense, thanks for the explanation. This being said, I see that you changed the tag to point to alignmentforum.org, which afaik does not work, which is why we were using LW ones. Was there a reason for that?
Also I think that the workaround for re-parsing that make a lot of sense, and making it automatic is low priority.
Are you sure about it not working?
(it wasn't, but I fixed it earlier)
I thought I saw it as not working, but it seems ok now. Looks good, I will update the team on the fact that we can now use the AF tags.