twofactorauth
twofactorauth copied to clipboard
A "Recently Added" section?
A section on the website that shows sites that recently add 2FA. Do you think this would be beneficial? I'm thinking something like a page/section that lists sites that recently implemented 2FA, since the last time the website was updated or in the last week/month. Might be beneficial if people want to come back to the website to see if there are sites they use that now implement 2FA.
I think it's not that simple to implement because the site a fully pre-rendered static HTML. The source of data are yaml files which do not record timestamp of when entries were added. Unless I'm missing something, I think your best bet right now is to simply look at repo's changelog at https://github.com/jdavis/twofactorauth/pulse
@mxxcon Yeah, I couldn't figure out a way to implement this. That's a pretty good workaround, but I don't think the website's users should have to look at github. Then again, I'm not sure people other than me go to the site and look for this info.
I've never used the GitHub API before, but maybe there's a way to do this by pulling closed issues with a certain label? I don't see how this would be accurate though.
EDIT: Or maybe checking merges to master and figure out which ones update 2FA implementation info for sites?
As far as Jekyll variables go, we do have these available to use: https://help.github.com/articles/repository-metadata-on-github-pages but it doesn't look like there's anything useful there.
If we wanted to use the API, we could just do it client side, which would be neat. There's a JS library for that: https://github.com/k33g/gh3 Although it doesn't look like it can filter issues which isn't a problem, we'd just have to write our own.
The idea of using a specific label for it is interesting and probably the best way to handle it. We could have a little section somewhere that just lists the last sites added in the last week based on a issue tag called like "update" or something.
If we did this, I'd consider it a solution to #99 as I like the idea of the JS client-side as opposed to RSS.
Doing it client side sounds great.
Using a specific label might also be useful if a site adds/removes a 2FA method. Not sure if this happens. If so, maybe instead of "Recently Added" it should be called "Recently Updated."
Rezzing this thread. Perhaps a hook to trigger a script when gh-pages is committed to to generate a table of Recently Added/Modified?
This could just be done client-side, tracking the last visit date and asking the GitHub API for changes, then rendering a small table at the top. (Or highlighting the new entries, at the very least)
I feel like doing it client-side would mean lag for the users.
It could be optional, small and asynchronous. Nothing using Angular.js or the sort, just basic JavaScript that doesn't block the page loading.
@smiley if you have an idea how to do it, mind throwing together a POC to show it'll work?
What if we combine this idea with #1368? We could have an icon for a recently added list.
As part of this request, it would be nice to have a date field added to each company. One thing I would like to do is graph a trend of companies adding 2FA to their service. Combined with the categorization of industry, we could get some interesting trending stats.
@SecuritySimon but the date when a site is added here != date when a site enables 2fa.
@mxxcon understood, but most places announce when they add 2FA, so in theory it should be data available at the time of updating twofactorauthy.org. It also doesn't need to be uber accurate, error of a week still allows for tracking of trends.
That's true for big sites but not for small sites (something which we have a lot of in our list.)
@SecuritySimon Have you considered mining the git log? GitHub also has some nifty graphs that might tell you the trend; for example, https://github.com/2factorauth/twofactorauth/graphs/commit-activity
Good idea, I might try and use the commit activity. I'm also thinking of pulling data from datalossdb.org to see if I can find trends of dataloss incidents in certain industries with an increase in those same industries implementing 2FA.
That is some kind of closure! after 9 years this is marked as not planned. LOL
@gingerbeardman want it reopened? Maybe we can hit 25 years 😉