Also, am considering using the site's directory name as the default name so you could just type bin/mkws instead of bin/mkws https://example.com, assuming you have the source files in an example.com directory.
@adi@prologic But maybe I could work with the HTML before them and bake microformats in more semantically while keeping stuff simple? Did the HTML get more complex with the addition of mf2? Did you add tags without affecting functionality there?
@adi@prologic \n\n> I think you want the version before I added mf2 support? π€ Shall I just make that a configuration option?\n\nNeah, I'd rather have microformats by default.
@mckinley I don't believe so, is that I read "anti-social social media" as "anti social media social media" because https://twtxt.net/ is not "antisocial"/"anti-social" but twtxt would be as you put.
I'm going to host a yarn instance at https://c.mkws.sh for community purposes but I have to work on yarn's HTML output as I believe it could be better and skin it accordingly.
@maya \n\n> Twtxtβs original spec is like taking a 140 character long string of text, loading it into a cannon, and shooting it off into space.\n\nThat would be "antisocial" as I wrote it and what you ment by "anti-social".\n\nYeah, twxt and https://twtxt.net/ kinda overlap. I would say yarn would be "anti social media social media", as joke, truth is I personally am neither anti nor pro anything.
@jlj π, glad you're having fun, just saw https://nfld.uk/, looking cool! π\n\n> Now I need some content. ;-)\n\nWouldn't worry about that, I constantly get content ideas for both of my sites while not actively looking for them.\n\n> Built with mkws.sh\n\nCould you update this link so it would say just \n\n> Built with mkws\n\nI would say mkws is the name of the program and mkws.sh is the name of the web site?
@prologichttps://mckinley.cc/blog/20210831.html\n\n> I've recently become active again on twtxt.net, the platform that puts the "social" in "anti-social social media".\n\nIt's not antisocial to be clear. Maybe it would be better put as "anti social media social media". π
@lohn@eldersnake@adi Stuff has some comments and may be a little broken (from the unpublished stuff I showed you) because I added selectively serving .gz, .br, uncompressed files tonight so it's a good idea to fix some scripts.
@adi@lohn@eldersnake \n\n> A common practice in SSG is to separate the code/content/siteready. As I understand now, #mkws puts almost everything in the root dir. There is a way to separate those things?\n\nYou could do, assuming mkws is in your $PATH, do something like:\n\n MKWSTHEMEDIR=/path/to/share/dir mkws https://example.com /path/to/src/dir\n\nIt would get you the output in the current directory tho.\n\nYou could also just output elsewhere from bin/mkws.\n\nI however recommend publishing the sources also, keeping sensitive info in ENV vars.=
@lohn \n\n> I learned a lot of Hugo looking as otherβs solutions. Do you have some other theme option for #mkws?\n\nFor now I have all the source files also on https://mkws.sh/ and https://adi.onl (s/html/upphtml/g in urls, e.g. https://mkws.sh/index.htmlhttps://mkws.sh/index.upphtml,https://mkws.sh/docs.upphtml) maybe @eldersnake could also give you his sources, he was also very satisfied, the other weren't so brave. π\n\nI recommend distributing the sources of the website, you can hide sensitive information in environment variables.
@lohn \n> Almost every thing I think to do Iβll have to mod #mkws mkws.sh file. Is there the expected behavior or am I imagine things?\n\nNot necessarly _expected_ but recommended skips writing config files, do your config in code, and don't restrict your self to /bin/mkws, script the whole thing. There's not much to upgrade in /bin/mkws, if any. I believe any config I'll ever add is Markdown front matter, some variant of it.
@lohn \n> There is an out of the box way to #mkws to create posts pages based in a list of Markdown files in a directory? And generate a list of those posts?\n\nNot right now, you could look here for inspiration https://mkws.sh/blog.upphtml\n\nThep directory is basically:\n\n |adi@huike ~/s/m/p ls -1\n 2021-02-28 15:34:42 Welcome\n 2021-02-28 15:35:21 How to add a navigation menu\n 2021-02-28 15:35:39 How to add custom titles\n 2021-03-09 19:45:23 How to render Markdown\n\n/bin/mkws is https://mkws.sh/bin/mkws~
@adi@prologic (Here are some other goodies I have: https://mkws.sh/bin/precommit - inspired by gitpre-commit hook, run linters, validators, and shellcheck in this script https://mkws.sh/bin/dv - run _dev_ environment: monitor files, start development web server, live reload offered by https://livejs.com/, scripts also recompiles/restarts web server, nice to have when playing with headers https://mkws.sh/bin/d - wrapper for above script, runs it via doas because I have to access TSL certs https://mkws.sh/bin/up - deployment script)
@prologic \n\n1. That's illegal, right?\n2. It would be nice to have VPS I can automatically ssh into build the binaries there, and copy them back on the https://mkws.sh server. That's how I build the Linux version.\n\nHere is my current build script: https://mkws.sh/bin/mkws
@prologic@mckinley\n\n> Oh wow! π³ Like just straight up deleted?! π€ Thatβs a bit harsh no? π\n\nMy opinion exactly, no archive for a few months I guess?
@prologic Removing DMs would definitely remove any trust/privacy issues between users and pods owners because users wouldn't need to trust the pod owner regarding their privacy. That's how trust works, trustworthy people/tech don't need to be trusted.
One of my problems with self hosting is the lack o visual consistency between pieces of software. Maybe it would be a good idea to develop some sort of "skinning" standard.
\n