cleverdevil / together Goto Github PK

The slides from your IWS demo would be lovely to have here. :-)

At least on my iPhone X, together is just barely too wide to fit the screen properly. It’s close!

Currently getting mixed-media warnings for http://fonts.gstatic.com/s/opensans/v15/mem8YaGs126MiZpBA-UFVZ0b.woff2 and http://www.inoreader.com/css/fonts/Inoreader-UI-Icons-Font.ttf?t6rt67 . The latter probably also is not intended for public use by random projects?

The more I use Together on a daily basis, the more I wish I could create content directly within Together. I don't think it needs to be as feature complete or sophisticated as, say, Quill, or using my preferred CMS, but having the ability to compose at least status updates and short articles would be lovely.

Should be able to click and see the full size photo

It’d be great to have a way to view only the unread items in a channel.

https://cleverdevil.io/s/U19hNDZhAf2OwosTxEa1.jpg

Since the recent change making the classic view article list wider, the above behavior has been showing in iOS.

I replied to post in Together, and got the following error page:

Unhandled Rejection (TypeError): undefined is not an object (evaluating '_this4.props.addNotification')
(anonymous function)
src/components/card.js:98
   95 |       this.setState({ popoverOpen: false });
   96 |       this.props.addNotification(`Successfully posted reply`)
   97 |     })
>  98 |     .catch((err) => this.props.addNotification(`Error posting reply`, 'error'));
   99 | }
  100 | 
  101 | handleView(e) {

That said, the actual reply seemed to post just fine.

Material UI supports dark and light themes by default so would love to be able to have a dark mode

Would like to automatically mark posts as read as you scroll by them

Should be split up into far smaller components in general and separate out styles into their own files

I can't quite figure out the circumstances under which this happens, but sometimes the "mark posts read" button is missing even though there are a bunch of unread posts in the channel.

Right now after you log in, the app is stuck on the URL with the code in the query string. Since it's a single-page app, it just stays around forever.

It would be better to either redirect back to the root after exchanging the code for an access token, or at least using the browser history API to update the URL without a pageload.

When attempting to login to Together with the latest update, I get an error in the JavaScript console:

https://cleverdevil.io/s/LPd2otbKQH.png

POST http://localhost:3000/api/micropub/getAuthUrl 404 (Not Found) micropub-api.js:39

Looks like perhaps some code didn't get fully checked in. I've tried in both Safari and Chrome on macOS.

It would be nice to enable the user to choose how they want their channels sorted and grouped when browsing:

• Sorting
  • Chronological by publish date
  • Chronological by "added" date (when the item was discovered by the microsub server)
• Grouping
  • By feed
  • By "post type"

I, personally, like some channels as chronological by publish date (sort of like a traditional "river of news" timeline) and others grouped by source and then sorted chronologically by publish date.

This is partially a Microsub thing, but I'd personally like having the ability to track the "read" state of individual items in a channel. I like the ability to see if a channel has any "new" or "unseen" items. In some cases, I like to hide items that are marked read. In others, I just want a continuous timeline.

If you add http://feeds.kottke.org/json as a source, images in the feed items won't load. He is using relative image paths in his image markup.

The checkins from my personal website:

https://cleverdevil.io/content/locations/

... do not show up on our "Checkins" map.

At first I thought the micropub posting form in the menu bar was the way to add a new channel, a tooltip and a title in the entry pop-up would have avoided me posting a random note saying "aaronparecki.com" ;)

When reading an article in “classic view” on a mobile device (you select the summary segment which loads the full page article) scrolling is not smooth on iOS. Using some css attributes this can be fixed: https://css-tricks.com/snippets/css/momentum-scrolling-on-ios-overflow-elements/

According to the IndieAuth Spec, there shouldn't be a "me" parameter returned from the initial Authorization Response. (https://indieauth.spec.indieweb.org/#authentication-response). My Authorization Endpoint follows the spec, so it breaks when I try to login.

The state parameter is supposed to help pass state along. Either using local storage or the state parameter to carry the "me" state through the login process.

@aaronpk's monocle had the same issue, there it happened because the channel ID gets used as the path component, which is also the case with together and might cause problems here too.

I have a publicly running demo server that accepts any auth token and has a channel like that at http://svenknebel.de:8089/microsub, you can use this for testing if you want. https://alltogethernow.io/channel/slashes/slashes does not work, the other channels do.

Would make sense to have keyboard controls at some point for navigating the app. Probably based on classic google reader keybindings

Right now the name and photo are not links, and I keep trying to click them

The PWA updates in the background. Together should provide a notification when the update is complete that the user can click to reload the page

So what are we thinking for a first working prototype type thing?

Based on the wireframe we came up with I think the first step would be to develop a basic functional stream that reads from a parsed feed eg https://ruby.microformats.io/microformats?utf8=✓&url=https%3A%2F%2Fcleverdevil.io

Or maybe it would be wiser to try and update woodwind to be more like the wireframe if it has the same end goal.

Personally I'd be happy to have a go at putting something basic together with react if there's no huge objection to that. Then it shouldn't be super difficult for others to contribute and improve.

I get a white page when using the map layout. I get the following error in the console: "Cannot read property 'marker' of null" at checkins.js:122

I'm not sure, it looks like the problem could that I have "checkin" property that is and empty object.

(Originally published at: https://publog.stuifzandapp.com/posts/525)

Support some way of expanding the micropub posting interface into a full editor.

After adding a feed, no channel items are visible ("🤷‍ Nothing to show - Maybe you need to subscribe to a site or select a different channel"). I have to switch channels to another one to see items again, clicking the same channel again does not work.

Chances are people will want to use different views for different channels. (compact / timeline / gallery etc)

This should be saved. Simplest option is probably just to store the last used view and default to that.

I have both node.js and yarn installed on my machine.

I run yarn start and I get the following output:

yarn run v1.1.0
$ react-scripts start
/bin/sh: react-scripts: command not found
error Command failed with exit code 127.

Having cards be able to be "collapsed" would be nice. This way, on channels with a lot of items, you could more easily skim through title/headline and then choose to expand a "Read More" of a particular article if desired.

Right now the client_id is set to "together.com" which is not where the app is launched! This also means any time I post from it my site is linking to together.com when it credits the app!

After pressing "logout" in the settings, not only was I not returned to a login screen (as I would have expected), together also was still useable and I could make changes that were sent to the microsub server.

The IndieAuth spec now has a way to do token revocation too.

Would love to have a classic multi column feed reader view, article preview on the left with a panel for the full article on the right.

Presently, Together offers users the ability to reply, like, or repost an item. It would be wonderful if there was a way to repost with comment, with the ability to enter more longform comments. One of my personal primary ways to share content is to "bookmark" it in my website with some commentary. Some examples:

• https://cleverdevil.io/2017/apples-new-ad-for-the-ipad-pro-is-pure-genius
• https://cleverdevil.io/2017/daring-fireball-cultural-insularity-and-apple-tv

Especially nice would be the ability to embed block quotes, as I do in the second example above.

I have 19 channels in Microsub, so just over half appear in the list before being cut off. It seems to fit 11 of my channels (some of them take up two lines because they are too long). It seems the the max single line channels is probably around 13 or 14. Adding an overflow-y scroll would help allow scrolling that view.

Now with the backend existing the app needs to make a request to login the user (it is not instant anymore), so I should add a loading indicator before that request is completed.

In addition to indentation, I like when blockquotes have a left border. I know it's totally a personal preference thing but I think it helps. I believe github does it as well:

test quote

Here's a mockup of some quick css i added in the browser:

blockquote {
    border-left: 4px #dfe2e5 solid;
    padding-left: 1em;
}

Ok so just wanted to write down some random thoughts on a backend system while I remember them.

I think we will almost certainly need a (hopefully fairly lightweight) backend system that can talk to microsub endpoints. Functionality I can see being very useful is:

1. Resizing photos - At the moment all photos are retrieved from their original url in full resolution, obviously not ideal
2. Normalising data - It will be a pain to have to deal with a lot of the variables in JF2 data, such as the author property seems like it can either be an object, a url string or completely empty and inferred from the source site hcard. Would be great if it was always an object so the frontend is more consistent. This might be something the microsub spec handles but I don't know. And the same goes for a bunch of other properties.
3. Micropub client - The backend should provide micropub client functionality to post likes, replies etc. I have my micropub-helper node package I can easily use if we have a node backend.
4. Streaming data - Would be great to have some sort of real time updates if possible without needing to refresh.
5. Url to MF2 parsing - For attributes like in-repy-to or children that may just be a url it would be great to be able to expand those into full MF2 objects and pull them into together if we want them.

Instead of having to click the button to pop out the post in the sidebar

The notifications channel should have it's own UI:

clients are expected to treat it separately such as showing it as a separate icon, not in the main channel list

https://indieweb.org/Microsub-spec#Set_Channel_Order

When a post is open show buttons to go back and forwards