Show HN: Squall – A microblogging platform that replaces tweetstorms

Post by forthefuture » Fri, Mar 06, 2015, 7:03 PM UTC

Post by drvortex » Fri, Mar 06, 2015, 7:14 PM UTC

Post by [deleted] » Fri, Mar 06, 2015, 7:25 PM UTC

barisser wrote: post #12

forthefuture wrote: post #11

I don't know if it's part of the platform, but all of the watermarking seems a little over the top. By that I mean the "sent from Squall", and "by...via @SquallApp". I'd put forth that you don't need those things to have people understand where the image came from; the link in the twitter post that starts with "squall.io/", and anyone following the link ends up at the site. Not that it's overwhelming, it's just that…

You make a fair point. We're still adjusting the branding. I could see us tuning it down.

Post by aiiane » Fri, Mar 06, 2015, 7:37 PM UTC

barisser wrote: post #3

Hi, core team here from Squall. I'd be happy to answer any questions/comments. Squall is a community-built product on Assembly. So each contributor gets some fraction of ownership, commensurate with their contribution to the product. I'd highly suggest writing a Squall post. It's an easy way to say more on Twitter.

Post by nicwest » Fri, Mar 06, 2015, 7:49 PM UTC

barisser wrote: post #4

giancarlostoro wrote: post #2

I saw a similar application here on HN one of the valid points against this is that you cannot really parse the text through the image, so it becomes a barrier against visually impaired users. At first I was thinking it was going to be links to a bigger tweet or something similar.

One difference with Squall is that, while the post is an image on Twitter, it lives on as a text post on Squall.io. So you can always follow the link and parse the text there. Also the images are highly legible. Check out this Squall for example: https://twitter.com/bshyong/status/573557768285732864