wordpress-webmention icon indicating copy to clipboard operation
wordpress-webmention copied to clipboard

Implement Avatar Store in Branch 5.X

Open dshanske opened this issue 4 years ago • 11 comments

The other was based on 4.X. Creating this pull to actually put it into 5.X for various reasons.

dshanske avatar May 15 '21 18:05 dshanske

I opted to work on this off of Branch 5.X instead of 4.X because in the older code, we stored author url in a meta property. In the new webmention storage philosophy, we store it properly in author URL and stop trying to be backward compatible with pingbacks.

So, it's better to key things to the author URL, whatever it is, as that is what we consider to be their identity.

dshanske avatar May 15 '21 20:05 dshanske

The code also now removes the gravatar caching code. Instead, it retrieves even the generic default avatars from gravatar and caches them per author url. It also rewrites the gravatar URLs to the default cache size.

dshanske avatar May 15 '21 20:05 dshanske

@pfefferle The quality check is failing over md5 hashing. I could go to sha256, but it seemed overkill. Thoughts?

dshanske avatar May 15 '21 20:05 dshanske

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 4 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

sonarqubecloud[bot] avatar May 29 '21 14:05 sonarqubecloud[bot]

@pfefferle Do we want to try and update and merge this?

dshanske avatar Feb 09 '22 23:02 dshanske

What do you think about decoupling the storing part from the main avatar class, like we did with the handlers? So that it is possible to add new storing classes, like a db store, a CDN store or...?

pfefferle avatar Feb 10 '22 07:02 pfefferle

I think I am fine with that

dshanske avatar Feb 10 '22 13:02 dshanske

Nice! So let's merge the open PRs then and then I will try to change the structure a bit (maybe add namespaces) to prepare different avatar stores?!?

pfefferle avatar Feb 10 '22 17:02 pfefferle

Going to tackle refreshing this next as discussed for namespacing so we can merge it

dshanske avatar May 30 '22 16:05 dshanske

Shouldn't we get comment Display ready first? To have the current feature set ready and to have the 5.0 ready to launch?

pfefferle avatar May 30 '22 16:05 pfefferle

Shouldn't we get comment Display ready first? To have the current feature set ready and to have the 5.0 ready to launch?

Good point. I'll redo this one later. Just wanted to close out the PRs. But the display does have a higher priority.

dshanske avatar May 30 '22 16:05 dshanske

@pfefferle I know you are leaning toward an external solution but would still like to pursue this even if it is off by default

dshanske avatar Apr 08 '23 20:04 dshanske