Skip to content
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

Parsing Issue #31

Closed
mrkrndvs opened this Issue Jan 17, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@mrkrndvs
Copy link

mrkrndvs commented Jan 17, 2019

For the last week or so I have been having issues with parsing sites. Where I was getting some information in the past, I am not getting very little.

For example:

https://wiobyrne.com/the-case-for-anonymity-online/ produces
{“type”:”entry”,”syndication”:”https://medium.com/@wiobyrne/how-to-respond-to-trolling-behaviors-c27d269330e4″,”post-type”:”note”}

Organizational Agility
{“type”:”feed”,”uid”:”https://dculberh.wordpress.com/2019/01/13/organizational-agility/#page”}

> Weeknote 02/2019

{“category”:[“weeknotes”,”weeknote”,”work”],”type”:”entry”,”post-type”:”note”}

I have this strange feeling that it is not Parse This that is the problem, but it is where I am noticing the issue.

@dshanske

This comment has been minimized.

Copy link
Owner

dshanske commented Feb 10, 2019

On the first one, look at it in an MF2 parser. That is what is there.

Same on the second one. I have fallbacks for OGP parsing, but not when there are some microformats...even if empty ones. Should look to shift over in cases like this.

@dshanske

This comment has been minimized.

Copy link
Owner

dshanske commented Feb 16, 2019

Resolved. The HTML parser tries earlier in the process.

@dshanske dshanske closed this Feb 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.