I just like this image so much.

GM and fuck the government! One of my favourite anarchist performance from Benny Wills.

There is no single correct implementation of NIP-54 (wiki). Although asciidoc promises you need not shave yaks to add new functionality into asciidoc convert, it is not true. Go and buy shaving foam and razors in bulk because you'll need that. Asciidoc extensions cannot hook into the conversion of inline elements, which makes it difficult to selectively replace wikilinks in literal code blocks (`+blabla+`) but not in monospace blocks (`blabla`). To replace wikilinks, you have to parse asciidoc manually, line by line before sending it to the Asciidoc.convert method. proof 1: https://wikifreedia.xyz/asciidoc/lez@nostr.hu proof 2:https://wikistr.com/asciidoc*cfd7df62799a22e384a4ab5da8c4026c875b119d0f47c2716b20cdac9cc1f1a6 But the bigger issue with asciidoc is the `+...+` syntax for inline code snippets. Since decades, programmers are trained to use simple backticks for inline code, without formatting. We will never ever change habits to use `+code-snippet+` syntax. This is an utterly strange decision from asciidoc. It should be the opposite way: simple backticks for code snippets, and an additional plus sign if text formatting is needed. And the list goes on, since asciidoc is packed with features. The wikilinks format [[xxx]] is actually an existing asciidoc feature: anchors. Fortunately there are another 2 alternative syntax for that: [#xxx] and [id=xxx], so wikilinks don't cause a big trouble here. If I had a wiki (which I have, actually: https://tribewiki.org), now it would be high time to reconsider the storage format. Gitlab flavoured markdown is a strong candidate, with all the important features and a WYSWYG editor. This might bring in non-tech people, like activists, too.

@Silberengel @liminal 🦠 I'm also building on asciidoc, and I just got to the point where I'm busy disabling / hiding asciidoc features in order to ship in time. I had my asciidoc moment. Have you had this experience?

Red – Colour of passion Orange – Colour of freedom Yellow – Colour of hope Light green – Colour of peace Dark green – Colour of love Blue – Colour of joy Indigo – Colour of understanding Purple – Colour of confidence Magenta – Colour of harmony Turquoise – Colour of wholeness

Ki Science | Ki Science

Coloured Glasses Set | Ki Science

Advanced Autonomic Response Testing (A.R.T.) Tool. Coloured glasses set - 10 pairs Comes with a specific black foam case which can accommodate the ...

Setting up my Librewolf

GM! Water has a 4th phase. https://videos.dyntube.com/videos/exp-i5Yz0RN8b0Ctw3X0mRxgwg

Girl had her contracts cancelled because she wouldn't change the lyrics. Was offered to be a superstar, instead she stuck with her truth. Saylor calls her poor, I call her hero. Enjoy!

Truly great, almost emotional. View quoted note →

It seems that serving NIP-05 nostr.json with a correct "Access-Control-Allow-Origin" header is not common at all. To the degree that it's not useful at all in web clients to show all the warnings. It's a distraction ritght now. Maybe we could solve that with DVMs fetching and caching nip-05 data.

I'm releasing a relay that is a $HOME for tribes. It is willing to store events for tribe members. The basic vision is that when newbies join Nostr via a tribe, they get immediate access to a relay that stores their events, therefore act as their home relay. In its current form it's quite similiar to @fiatjaf's khatru-pyramid, but implemented with nostr events instead of relay auth.

GitHub

GitHub - lez/khatru-tribe: Home of nostr tribes

Home of nostr tribes. Contribute to lez/khatru-tribe development by creating an account on GitHub.

The vision includes blossom servers, NIP-96 media servers, and whatever servers are coming in the future automatically host tribe members' content and provide services to them. The idea is to be able to carry the tribe membership a.k.a. the initial social net between applications. And at the same time provide some defence against the reply guys / gals. Ideally, there should be also a community UI that provides an initial supporting community for the newbies, which also uses the same relay(s), so it should just work out of the box, without any pre-configuration of relays. They can help navigate the newbies through the rough path that nostr is today. And they can provide the social inspiration to come back every day. There's a lot more to come in the next few weeks. Some community UI, a tribal knowledge base (wiki) and more. Stay tuned. View quoted note →

Publishing a new way to organize communities, called Tribes. Looking for some feedback!

GitHub

nipls/tribe.md at main · lez/nipls

Contribute to lez/nipls development by creating an account on GitHub.