31–40 of 103 posts
Like the idea, a lot, but I'm missing text. Maybe a small header text telling the core news of the item (and with more text than a typical tweet). And also articles instead of just videos? Or maybe the whole point is not having it? Personal preference of course, but for instance after clicking Russia-Ukraine conflict it doesn't tell me in a quick glance what the story is, at the left there is a bunch of meaningless p…
I'm having trouble viewing the page. I've successfully signed up and in, but the newsfeed hangs (blank page): http://api.grasswire.net/v1/newsfeeds All javascript etc. is also loaded succesfully. Any ideas?
Pushing up some changes now that should hopefully fix that. Essentially, the AWS healthcheck ping is timing out so it's removing instances from our load balancer. The streaming of tweets down to the client is pretty intensive and apparently a big bottleneck at the moment.
TypeError: Cannot read property 'left' of undefined at g ( http://grasswire.com/scripts/8ca0d719.vendor.js:12:1650 ) at Object.fn ( http://grasswire.com/scripts/8ca0d719.vendor.js:12:1242 ) at i.$digest ( http://grasswire.com/scripts/8ca0d719.vendor.js:5:17771 ) at i.$apply ( http://grasswire.com/scripts/8ca0d719.vendor.js:5:19070 ) at HTMLAnchorElement. ( http://grasswire.com/scripts/8ca0d719.vendor.js:6:28105 ) at…
This really needs a "disturbing content ahead" warning on the parts of the site that have graphic images. I really don't expect to see decapitated bodies when I randomly click a link.
In practice you're absolutely right. Will get on that.
Like the idea, a lot, but I'm missing text. Maybe a small header text telling the core news of the item (and with more text than a typical tweet). And also articles instead of just videos? Or maybe the whole point is not having it? Personal preference of course, but for instance after clicking Russia-Ukraine conflict it doesn't tell me in a quick glance what the story is, at the left there is a bunch of meaningless p…
Earlier quoted context omitted.
yes, I would keep tweaking the words if i were you to be exactly explicit/specific. eg: 1. 'like" is better than 'upvote' because it is clear that i am evaluate whether i like(re: enjoy) something, but what metric am i using to [up]vote on something? 2. "Reference URL" describes specifically what you want rather than some random URL.
Great feedback. But what if something is important but I don't "like" it - similar to how I'm not sure whether I should like a post on FB when my boss in unemployed. We've had that feedback too, like "This is awful and heartbreaking - do I favorite it?" (Favorite was the word we used to use).
Earlier quoted context omitted.
Give it just a second :)
I had to load the site 5 times before reading this comment and just being patient. Seems like a good tip to add to the onboarding tour.