They don't seem to post, and they don't seem to update the UI.

Hello. :) So I read the contributor guidelines, and I understand that this might be an issue that it's too early-days for and you might not respond, which is totally fine.

First of all, this is very nice to use! I love the dark text on the light background, too. My feedback is just that it takes a lot of clicks/taps to switch between accounts - Settings > Instances > [Instance] > "Switch to this instance" > Home. So a way to make that a little faster, and maybe even a way to change which account you're posting to from the "New Toot" text box area, could be really nice!

Thank you for your hard work on this, the results so far are LOVELY.

This might be possible, but would be really tricky given how I implemented data sharding on a per-instance basis.

If I create an toot using the instance https://pinafore.photog.social the public Mastodon toot page says it was created using Pinafore and links that text to https://pinafore.social.
Shouldn't it link directly to the instance which was used to create the toot?
Other people could see that note and it would help the decentralization if that note links to different instances and not only the official one.
As the correct link must be configured for the callback from the OAuth login page it should be easy to use the same address for the footer note.

Once we're open-sourced, we can set up Travis tests.

Reported here:

PWA functionality does not play nicely yet on iOS11.3 because when adding an instance, Safari opens & gets the login cookie instead of the sandboxed PWA webview, so it cannot login.

Sometimes new statuses and notifications don't appear until you refresh. Not sure how this happens, but I think it may be related to the browser suspending background tabs.

In desktop Chrome, if you scroll fast on the home timeline and click the sticky-positioned "compose" button, occasionally the hit detection falls through and clicks the underlying element instead. No repro in Edge, Firefox, or Safari. Probably a Chrome bug, but there may be some way to work around it.

Pinafore doesn't load any JS/CSS from anywhere but pinafore.social, but it'd be nice to protect against any potential XSS attacks by stipulating that fact in the CSP headers.

When you click the _n_th media in a status, you should be able to click some left or right buttons (or use the left/right keyboard buttons) to paginate between them.

Swipe left and right on a timeline to switch columns, so you don't need to tap the button in the navigation header.

I avoided this because I found that the react-swipeable-views on Mastodon sometimes has false positives on certain browsers. E.g. on mobile Firefox you scroll down, but it's interpreted as a swipe, which is confusing. Also touchmove events can block scrolling.

I think it may be possible to do this performantly and accurately with Pointer Events, but this needs some investigation first.

When the Service Worker updates, I've observed that in desktop Firefox the async chunks might fail to load unless you refresh the page. There is probably a way to fix this, but haven't figured it out yet.

STR:

1. Update the service worker until you see the "app update available" toast
2. Click a button that triggers a modal or something that triggers an async chunk
3. Observe that the async chunk fails to load

Right now this is just appended to the end of the thread, but we can deduce where it should appear.

I'm not sure we could do this in a privacy-respecting way. I'd really prefer not to handle any user data server-side.

Perhaps it would be possible to extend the Mastodon server API to allow clients to hook into the web push notification system? That way all user data would still reside with the instance, and the web client would just be responsible for receiving pushes.

To reproduce, with VoiceOver and Safari on the Mac:

1. Find a toot to reply to, then navigate to the Reply button and hit Ctrl+Option+Space (keystroke to activate current control).
2. Navigate forward (ctrl+option+right arrow) to the input to compose your reply. Write something.
3. Forward some more to the Toot button and hit Ctrl+Option+Space.

Expected: Toot is posted, and focus is restored to the Reply button of the toot I was replying to.
Actual: Toot is posted, but focus ends up somewhere random. So far, I've either landed at the very bottom of the page or at the toot controls at the top that are unrelated to replying.

When attempting to add an instance, https://i.write.codethat.sucks, I get: Error: undefined. Is this a valid Mastodon instance? I see an OPTIONS, a GET, and a POST, all succeeding. In the console, an InvalidStateError and then some error event involving the string IDBOpenDBRequest. Something to do with IndexedDB?

Firefox ESR 52, Debian Linux 9.

On mastodon.social (and twitter) pressing ctrl+enter when typing a toot will send that toot.

Timeline content on the same height as the floating compose button is not clickable. This is kinda confusing.
Thanks for this lightweight interface! 🎉

This is useful for folks who want to self-host Pinafore but don't want to spin up a whole Node server to do so. It'd also be useful for hybrid mobile apps.

In theory sapper export should work, but I'm on an older version of Sapper and so it doesn't. Need to either 1) upgrade Sapper, or 2) write my own script to crawl the various URLs and generate a static site. (2) may be easier given all the modifications I've made to the Sapper code.

This is a new thing that Mastodon 2.3.3 supports.

Pixel 2, Chrome 65.0.3324, installed as a PWA. Also confirmed on Chrome 65, ubuntu linux

The entire site locks up, leading to the app needing to be force-closed (on mobile), or displaying the "oh snap!" page on chrome.

of note is that we have lots of emoji (339) and a couple that are broken (for unknown reasons, the asset urls return 403s)

Privacy Badger thinks that Pinafore is running "third-party trackers" because of CORS requests to instances. Sigh...

Backstory: https://mstdn.io/@lychee/99830242316872578

1. Enter some text
2. Put the prefix of a username in the middle of the text
3. Press enter to choose the user
4. Your cursor jumps to the end of the entire textarea instead of just to the end of that username.

Observed in Firefox 59 desktop on Mac.

I can read image descriptive/alternative text by right clicking the image and viewing image info, but it would be nice to be able to see the descriptive text without having to click anything.

Probably tapping the nav button for a column you're already on should just go to the top of the timeline.

Need to fix the CSS for toots in search results.

This looks janky, especially on mobile Firefox. The built-in svelte-transitions slide animation animates height rather than transform.

I tested Pinafore with Pleroma, it works very well, except for viewing threads / posts. The browser does a request with an added } to the path, example: https://pleroma.soykaf.com/api/v1/statuses/7812305}.

Otherwise, it looks and works very well!

To reach basic parity with the Mastodon web UI, we need these features:

• mention someone from their profile page
• block/unblock accounts
• mute/unmute accounts
• authorize/reject follow requests
• show list of followers/following on account profile
• pin/unpin toots
• mute conversation
• hide boosts from someone
• block/unblock instances
• show client that posted a toot (web/Amaroq/etc)
• report toots
• confirmation dialogs for deleting/boosting/blocking/muting/etc
• confirmation to also mute notifications when muting someone
• media focal points
• opengraph cards
• edit profile
• edit lists
• paginate list of accounts beyond 80
• close/open all CWs in a thread at once
• embed a status

The text that precedes the actual posts of a timeline should be a heading. That way, screen reader users can jump past the navigation and toot composer straight to the beginning of their timeline and start reading. Right now, this is plain text.

There's no reason we couldn't also support dark themes.

When you unfollow someone, their toots should be purged from the home timeline.

Saw this once in Firefox desktop, seems to be related to Service Worker and the /statuses page? Not sure if it's due to some of my extensions, though (HTTPS Everywhere, uBlock).

The goal is to fallback to offline mode when offline, but for some instances this means media uploads just don't work. Upping to 30 seconds or having a higher timeout for media would be a potential fix.

When using Safaris private mode it shows an error page saying that it can't open the site after entering the 2FA code for your instance. All extensions were disabled.

Safari 11.1 on macOS 10.13.4

Screenshot (in German):

Currently those show a 404, but we could be intelligent about what to do when we get 404s.

This is currently not supported, but ideally you should be able to set filters that apply to all instances.

Right now you have to go into the settings to switch instances, but it'd be nice if you could do it from the home page.

I tried to add alt text to an image, but it renders as "undefined".

My testing thread is at https://icosahedron.website/@bvtsang/99830825277167424

There appears to be a leak in websockets for threads; I shouldn't be seeing this many console logs about this.

adding  0 items to itemIdsToAdd for thread status/99830632393220746
adding  1 items to itemIdsToAdd for thread status/99830809027028309
adding  1 items to itemIdsToAdd for thread status/99830575416375613
adding  1 items to itemIdsToAdd for thread status/99830830651335119
adding  0 items to itemIdsToAdd for thread status/99830810675607503
adding  0 items to itemIdsToAdd for thread status/99830521172162781

I should write a quick README about custom themes. Or maybe make it possible in the UI itself.

I tried to add https://i.write.codethat.sucks/ as an instance and received this error:

Error: NetworkError when attempting to fetch resource.. Is this a valid Mastodon instance?

Nothing stands out in the dev console or network log (and I don't see a request attempt being made.)

Firefox ESR 52, Debian Linux 9. Is this maybe an issue with Service Workers? I see that entered Firefox in January 2018.

Pixel 2, Chrome 65.0.3324, installed as a PWA (no clue how to find the app shell version sorry :( may be different from the installed chrome)

After pressing "reply", the input field opens and receives focus, but then the keyboard opens and covers the input field, emoji/attach/cw controls, and toot button. The input form does not appear to automatically scroll into view the way I would expect it to

ideally, the correct behavior here is that, after the keyboard opens, not only the input field but also the "TOOT" button is still in view.

We should probably limit these after the first 3 or so. When I'm walking around and momentarily lose a connection on my phone, I don't need to be notified.

It's not ideal performance-wise, but not everyone has an emoji keyboard on their operating system or knows how to use it. We probably ought to have a full emoji keyboard beyond just the custom emoji.

When I sign into an instance, it'd be nice to have an autocomplete populated by the http://instances.social/ API.

This would be useful for admins who just want Pinafore as an alternative UI that only works for their instance. It's possible, but would probably need a separate build system in order to lock it to a single instance and automatically log folks in.

Currently, all incoming notifications show up in the Notifications tab, regardless of which instance you're using. It would be helpful to distinguish this, whether it be by only showing notifications for the active instance, adding a tag, or something else.

I've seen this at least in desktop Firefox. Occasionally when you open a status in its thread, the scroll position is off by a bit. Not sure what causes this, and can't consistently reproduce it.