-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update mf2py (waiting for next release) #828
Comments
yes! this should fix or at least help with snarfed/granary#145 and snarfed/granary#142 too. bridgy is pretty particular about mf2py's behavior, and some new changes are nontrivial, eg it adds |
for snarfed/bridgy#828, #145, #142, etc.
the the good news is, it sounds like everyone agrees that we should revert that part of the spec, so hopefully I'll be able to upgrade to the next mf2py release! |
woo, thanks to @kartikprabhu for implementing the implied name change! microformats/mf2py@71997eb. can't wait for the next release! |
fixes #142, fixes #145, fixes snarfed/bridgy#756, for snarfed/bridgy#828
details in #828, snarfed/granary#142, snarfed/granary@a989c3e, etc.
details in #828, snarfed/granary#142, snarfed/granary@a989c3e, etc.
details in #828, snarfed/granary#142, snarfed/granary@a989c3e, etc.
deployed this just now with https://github.com/snarfed/mf2py/tree/all , which has a number of pending mf2py bug fixes, eg microformats/mf2py#115 and microformats/mf2py#118. 🤞 |
rolling back, it's currently crashing on microformats/mf2py#108 . e.g. https://brid.gy/log?start_time=1532441945&key=aglzfmJyaWQtZ3lyFgsSB1R3aXR0ZXIiCXNjaHVzc21hbgw |
added microformats/mf2py#114 and it's no longer crashing. mf2py at head (with a bunch more unmerged bug fixes) is now live on bridgy prod. |
closing, yay. thanks again @sknebel! |
Exciting new features! E.g. improved implied name handling, which keeps cropping up. (e.g. http://twtr.io/1eNFR0C3voG )
The text was updated successfully, but these errors were encountered: