# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 37
# self = https://watcher.sour.is/conv/2k3rywq
Also Markdown by default falls short when it comes to customizability, if you have lots of pages, then yes and maybe writing often (blog), I agree, it's a good idea to use Markdown, but if you have a 3-4 page site, that you don't update often, HTML is enough IMO and _the good tool_. Having to do all this in Markdown https://peguero.xyz/ might not work so great! I'm pretty sure he's using Markdown for the blog posts tho.
@adi That is of course your opinion bud 😆 And one I don't share 🤗
@adi That is of course your opinion bud 😆 And one I don't share 🤗
@prologic Not trying to convice you!
@prologic But disagree on _opinion_ but rather _fact_ that for complex pages Markdown is ill suited as you yourself saw when building https://prologic.shortcircuit.net.au/
Granted we simplified that and remove most HTML from Markdown as far as I remember.
@adi seems like you are trying to convince me, because you're also trying to convince me that you disagree on my opinion which is kind of rude 😆 opinions are individual and therefore my opinion is my opinion so I don't really care that much about your opinion 😆 I empathize and understand that you believe Mark down is ill suited for a single page or a few handful of pages but that is your opinion and your opinion only 🤣

That's the thing about opinions we have choices we are humans we have free wills everyone has an opinion 👌
@adi seems like you are trying to convince me, because you're also trying to convince me that you disagree on my opinion which is kind of rude 😆 opinions are individual and therefore my opinion is my opinion so I don't really care that much about your opinion 😆 I empathize and understand that you believe Mark down is ill suited for a single page or a few handful of pages but that is your opinion and your opinion only 🤣

That's the thing about opinions we have choices we are humans we have free wills everyone has an opinion 👌
@prologic Facts and opinions are different! It's a fact!
@prologic Arguing doesn't work by us trying to convince each other, arguing works by us providing logically correct arguments and proof. When there is enough evidence (proof, arguments) that a statement is true, it becomes a _fact_, not an _opinion_.
I'm sorry what are the facts here? 🤔 please provide the appropriate evidence.
I'm sorry what are the facts here? 🤔 please provide the appropriate evidence.
@prologic

> fact that for complex pages Markdown is ill suited

Do you believe Markdown is suited for something like this https://git.suckless.org/9base/log.html or this https://git.suckless.org/9base/commit/09e95a2d6f8dbafc6601147b2f5f150355813be6.html? Those are statically generated btw.
Or actually, if Markdown was that great for everything, we would all be writing Markdown, not HTML.
@adi hang on a second! I thought we were trying to present evidence and facts not opinions or beliefs 🤦‍♂️
@adi hang on a second! I thought we were trying to present evidence and facts not opinions or beliefs 🤦‍♂️
@prologic The fact that most of the WWW is written in HTML is evidence enough.
@prologic It's evidence that you wouldn't have a great time writing https://git.suckless.org/9base/commit/09e95a2d6f8dbafc6601147b2f5f150355813be6.html in Markdown, don't nitpick on words, whereas HTML is doing a good job there.
@prologic Also, forms!
@prologic Also https://mkws.sh/
@adi so let me get this striped… Your arguments and evidence is that Markdown isn't as flexible as hasht amount correct?

Now let's consider another piece of fact. Markdown is in fact a markup language that is strictly a very restricted subset HTML.

So therefore how can you compare them?

- If Markdown is not HTML. True/l
- And Markdown is not suitable for writing complex HTML. True
- Then what exactly? What are you trying to assert out of two True statements?
@adi so let me get this striped… Your arguments and evidence is that Markdown isn't as flexible as hasht amount correct?

Now let's consider another piece of fact. Markdown is in fact a markup language that is strictly a very restricted subset HTML.

So therefore how can you compare them?

- If Markdown is not HTML. True/l
- And Markdown is not suitable for writing complex HTML. True
- Then what exactly? What are you trying to assert out of two True statements?
I say, use Markdown when you're updating often, like blog posts, Markdown is easier on the fingers indeed (less to write) but when doing the _presentation_ part, do HTML.
In mkws I used HTML by default because using Markdown as most static site generators do feels limiting. That's why people complain they of the lack of customizability. In the About Me, My Projects, Other Stuff _presentation_ pages you can go as wild as you prefer with HTML, on the blog side, do Markdown.
When you get to customizing your _presentation_ pages you wrote in Markdown you start to see its limits, that it's not that flexibile and you have to get in the internals of the static site generator, complicating things.
It's super complicated to customize these _simple_ Markdown based static site generator!
Because Markdown was made mostly for content less for presentation.
_article content_, _blog content_, rather than _presentation content_.
> The HyperText Markup Language, or HTML is the standard markup language for documents designed to be displayed in a web browser.

> Markdown is a text-to-HTML conversion tool for web writers.
> The HyperText Markup Language, or HTML is the standard markup language for documents designed to be displayed in a web browser.

and

> Markdown is a text-to-HTML conversion tool for web writers.


> The idea was to make writing simple web pages, and especially weblog entries

> We’ve tested it extensively: on our blogs, in my comments form, in our emails.

http://www.aaronsw.com/weblog/001189

And by "simple web pages" he means this kind of _simple_ https://mkws.sh/docs.html!

Markdown is not for landing pages like https://mkws.sh or https://peguero.xyz/ or https://www.andrewjvpowell.com/.


> The idea was to make writing simple web pages, and especially weblog entries

> We’ve tested it extensively: on our blogs, in my comments form, in our emails.

http://www.aaronsw.com/weblog/001189

And by "simple web pages" he means this kind of _simple_ https://mkws.sh/docs.html !

Markdown is not for landing pages like https://mkws.sh or https://peguero.xyz/ or https://www.andrewjvpowell.com/.
More proof!

> The basic idea behind all weblog software — reduced to a nutshell — seems so simple in retrospect. Rather than managing a web site as a collection of pages, you manage a collection of posts, and the weblog software takes care of turning the posts into pages for you.

https://daringfireball.net/2004/03/dive_into_markdown


>That is of course your opinion bud 😆 And one I don’t share 🤗

Not opinion but quotes from the authors!


>That is of course your opinion bud 😆 And one I don’t share 🤗

Not opinion but quotes form the authors!
So basically, lots of static site generators are actually static blog generators!
> Markdown is not for landing pages like https://mkws.sh or https://peguero.xyz/ or https://www.andrewjvpowell.com/.

Ok, I misunderstood the term “landing page”, but the main idea is Markdown is for blog posts.