# 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 17
# self = https://watcher.sour.is/conv/qy6mbvq
@thewismit Oh my! I'll have a proper look later, but my initial reaction was: envy! Well done, sir! 😁
@thewismit Oh my! I'll have a proper look later, but my initial reaction was: envy! Well done, sir! 😁
@thewismit I just had a look at the blog. It looks like the font sizes of the publish dates aren't the same on the overview and and articles. Although I usually like space-efficient designs, the overview seems a tiny bit squished too much. Not sure whether vertical spacing would help or placing the publish dates on the right, but same line as the titles. Or is the excerpt too short? Don't know. Other than that, I like it.
@lyse thanks Lyse :) I used a table data field with in it, to space out the blog roll a bit https://thewismit.com/ also, thanks for catching the publish font size difference!
@darch thanks much! my 13 yr old is responsible for the colors :D
@jlj glad you like it. now I need to somehow keep the motivation to blog lol!
@thewismit Oh yes, this looks way better! But why do you use tables for the layout and not <h2>, <p> and <date> with a bit of CSS?
@lyse because I ripped off the HTML from elsewhere. Is there a better way? :D
@thewismit I don't consider myself a web developer (hell no!), but I strongly believe, that semantic elements should be used whenver possible. I also advocate making use of the HTML structure in the CSS rules, rather than defining classes and IDs for that purpose. Something along those lines: https://lyse.isobeef.org/thewismit.html It's not a pixel-perfect copy, that's left as an excercise to the dear readers. :-P
@lyse Interesting! Thank you for that. If I set the arrow bullet point using CSS like you did, won't that set all h2 tags to have that arrow? Also, if so, I could get around that by using inline CSS on that single page but I don't think I want to do that either. Right?
@thewismit Yes, this rule applies to every <h2>. It was just meant to illustrate the point of separation between semantic and presentation. The square brackets in the nav could be also seen as visual things only and thus generated using CSS rules. Back to the <h2>: You could use section > h2 as selector, if you just use the <section> container in the overview. Now that you say, that this is meant be be a list item, I reckon you're better off using <ul> and <li> instead.
@lyse Nice, I learn something every day. Thanks!