-
Notifications
You must be signed in to change notification settings - Fork 25
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
Redesign Activity data model #286
Comments
…add protocol #286 ndb implements StructuredProperty by hoisting each nested property into a corresponding property on the parent entity, prefixed by the StructuredProperty's name, eg delivered.uri, delivered.protocol, etc. For repeated StructuredPropertys, the hoisted properties are all repeated on the parent entity, and reconstructed into StructuredPropertys based on their order. https://googleapis.dev/python/python-ndb/latest/model.html#google.cloud.ndb.model.StructuredProperty
#286 temporarily adds back Activity model definition, will remove again later.
#286 temporarily adds back Activity model definition, will remove again later.
…add protocol #286 ndb implements StructuredProperty by hoisting each nested property into a corresponding property on the parent entity, prefixed by the StructuredProperty's name, eg delivered.uri, delivered.protocol, etc. For repeated StructuredPropertys, the hoisted properties are all repeated on the parent entity, and reconstructed into StructuredPropertys based on their order. https://googleapis.dev/python/python-ndb/latest/model.html#google.cloud.ndb.model.StructuredProperty
#286 temporarily adds back Activity model definition, will remove again later.
I've tentatively deployed this just now and migrated all stored |
Looking ok! UI pages all seem ok, webmentions and AP inbox delivery both directions seem ok, #361 is fixed. No crashes yet. Last |
Tentatively closing. Onward to #388... |
Actually, let me keep this open to track all the post-launch work. |
Converted the remaining post-launch tasks to their own issues. Closing this one. Big milestone, woo! |
Right now, for outbound activities, we store an
Activity
entity per delivered inbox. We also show per-delivered-inbox activities in the recent activities UI on user pages and https://fed.brid.gy/recent. Obviously not ideal.Ideally we'd rethink the data model. As a short term workaround until then, we should probably also only show one row per outbound activity in the UI, not one per delivered inbox.
Before launch:
type
: verb for activity, objectType otherwiseobject_ids
send
(Redesign protocol code #388) deliverySplit current dashboard page into user and notifs?Activity
=>Object
migration:Activity
s with same source, populateap_*
fields, earliestcreated
, latestupdated
labels
,type
,object_ids
Object
s for activities vs objects (notes, articles, actors)(this is now required by
render.py
)After launch:
as1
prop for everythingFollower.last_follow
toKeyProperty(Object)
? #412The text was updated successfully, but these errors were encountered: