Skip to content
Snippets Groups Projects
  1. May 19, 2017
  2. May 18, 2017
    • Eugen Rochko's avatar
      Account domain blocks (#2381) · 620d0d80
      Eugen Rochko authored
      * Add <ostatus:conversation /> tag to Atom input/output
      
      Only uses ref attribute (not href) because href would be
      the alternate link that's always included also.
      
      Creates new conversation for every non-reply status. Carries
      over conversation for every reply. Keeps remote URIs verbatim,
      generates local URIs on the fly like the rest of them.
      
      * Conversation muting - prevents notifications that reference a conversation
      (including replies, favourites, reblogs) from being created. API endpoints
      /api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute
      
      Currently no way to tell when a status/conversation is muted, so the web UI
      only has a "disable notifications" button, doesn't work as a toggle
      
      * Display "Dismiss notifications" on all statuses in notifications column, not just own
      
      * Add "muted" as a boolean attribute on statuses JSON
      
      For now always false on contained reblogs, since it's only relevant for
      statuses returned from the notifications endpoint, which are not nested
      
      Remove "Disable notifications" from detailed status view, since it's
      only relevant in the notifications column
      
      * Up max class length
      
      * Remove pending test for conversation mute
      
      * Add tests, clean up
      
      * Rename to "mute conversation" and "unmute conversation"
      
      * Raise validation error when trying to mute/unmute status without conversation
      
      * Adding account domain blocks that filter notifications and public timelines
      
      * Add tests for domain blocks in notifications, public timelines
      Filter reblogs of blocked domains from home
      
      * Add API for listing and creating account domain blocks
      
      * API for creating/deleting domain blocks, tests for Status#ancestors
      and Status#descendants, filter domain blocks from them
      
      * Filter domains in streaming API
      
      * Update account_domain_block_spec.rb
      620d0d80
    • Matt Jankowski's avatar
      After remote follow worker specs (#3098) · 8ec84106
      Matt Jankowski authored
      * Add specs for the after remote follow workers
      
      * Refactor the after remote follow workers
      8ec84106
    • Sorin Davidoi's avatar
      07e87597
    • Yamagishi Kazutoshi's avatar
      79ef8b36
    • Ira's avatar
      i18l: Hebrew translation updates (#3109) · b11c4326
      Ira authored
      b11c4326
    • Quent-in's avatar
      update (#3113) · 390a2a8a
      Quent-in authored
      390a2a8a
    • Yamagishi Kazutoshi's avatar
      4d1ce3c7
  3. May 17, 2017
  4. May 16, 2017
  5. May 15, 2017
    • Hiroaki Ninomiya's avatar
    • Eugen Rochko's avatar
    • Eugen Rochko's avatar
      Fix change of status callbacks not setting in_reply_to_account_id and (#3072) · af706583
      Eugen Rochko authored
      possibly others when expected. Add some tests for it
      af706583
    • Akihiko Odaki's avatar
      Introduce common JavaScript file (#2981) · 85c94963
      Akihiko Odaki authored
      * Create common chunk rather than vendor chunk
      
      vendor chunk is a set of modules provided by external vendors, but now we
      can have a chunk as a set of modules shared by multiple entry points,
      which could be more efficent than having vendor chunk.
      
      * Start rails-ujs in common.js
      
      This is used by /settings/two_factor_authentication.
      85c94963
    • Kazuhiro NISHIYAMA's avatar
    • Eugen Rochko's avatar
      Feature conversations muting (#3017) · d0dd9eb5
      Eugen Rochko authored
      * Add <ostatus:conversation /> tag to Atom input/output
      
      Only uses ref attribute (not href) because href would be
      the alternate link that's always included also.
      
      Creates new conversation for every non-reply status. Carries
      over conversation for every reply. Keeps remote URIs verbatim,
      generates local URIs on the fly like the rest of them.
      
      * Conversation muting - prevents notifications that reference a conversation
      (including replies, favourites, reblogs) from being created. API endpoints
      /api/v1/statuses/:id/mute and /api/v1/statuses/:id/unmute
      
      Currently no way to tell when a status/conversation is muted, so the web UI
      only has a "disable notifications" button, doesn't work as a toggle
      
      * Display "Dismiss notifications" on all statuses in notifications column, not just own
      
      * Add "muted" as a boolean attribute on statuses JSON
      
      For now always false on contained reblogs, since it's only relevant for
      statuses returned from the notifications endpoint, which are not nested
      
      Remove "Disable notifications" from detailed status view, since it's
      only relevant in the notifications column
      
      * Up max class length
      
      * Remove pending test for conversation mute
      
      * Add tests, clean up
      
      * Rename to "mute conversation" and "unmute conversation"
      
      * Raise validation error when trying to mute/unmute status without conversation
      d0dd9eb5
  6. May 14, 2017
    • Eugen Rochko's avatar
      Fix style regressions (#3062) · a588358f
      Eugen Rochko authored
      From #2327 - Elephant friend was overlapping with text, oversized in
      single column layout
      
      From #2021 - Centered layout goes against design principles, changes
      UX for everybody who's already used to the current one
      
      From #2271 - CPU/RAM overusage from keeping columns in DOM (fix #2648,
      possibly also #2101)
      a588358f
    • Paul's avatar
      Fix only typo (#3035) · bc1a91f4
      Paul authored
      bc1a91f4
    • Eugen Rochko's avatar
      Do not cancel PuSH subscriptions after encountering "permanent" error… (#3046) · 657496b5
      Eugen Rochko authored
      * Do not cancel PuSH subscriptions after encountering "permanent" error response
      
      After talking with MMN about it, turns out some servers/php setups do
      return 4xx errors while rebooting, so this anti-feature that was meant
      to take load off of the hub is doing more harm than good in terms of
      breaking subscriptions
      
      * Update delivery_worker.rb
      657496b5
  7. May 13, 2017
Loading