The quickest way to explain QuikPub in a way everyone should get is to describe it as “Imgur for text.”
I’ve felt for a long time that there was no easy way to quickly publish short or long form rich text without going down the blog route. Blogging -- by design — comes with a history of posts and comments. Too much information when all you want to do is post about something that has nothing to do with your blogging persona or area of expertise.
QuikPub lets you post anonymously (or add your name) and share a short URL to that content anywhere you want (just like Imgur). It comes with a slightly longer edit URL so that you can change or delete the post later.
There’s no link or connection to other posts you make. There’s no public list of “new posts.” Your QuikPub post is invisible to Google and to casual browsers until you choose to share it.
There was a Show HN yesterday about a new product called Haven that seems to be targeting a similar user base, though their solution was very different. (https://news.ycombinator.com/item?id=26013715) While reading the comments I felt that many of those commenting would benefit from a simple publishing app like QuikPub.
Feedback is very welcome. I’m not a UI designer, and I’m aware that the UI is a bit on the weak side, but that’s something I hope to improve over time.
Here’s a few examples of posts I made myself earlier:
There is with write.as (e.g. <https://write.as/hjr5ogk4f0wnw.md>), which uses the same engine as WriteFreely, a blogging alternative to Medium, and is operated by the WriteFreely maintainer.
Cool project. I've been looking for this kind of service for a long time.
I would like to report a bug regarding your rich-text editor. I'm trying to post several images, but everything is vanished when i publish it. See here : https://streamable.com/wpm5mh
Screenshot : https://github.com/altilunium/rtnF/blob/main/rtnf_screenshot...
Github Repo : https://github.com/altilunium/rtnF
Maybe you can use it as a component for this service.
Oh, sorry. I haven't read your thread comment below. At least you probably should tell it directly to the users on the landing page (no image support yet), or hide the "image" icon on the richtext editor, and disable the paste-image feature on the richtext editor. Some users are probably expecting your service can handle the image feature, just like the usual blogging platform.
Also, how do you plan to promote it? Apart of HN.
How far I get with stages 2 and 3 depends on the kind of feedback I get from people over the coming weeks.
I have ideas about how to extend it to a paid for app, but the short answer is I haven't decided yet if that direction has legs. Too early to say.
As for promotion, I'm reaching out to different types of potential users right now. I have some older desktop products in the creative writing field, and have a lot of users of those products, so that's another avenue for feedback and potential users.
Two pieces of advice for you if you are intending to take this to market. I suggest writing/investing in some good moderation tools to prevent spammers and other undesirables from using your site for illegal stuff. Also, get yourself a lawyer and write terms of service to protect your project from liability.
Shady content, potential copyright infringements, it's a can of worms all right.
A quick skim reveals some link-filtering services and libraries do exist, such as:
You might want to consider hosting content published on a different domain from your main site, otherwise search engines and site lists could flag the domain as a bad actor if something gets through.
The normalization of deplatforming and censorship is one of the most dangerous turns in recent times. I don’t wish to support any platform which will remove content that isn’t explicitly illegal.
After publishing, the page is more wider than phone screen, & user can't scroll horizontally to see the whole page or published link https://quikpub.co/763Q4EX52G
You don't need to build these things today, but you need a backlog of clear plans or at least plans for investigation, and some sort of tech in place now to warn you of potential risks (very popular pages, loads of use from one Ip, etc etc)
Anything that can be done about reducing the load on this?
The individual content (QuikPub) view page is a lot less as it doesn't contain any of the JS library scripts.
How long are posts guaranteed to stay available?
Do your future plans for the service include creating an authentication method so that users can edit/remove earlier posts or download all of their content and move it to another server if necessary?
How do you plan to deal with libel claims?
There's an edit/delete url as well as a share url.
>How long are posts guaranteed to stay available?
Hopefully for ever. But it's early days now on a two week project, so I don't have answers for that far in the future.
>or download all of their content and move it to another server if necessary?
That would definitely be on the plan, but wouldn't be implemented until a log in / user account mechanism was in place.
>How do you plan to deal with libel claims?
I haven't fleshed out that far ahead yet. Today I'm focused on getting a working app out there. Next week, once I see if anyone is using the app in earnest I'll have more time to get a handle on what to do about illicit or potentially harmful content.
I say keep it text only for people to publish. No images.
Make the footer a bit smaller and also include a link to report the post. Just to cover your bases.
Just minor feedback. Nice work.