nogafam
/
fedilove-ui
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity
1,606 Commits 1 Branch 0 Tags 143 MiB
JavaScript 59.1%
HTML 37%
SCSS 3.7%
Go to file
Cătălin Mariș cdade05315 fix: use only one 180x180px touch icon (#1213) 
* Include just one 180x180px touch icon`.

  Over time as Apple released different size displays for their
  devices, the requirements¹ for the size of the touch icon have
  changed quite a bit:

   * 57×57px – iPhone with @1x display and iPod Touch
   * 72×72px – iPad and iPad mini with @1x display running iOS ≤ 6
   * 76×76px – iPad and iPad mini with @1x display running iOS ≥ 7
   * 114×114px – iPhone with @2x display running iOS ≤ 6
   * 120×120px – iPhone with @2x and @3x display running iOS ≥ 7
   * 144×144px – iPad and iPad mini with @2x display running iOS ≤ 6
   * 152×152px – iPad and iPad mini with @2x display running iOS 7
   * 180×180px – iPad and iPad mini with @2x display running iOS 8+

  However, most iOS users will be on the latest 2 versions² of iOS
  and using newer devices, so nowadays, one 180x180px touch icon is
  enough.

  Also, if needed, the icon will be automatically³ downscaled by
  Safari, and the result of the scaling is generally ok.

* Remove unneeded `sizes` attribute.

  When using only one touch icon there is no need to use the `sizes`
  attribute.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

¹ https://github.com/h5bp/html5-boilerplate/pull/1599#issuecomment-56384135
² https://developer.apple.com/support/app-store/
³ https://realfavicongenerator.net/blog/how-ios-scales-the-apple-touch-icon/

See also: https://mathiasbynens.be/notes/touch-icons
 		2019-05-13 21:45:38 -07:00
bin fix: close/open websocket on freeze/resume events (#1195) 2019-05-08 19:58:32 -07:00
docs chore: switch to yarn (#927) 2019-01-27 17:44:30 -08:00
src fix: use only one 180x180px touch icon (#1213) 2019-05-13 21:45:38 -07:00
static fix: use only one 180x180px touch icon (#1213) 2019-05-13 21:45:38 -07:00
tests fix: make autosuggestion accessible (#1183) 2019-05-05 22:08:54 -07:00
webpack fix: close/open websocket on freeze/resume events (#1195) 2019-05-08 19:58:32 -07:00
.dockerignore chore: remove now.json from source control (#1126) 2019-03-31 10:55:54 -07:00
.editorconfig chore(editor): add an editorconfig (#710) 2018-12-01 23:06:34 -08:00
.gitignore chore: remove now.json from source control (#1126) 2019-03-31 10:55:54 -07: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 chore: update to mastodon v2.8.2 (#1181) 2019-05-05 15:02:14 -07:00
Dockerfile Clean yarn cache during docker image build phase (#1073) 2019-03-03 13:25:42 -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
package.json 1.7.0 2019-05-11 08:26:38 -07: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 deps (#1206) 2019-05-11 08:13:30 -07: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.