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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plan here is to create a table in the database that has the h-card's base URL (usually be a domain name, but I'd like to also support subdomains and paths), the status of the card (i.e. if someone has requested I do not post their information), a JSON-formatted cell of the parsed mf2 of their h-card, and a timestamp of the row's entry.
Should someone's h-card update to not exactly match the most recently timestamped row for that URL, save it as a new row. This will create a natural history of any changes they've made. The front-facing site will only ever consult the table's most recent row for a given h-card.
No description provided.
The text was updated successfully, but these errors were encountered: