You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

122 lines
3.6 KiB

Change IDs to strings rather than numbers in API JSON output (#5019) * Fix JavaScript interface with long IDs Somewhat predictably, the JS interface handled IDs as numbers, which in JS are IEEE double-precision floats. This loses some precision when working with numbers as large as those generated by the new ID scheme, so we instead handle them here as strings. This is relatively simple, and doesn't appear to have caused any problems, but should definitely be tested more thoroughly than the built-in tests. Several days of use appear to support this working properly. BREAKING CHANGE: The major(!) change here is that IDs are now returned as strings by the REST endpoints, rather than as integers. In practice, relatively few changes were required to make the existing JS UI work with this change, but it will likely hit API clients pretty hard: it's an entirely different type to consume. (The one API client I tested, Tusky, handles this with no problems, however.) Twitter ran into this issue when introducing Snowflake IDs, and decided to instead introduce an `id_str` field in JSON responses. I have opted to *not* do that, and instead force all IDs to 64-bit integers represented by strings in one go. (I believe Twitter exacerbated their problem by rolling out the changes three times: once for statuses, once for DMs, and once for user IDs, as well as by leaving an integer ID value in JSON. As they said, "If you’re using the `id` field with JSON in a Javascript-related language, there is a very high likelihood that the integers will be silently munged by Javascript interpreters. In most cases, this will result in behavior such as being unable to load or delete a specific direct message, because the ID you're sending to the API is different than the actual identifier associated with the message." [1]) However, given that this is a significant change for API users, alternatives or a transition time may be appropriate. 1: https://blog.twitter.com/developer/en_us/a/2011/direct-messages-going-snowflake-on-sep-30-2011.html * Additional fixes for stringified IDs in JSON These should be the last two. These were identified using eslint to try to identify any plain casts to JavaScript numbers. (Some such casts are legitimate, but these were not.) Adding the following to .eslintrc.yml will identify casts to numbers: ~~~ no-restricted-syntax: - warn - selector: UnaryExpression[operator='+'] > :not(Literal) message: Avoid the use of unary + - selector: CallExpression[callee.name='Number'] message: Casting with Number() may coerce string IDs to numbers ~~~ The remaining three casts appear legitimate: two casts to array indices, one in a server to turn an environment variable into a number. * Back out RelationshipsController Change This was made to make a test a bit less flakey, but has nothing to do with this branch. * Change internal streaming payloads to stringified IDs as well Per https://github.com/tootsuite/mastodon/pull/5019#issuecomment-330736452 we need these changes to send deleted status IDs as strings, not integers.
6 years ago
  1. # frozen_string_literal: true
  2. class RemoveStatusService < BaseService
  3. include StreamEntryRenderer
  4. def call(status)
  5. @payload = Oj.dump(event: :delete, payload: status.id.to_s)
  6. @status = status
  7. @account = status.account
  8. @tags = status.tags.pluck(:name).to_a
  9. @mentions = status.mentions.includes(:account).to_a
  10. @reblogs = status.reblogs.to_a
  11. @stream_entry = status.stream_entry
  12. remove_from_self if status.account.local?
  13. remove_from_followers
  14. remove_reblogs
  15. remove_from_hashtags
  16. remove_from_public
  17. @status.destroy!
  18. return unless @account.local?
  19. remove_from_remote_followers
  20. remove_from_remote_affected
  21. end
  22. private
  23. def remove_from_self
  24. unpush(:home, @account, @status)
  25. end
  26. def remove_from_followers
  27. @account.followers.local.find_each do |follower|
  28. unpush(:home, follower, @status)
  29. end
  30. end
  31. def remove_from_remote_affected
  32. # People who got mentioned in the status, or who
  33. # reblogged it from someone else might not follow
  34. # the author and wouldn't normally receive the
  35. # delete notification - so here, we explicitly
  36. # send it to them
  37. target_accounts = (@mentions.map(&:account).reject(&:local?) + @reblogs.map(&:account).reject(&:local?)).uniq(&:id)
  38. # Ostatus
  39. NotificationWorker.push_bulk(target_accounts.select(&:ostatus?).uniq(&:domain)) do |target_account|
  40. [salmon_xml, @account.id, target_account.id]
  41. end
  42. # ActivityPub
  43. ActivityPub::DeliveryWorker.push_bulk(target_accounts.select(&:activitypub?).uniq(&:inbox_url)) do |target_account|
  44. [signed_activity_json, @account.id, target_account.inbox_url]
  45. end
  46. end
  47. def remove_from_remote_followers
  48. # OStatus
  49. Pubsubhubbub::RawDistributionWorker.perform_async(salmon_xml, @account.id)
  50. # ActivityPub
  51. ActivityPub::DeliveryWorker.push_bulk(@account.followers.inboxes) do |inbox_url|
  52. [signed_activity_json, @account.id, inbox_url]
  53. end
  54. end
  55. def salmon_xml
  56. @salmon_xml ||= stream_entry_to_xml(@stream_entry)
  57. end
  58. def signed_activity_json
  59. @signed_activity_json ||= Oj.dump(ActivityPub::LinkedDataSignature.new(activity_json).sign!(@account))
  60. end
  61. def activity_json
  62. @activity_json ||= ActiveModelSerializers::SerializableResource.new(
  63. @status,
  64. serializer: @status.reblog? ? ActivityPub::UndoAnnounceSerializer : ActivityPub::DeleteSerializer,
  65. adapter: ActivityPub::Adapter
  66. ).as_json
  67. end
  68. def remove_reblogs
  69. # We delete reblogs of the status before the original status,
  70. # because once original status is gone, reblogs will disappear
  71. # without us being able to do all the fancy stuff
  72. @reblogs.each do |reblog|
  73. RemoveStatusService.new.call(reblog)
  74. end
  75. end
  76. def unpush(type, receiver, status)
  77. if status.reblog? && !redis.zscore(FeedManager.instance.key(type, receiver.id), status.reblog_of_id).nil?
  78. redis.zadd(FeedManager.instance.key(type, receiver.id), status.reblog_of_id, status.reblog_of_id)
  79. else
  80. redis.zremrangebyscore(FeedManager.instance.key(type, receiver.id), status.id, status.id)
  81. end
  82. Redis.current.publish("timeline:#{receiver.id}", @payload)
  83. end
  84. def remove_from_hashtags
  85. @tags.each do |hashtag|
  86. Redis.current.publish("timeline:hashtag:#{hashtag}", @payload)
  87. Redis.current.publish("timeline:hashtag:#{hashtag}:local", @payload) if @status.local?
  88. end
  89. end
  90. def remove_from_public
  91. Redis.current.publish('timeline:public', @payload)
  92. Redis.current.publish('timeline:public:local', @payload) if @status.local?
  93. end
  94. def redis
  95. Redis.current
  96. end
  97. end