| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Squashed commit of the following:
commit b9877e37f72fdd8134936e1014033b07cb6c3671
Author: Surinna Curtis <ekiru.0@gmail.com>
Date: Wed Jul 12 00:50:10 2017 -0500
account for the eye in the chars left count for local-only toots
commit 56ebfa96542e16daa1986cc45e07974801ee12dc
Author: Surinna Curtis <ekiru.0@gmail.com>
Date: Wed Jul 12 00:21:02 2017 -0500
factor out an AdvancedOptionsToggle to avoid unnecessary re-renders
commit 04cec44ab8744e4e0f52da488c9ec24b1b1422ef
Author: Surinna Curtis <ekiru.0@gmail.com>
Date: Wed Jul 12 00:20:24 2017 -0500
s/changeComposeAdvancedOption/toggleComposeAdvancedOption/g
commit af5815dee750d1aa8b797a9305e5ab3ce6774e3f
Author: Surinna Curtis <ekiru.0@gmail.com>
Date: Tue Jul 11 23:55:19 2017 -0500
clicking anywhere on the whole advanced option toggles
|
|
|
|
|
|
|
|
|
|
* First lame pass at adding optional git commit hash display on /about/more page.
Currently, this is implemented by checking for the existence of a file called CURRENT_RELEASE in the home directory of the user running Mastodon. If the file exists, its contents are added.
I've modified my update process to include the following before precompiling assets:
git log -1 | head -n 1 | cut -d " " -f2 > ~/CURRENT_RELEASE
That puts the current commit hash into the file ~/CURRENT_RELEASE, but you figured that out because you're a smart cookie.
As I am quite sure this is a horrible methodology for implementing this, I look forward to any improvements you have to offer!
* Updated to handle instances that share a user - the CURRENT_RELEASE file now lives in the instance's base directory.
This also requires modifying the update hook to `git log -1 | head -n 1 | cut -d " " -f2 > CURRENT_RELEASE`
|
|
|
|
|
|
|
|
(#4157)
This reverts commit 425acecfdb15093a265b191120fb2d4e4c4135c4.
|
|
|
|
Can be filtered by a specific domain
Resolves #2292
|
|
This makes it consistent with /api/v1/accounts/search and
previous behaviour has been an oversight.
|
|
* Redesign the landing page, mount public timeline on it
* Adjust the standalone mounted component to the lacking of router
* Adjust auth layout pages to new design
* Fix tests
* Standalone public timeline polling every 5 seconds
* Remove now obsolete translations
* Add responsive design for new landing page
* Address reviews
* Add floating clouds behind frontpage form
* Use access token from public page when available
* Fix mentions and hashtags links, cursor on status content in standalone mode
* Add footer link to source code
* Fix errors on pages that don't embed the component, use classnames
* Fix tests
* Change anonymous autoPlayGif default to false
* When gif autoplay is disabled, hover to play
* Add option to hide the timeline preview
* Slightly improve alt layout
* Add elephant friend to new frontpage
* Display "back to mastodon" in place of "login" when logged in on frontpage
* Change polling time to 3s
|
|
Require stylesheets in common.js because stylesheets are shared by the
entry points.
|
|
* Add notifications link to drawer
* Remove local and public timeline tab in drawer
* Add home
|
|
ProcessFeedService::ProcessEntry had many methods, so wrap them in classes
representing activities.
|
|
|
|
|
|
|
|
* i18n: @7a889a8 (pl)
* Update pl.yml
|
|
Since es5-ext used `new Function("...")`, it caused CSP violation unless "unsafe-eval" included. So this patch updates it to the version which fixes it.
Note that this package is used in polyfills, so loaded only if needed. I've encountered this issue on iOS9.
cf. medikoo/es5-ext@d3864493
|
|
It increased memory usage of Webpack 1.5x fold with little benefits
|
|
* Added a success page to remote following
Includes follow-through links to web (the old redirect target) and back to the remote user's profile
* Use Account.new in spec instead of a fake with only id
(fixes spec)
* Fabricate(:account) over Account.new
* Remove self from the success text
(and all HTML with it)
|
|
|
|
Since there is little point in retrying so often when a service is down
or does not exist anymore. Subscriptions are renewed 1 day before they
should expire, so retrying in 30 minutes, then 2 hours, then 12 hours
is fine. If even after that, the remote server does not work, there is
little sense in retrying more often than once a day
Also, uniqueness of the job should ensure that failed retries will
not result in multiple retries for the same endpoint when the next
resubscription cycle comes
|
|
|
|
* Add Japanese translations for #3879
* Add Japanese translations for #4033
* Add Japanese translations for #4136
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is per issue #3876
|
|
Deleted ">" just a typo.
|
|
* Add attribute for default privacy to verify credentials
* add raw_note
* source
|
|
* fix(components/media_modal): Aspect ratio
* fix: Remove useless style
|
|
|
|
* Rescue exceptions related to Goldfinger
* Exclude Goldfinger::SSLError
|
|
* feat: Replace react-swipeable with react-swipeable-views
* fix: iOS 9
|
|
|
|
|
|
|
|
|
|
|
|
|
