No screenshots of code. I don't care if it's not syntax-highlighted, but I would like it to be in plain text, hopefully fixed-width.
If you're going to reference another blog, please include the relevant information in your own blog before the linked site goes down and I have to hope that site's owner didn't block archive.org from indexing it.
I'd like comments enabled, but I know some people have a hard-line stance against it (I was once told, "oh, you're thinking of a forum" when I suggested a developer add comments to their blog). Sometimes people smarter than me comment on my blog, and that adds value to my post when it has incomplete or incorrect information.
I'd like to add that snippets of code presented as plain text should not be auto selected when someone clicks on them or what not, but should give the user the OPTION to copy the entire snippet as a separate button.
We don't always want to copy everything, we sometimes want to test out specific lines or what not. Don't mess around with how the select option works.
> Not that I disagree but isn't there a security risk with code that can be cut and pasted?
Yes if the blog author is malicious and the copy-paster inattentive. Don't even need an inattentive user if it's a command pasted in a terminal that will interpret the newline as <enter>.
No. Not to the poster. And not any different to the recipient than code that can be retyped, downloaded, or reproduced by any other mechanism besides copy and paste.
In addition to interactivity, Epiphany implements version control, forking and pull request. You can collaborate with others just like you do on github.
An article will have two timestamps, Create time and last modified time. More than that, you can see the entire revision history.
Source code is in text and syntax highlighted.
It also has the social publishing feature as seen on Medium.
Finally, users own their content. Epiphany has a download button to allow downloading all blog data.
The format used by Epiphany, unlike that of Jupyter, is in plain text and is human readable.
Sure! In the little tour it gives you, when it's describing the play button, I couldn't click Next or Finish because they were hidden behind the little tag input area. I just zoomed out on the page with CTRL + minus and was able to click.
I imagine you didn't notice this due to it being specific to my screen size (I'm on a macbook, I'm guessing you're using something else?)
I think that goes for everyone with a blog. And make sure that those dates have years! I've lost count of how many blogs only show the month and day of a post. "Mar 3" of 2019? Or is that 2009? I can't tell!
Thank you for giving me hope in my memory. Checking the Wayback Machine, it seems that putting absolute dates was a change that came some time after 2017. In 2017, HN post id=1 was dated "4027 days ago"[1].
Eh, I think it's fine if said timestamp starts off as relative, but becomes an absolute timestamp after a while. For instance, quite a few forums I use have the timestamp for today's posts as 'posted today at [time], but it changes to 'posted yesterday at [time]' when its a day old, then eventualy to 'posted on [date] at [time] once it's about a week ago or so.
Toptal is a big offender with this. I asked them before to do this and they declined. I understand there are some evergreen content out there, but anything related to technology does not fall into that category and having a date is important to understand if the content is likely out of date.
I suspect a fair few of the people who do this are trying to trick search engines into thinking their content was posted more recently than it actually was, since a few SEOs did experiments and found content without timestamps/with misleading ones would sometimes rank higher than those with accurate ones.
That or they think it gets people thinking they post more regularly than they actually do.
But yeah, agreed. Especially given that software development is a rather time sensitive field, and what works/happens to be best practice at one point may not be so further down the line.
Oh i wrote last blog post 10 years ago? So sad. Swoosh. Evergreen enabled :)
Ps. Techcically speaking a set of articles without timestamps is not a blog
A timestamp is useful for rapidly-cycling content, especially comment threads. If you're posting content less often than daily, a date stamp is sufficient, though if your site has multiple posts daily, go with timestamps.
"Sufficient granularity to distinguish content" should be your guiding principle.
Also n00bs like me... just don't offer code specific instruction about coding on your blog. Personal experiences, learning advice have at it, but if you really haven't done much coding.... please don't offer advice about it.
I hate to be so negative but the internet is awash with bad coding advice (and the same code copied from vid to blog and back again) that seems like resume fodder more than helpful.
The worst thing about learning is reading a post long enough to realize the other person is a noob too and their code is a malformed mess that the blog author doesn't really understand.
I have to disagree, I have learned from a lot of n00bs. I copied broken code and it didn't work, but it provided enough hints that I was able to make it work. I also posted back fixed code as comments on authors' blogs, and many would update their post with my code.
Same thing has happened on my blog, I have some super old Pentaho configuration posts, and every once in a while I get an email from someone saying my code is not right but they were able to make it work with some changes. Hence, I leave it up there.
No screenshots of code. I don't care if it's not syntax-highlighted, but I would like it to be in plain text, hopefully fixed-width.
If you're going to reference another blog, please include the relevant information in your own blog before the linked site goes down and I have to hope that site's owner didn't block archive.org from indexing it.
I'd like comments enabled, but I know some people have a hard-line stance against it (I was once told, "oh, you're thinking of a forum" when I suggested a developer add comments to their blog). Sometimes people smarter than me comment on my blog, and that adds value to my post when it has incomplete or incorrect information.