Accessible, simple and fast web client for Mastodon
Go to file
Nolan Lawson 880bc7a38a
perf: use a separate icons.svg file (#1067)
* perf: use a separate icons.svg file

This splits icons into inline and non-inline. The inline ones are high
priority; the rest go in an icons.svg file.

* create SvgIcon.html

* determine inlined svgs at build time
2019-03-02 19:02:06 -08:00
bin perf: use a separate icons.svg file (#1067) 2019-03-02 19:02:06 -08:00
docs chore: switch to yarn (#927) 2019-01-27 17:44:30 -08:00
src perf: use a separate icons.svg file (#1067) 2019-03-02 19:02:06 -08:00
static feat: implement web share target (#980) 2019-02-13 18:38:44 -08:00
tests test: improve emoji test (#1056) 2019-02-28 08:56:38 -08:00
webpack perf: use a separate icons.svg file (#1067) 2019-03-02 19:02:06 -08:00
.dockerignore perf: use a separate icons.svg file (#1067) 2019-03-02 19:02:06 -08:00
.editorconfig chore(editor): add an editorconfig (#710) 2018-12-01 23:06:34 -08:00
.gitignore perf: use a separate icons.svg file (#1067) 2019-03-02 19:02:06 -08:00
.nowignore perf: use a separate icons.svg file (#1067) 2019-03-02 19:02:06 -08:00
.travis.yml chore: switch to yarn (#927) 2019-01-27 17:44:30 -08:00
BREAKING_CHANGES.md docs: add documentation about 1.0.0 yarn changes (#959) 2019-02-10 11:30:00 -08:00
CONTRIBUTING.md perf: reduce install size using yarn --production (#1066) 2019-03-02 14:44:19 -08:00
Dockerfile perf: reduce install size using yarn --production (#1066) 2019-03-02 14:44:19 -08:00
LICENSE add footer and license 2018-03-07 09:25:07 -08:00
README.md perf: reduce install size using yarn --production (#1066) 2019-03-02 14:44:19 -08:00
now.json chore: use a script to generate the now.json (#1007) 2019-02-16 14:30:34 -08:00
package.json perf: use a separate icons.svg file (#1067) 2019-03-02 19:02:06 -08:00
server.js fix: use static server for `node server.js` (#1041) 2019-02-23 16:09:48 -08:00
webpack.config.js fix: update Sapper to latest (#775) 2018-12-11 07:31:48 -08:00
yarn.lock chore: update all deps (#1062) 2019-02-28 21:35:22 -08:00

README.md

Pinafore Build Status Greenkeeper badge

An alternative web client for Mastodon, focused on speed and simplicity.

Pinafore is available at pinafore.social. Beta releases are at dev.pinafore.social.

See the user guide for basic usage. See the admin guide if Pinafore cannot connect to your instance.

For updates and support, follow @pinafore@mastodon.technology.

Browser support

Pinafore supports the latest versions of the following browsers:

  • Chrome
  • Edge
  • Firefox
  • Safari

Compatible versions of each (Opera, Brave, Samsung, etc.) should be fine.

Goals and non-goals

Goals

  • Support the most common use cases
  • Small page weight
  • Fast even on low-end devices
  • Accessibility
  • Offline support in read-only mode
  • Progressive Web App features
  • Multi-instance support
  • Support latest versions of Chrome, Edge, Firefox, and Safari

Secondary / possible future goals

  • Support for Pleroma or other non-Mastodon backends
  • Serve as an alternative frontend tied to a particular instance
  • Support for non-English languages (i18n)
  • Offline search

Non-goals

  • Supporting old browsers, proxy browsers, or text-based browsers
  • React Native / NativeScript / hybrid-native version
  • Android/iOS apps (using Cordova or similar)
  • Full functionality with JavaScript disabled
  • Emoji support beyond the built-in system emoji
  • Multi-column support
  • Admin/moderation panel
  • Offline support in read-write mode (would require sophisticated sync logic)

Building

Pinafore requires Node.js v8+ and Yarn.

To build Pinafore for production, first install dependencies:

yarn --production --pure-lockfile

Then build:

yarn build

Then run:

PORT=4002 node server.js

Docker

To build a Docker image for production:

docker build .
docker run -d -p 4002:4002 [your-image]

Now Pinafore is running at localhost:4002.

Updating

To keep your version of Pinafore up to date, you can use git to check out the latest tag:

git checkout $(git tag -l | sort -Vr | head -n 1)

Exporting

You can export Pinafore as a static site. Run:

yarn run export

Static files will be written to __sapper__/export.

Note that this is not the recommended method, because CSP headers are not currently supported for the exported version.

Developing and testing

See CONTRIBUTING.md for how to run Pinafore in dev mode and run tests.

Changelog

For a changelog, see the GitHub releases.

For a list of breaking changes, see BREAKING_CHANGES.md.

What's with the name?

Pinafore is named after the Gilbert and Sullivan play. The soundtrack is very good.