The Key Principles of the IndieWeb.

— Own your data, content, metadata and your identity.
— Publish data for humans first, machines second.
— Scratch Your Own Itches. Make tools, templates, etc. for yourself first.
— Use what you make!
— Document your stuff.
— Open source your stuff!
— UX and design is more important than protocols, formats, and data models.
— Build platform agnostic platforms.
— Longevity. Build for the long web.
— Plurality.
— Have fun.

indieweb.org/principles

* Further on that null
@emsenn

In this snippet, I have replaced the NULL with ROLLING ON THE FLOOR
LAUGHING unicode. Basically use any char/string in those 2 places
which *you* will never type in your toots :)

ptpb.pw/FO7O/elisp

[1/1]

* Clarification about the previous toot
@emsenn

Note that on line [16], I have "\\&<NULL>" and on line [17], I have
the same null in "<NULL>"; they are not visible in that snippet!!

Emacs shows null chars as "^@" in some highlighted color.

- ptpb.pw/NODD/elisp#L-16
- ptpb.pw/NODD/elisp#L-17

[1/1]

* Hello from Org mode
@emsenn

Try this out: ptpb.pw/NODD/elisp

This needs you to first install mastodon.el.

- Test toot from an Org mode subtree.

[1/1]

@emsenn There's already mastodon.el that works wonders: github.com/jdenen/mastodon.el

You can then have some binding to send the current Org mode subtree contents as a payload of a toot and send it via mastodon.el.

It would be a good elisp exercise :)

Just discovered bridgy fed [1], the indieweb's bridgy fediverse-compatible.

How did I manage to miss that!

Just need to display the interactions on my website and I'm good to go :)

[1] https://fed.brid.gy/

@jrss

> display line numbers in a babel code block?

You mean the Org source blocks? (`#+begin_src ..`). I don't think you can display line numbers in there (but I could be wrong.. just that I never felt the need to do that).

> try to use -n after the declaration of the code (I think that's the right term), but nada.

The `-n` syntax is only for Org exports. You will see the line numbers once you export the code (example: ox-hugo.scripter.co/doc/source)

@alexjgriffith Well, I have my dev build static binary of public if you like to try. It will work on any 64-bit GNU/Linux OS.. so your Ubuntus would be eligible.

The new (not yet released, but to be released very soon in Hugo v0.50) is super awesome!

When running `hugo server`, error introduced in layouts is shown instantly in the browser. See gif[0].

[0]: discourse-cdn-sjc2.com/standar

@jrss

There are dozens of themes with social links.

I'd just go through them and learn the Go templating needed to do that, slowly, at my own pace.

@jrss

> how hard would it be (or not hard at all?) to include social links in hugo

The difficulty level is subjective. In general, it's not hard once you got the Go templating basics.

> Or is that something that Hugo has somewhere?

No, I am glad Hugo doesn't have that by default, because there isn't one "right" way to do this.

> do you personally think it's worth it?

That's subjective too. I add links to my social profiles at the bottom on my blog pages.

[1/2]

Hey!

I wrote a small write-up about the e-ink computer/digital typewriter I made 4 months ago.

https://alternativebit.fr/posts/ultimate-writer/

For the past few days, I'm having some fun implementing () in : github.com/kaushalmodi/elnim

Getting that "Woah! That's crazy cool!" feeling as I am learning Nim macros in the process.

@sir I think I would have contributed orgMode syntax highlighting to Pygments if it were on git (I did that to Chroma).

Tip:

Don't use Mercurial

Don't use BitBucket

@sir I thought I saw you mention at times (may not?). If so, look into pygments-equivalent-in-Go: : github.com/alecthomas/chroma

Show more
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!

We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface as a moderator.

Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!