If you're a writer, but not a techie, do you like Markdown?
If so, what do you use to write your MD text?
Is any of it public? If so how do you get it on the web? Where do you store it? How much does it cost, if anything?
0 Boosts
0 Likes
@davew I use Byword app to write my posts. I then paste them in Pika by @goodenough before publishing.
@rishidass @goodenough -- i made a small investment in Logseq, so it's nice that's what you use. Where do you upload your Markdown files? How automatic is it?
@davew
I write my blog in obsidian and build with zola and host on github but use a custom URL. All free.
@970uts1d3 -- github is great, the answer to all developers' prayers, but most def not a writer's product (ie not a developer).
@davew I love markdown. I tend to write in Obsidian or Drafts in MacOS. For my blog I'll write in Ulysses and publish to WordPress.
Not sure what subs are for Drafts or Ulysses, but not expensive.
For my Day Job we have to write SOPs in MS Word, which I hate. So I'll write in Obsidian and convert to Word.
@phoutz -- wordpress! that's one i had not heard in this context. i think wordpress with a few little tweaks could be the path of markdown files on to the web.
That part is beyond my pay grade. Ulysses does the conversion from markdown to whatever it is that Wordpress consumes. But it would be wonderful to write directly in markdown on the blog - particularly for adding links.
@davew Thanks for asking. I don't use MD - actually I can't use MD. It's part of my neurodivergence. In addition to dyslexia, I have some vision differences from normals. I need to see the shape of words, phrases, etc. to read, including to read what I am writing. MD is very difficult for me to read. Dyslexia means I'm already wrestling with coding/decoding ideas into words. MD adds another layer of decoding/coding.
So how do i write? I use WYSIWYG editors. TinyMCE is great.
@econproph -- i do all my writing in wizzy editors. but the latest ones i use convert them to markdown, using that as the native format.
@econproph @davew Do you know what about Markdown makes it hard to read for you? Is it the extra characters around text? Or something about the rendering of fonts (monospace, single-size)?
my two cents, markdown makes it more difficult to read the text for everyone, because for links or images, for example, you have to look at the details, they don't collapse down to the word with a link. even someone with perfect vision issues has to stop and try to figure out what's happening. makes it hard to proof your writing.
@davew @fvsch @econproph This is why I usually use the footnote-link style when I'm writing Markdown. An example I wrote recently, not including the footnote definitions, which are at the end of the section. This doesn't completely eliminate the "you have to look at the details" problem, but it does reduce it enough to be manageable.
At that point, I think you wouldn’t be worrying about pulse-current
ratings; the MOSFETs would be capable of crowbarring the panels
continuously. This could be desirable for fire protection purposes:
an emergency signal could put the MOSFETs into a continuous crowbar
state, greatly reducing the risk of, for example, shocking someone or
continuing to contribute to an electrical fire. As of 2018 ISEP, [US
NEC §690.12 Rapid Shutdown of PV Systems on Buildings][1558] requires
“not more than 30 volts within 30 seconds of rapid shutdown
initiation” one meter from the point of entry inside a building for
this purpose.
However, for low-voltage circuits, possibly you might as well just use
MOSFETs in series with your load in the conventional way. If you were
running your panels at 200V or more, the advantages might be more
compelling: you’d need a bigger MOSFET to crowbar the panels, but your
9¢ BT152 could control 4kW instead of 720W.
In other SCR-related news, I found [the General Electric SCR Manual
from 01972][1557], a 712-page book that began as an appnote. On p.5
(28/712) it says that some thyristors might require a turn-off time
“as high as several hundred microseconds”.
@davew @econproph Ah, I guess that's an aspect of Markdown there I've always liked, because my prior experience was with Word and browser-based WYSIWYG editors hiding away important info like "where does this link start and end" and "where does it go", resulting in regularly broken content. But I can see how that's a bit noisy when looking at the flow of words.
@davew Yes, I use Markdown.
I've used it with WordPress for long time, then I've used Ulysses (a subscription based productivity app) to publish on WordPress directly. Now my site is switched to WriteFreely, and on my phone and tablet I use an app called GhostWriter, and another called Drafts.
@davew there is a very small site called pages.casa that lets you upload your MD files via SFTP and it renders them for you. You need to know FTP but at least there's no build step.
@techlifeweb -- but you can only render them on the service? do they provide web access for the markdown source code?
@davew Technically I'm both. I just don't write as often as I'd like because I feel like a hypocrite asking people to read my shit if I'm not reading regularly and have fucking crippling self esteem when I right something longer than a social media rant.
I like Markdown not necessarily for the syntax itself or technical end of it so much as the seemingly universal adoption and how it can even be intuitive when you're writing in plain text.
@davew I write my texts in Joplin or in Zettlr. And then I copy/paste them into the Wordpress-Editor. Most of the MD is rendered there without s problem. I am nonetheless not at all satisfied with the process and am looking for a better solution. What does scripting.com run on?
@kunstweilkunst — anything that involves copy paste is too much work.
scripting.com works, but setting it up is too complicated for others to use.
@davew I am a writer and a nerd. No idea why anyone uses Markdown. But then I have never understood the text editor wars ether.
@davew I dislike MD very much. I used to write in plaintext html, and found MD an unreliable (but unavoidable) substitute. I will admit it is perfect for tiny text boxes.
I write in Logseq, VSCode / Zed to write it.
I publish with Logseq, which I self-host.