The docs for "unreblog" in https://docs.joinmastodon.org/methods/statuses/ don't specify which user is authorised to unreblog a status, nor the result of doing so.

In practice, I think this is restricted to the person who reblogged it (and not, for example, the person who posted the status being reblogged).

The docs have a great intro that explains the technology buildup to arrive at inventing stream but then it stops without explaining how stream uses Cassandra + Redis (plus celery message queue?) to solve this problem. (For all I know it doesn't.)

As a developer, a quick explanation of how this framework solves the

I have found that @activity.trackable does not work when there is a default_scope which excludes the tracked object. I found a working monkey patch (see below), though is there a more appropriate solution? Would it be possible to override this default_scope when it's present?

PublicActivity::Activity.class_eval do
  def trackable
    trackable_type.constantize.unscoped.find trackabl

I'm trying to create a multiple snapshots/releases/versions of an article. I found rel:latest-version, rel:predecessor-version but no real-world example of a publication with versions. My approach would be:

• put current version at http://example.org/article
• put versions at http://example.org/article/X.Y.Z where X.Y.Z is a version number
• link versions with rel:latest-version,

PS D:\React\react-native-example> expo start
Starting project at D:\React\react-native-example
Expo DevTools is running at http://localhost:19002
Opening DevTools in the browser... (press shift-d to disable)
(node:77844) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
error Invalid regular expression: /(.\fixtures\.|node_modules[\]react[\]dist[\].*

Currently we get date time from Postgres, but this is deprecated.

Need to get the date from a corresponding struct, if it's an activity like Blog/Post/Comment Created/Updated.

Or calculate an approximate date based on current_time - block_time * (current_block - activity_block)

Related to issue:

dappforce/dappforce-subsocial-offchain#61

I was thinking about how to best add inactive users to the user list, because when you don't need a bouncer anymore, you're hidden as a "member of the channel" otherwise. And the emptier a channel looks, the less likely are new people to idle and eventually engage in my experience. Options that came to mind:

1. Store a list of users that have been seen while you were online yourself in your use

It doesn't make sense to save the date when an activity was inserted into Postgres DB, because DB can be recreated based on Substrate events any time.