New Commenting Policy
I've added a new commenting policy to combat our OpenID-based spammers. It's a whitelist based on FOAF. There will be more about it in this space as development moves forward, so stay tuned if you'd like to know how to be placed on the whitelist.
As for specifics, the whitelist implementation is a Drupal module that reads a list of OpenIDs from an externally generated set every hour. The user's OpenID is checked against the whitelist at login time, and matches are allowed to proceed with account creation, commenting, etc.
Potential improvements:
- a UI for settings
- better database transaction flow, particularly for error handling
- viewable whitelist
Feel free to contact me if you're interested in the module portion of this equation for use with your own openid.module (again, it does none of the whitelist generation).
This is just great, Ryan! I'm psyched to see people actually using FOAF, aside from just publishing FOAF files and browsing our networks of friends. Can't wait to see what happens as this work grows and spreads around the Web.
Danny
Login works for me now—clearly, otherwise I wouldn't have been able to post this! My only comment on the process of logging in is that when I use the login link on this post I get directed to the breadcrumbs homepage after the login process rather than back to this post again; it'd be handy if the login process saved that state for me.
Good friend Patrick Hall has the compunction to throw Unicode into any new toy that he has, and I'm trying to make it a habit to follow suit. Therefore...
➔ ΰ㡈⃟ⓞ̇
⍾ ⍾ ⍾ ⍾ ⍾ ⍾ ⍾ ⍾
𝓬𝓪𝓷 𝓪𝓷𝔂𝓫𝓸𝓭𝔂 𝓻𝓮𝓪𝓭 𝓽𝓴𝓲𝓼?
Thanks,
--sbp
That's what sbp gets when he tries to login; perhaps there's a real problem somewhere on his end, but the URL he's using is fine: http://inamidst.com/
Are there any clues in the logs?
See #swig discussion for context.
