• [[zeno_dox]] https://twitter.com/zeno_dox/status/1523523167939039232 pull

• [[zeno_dox]] https://twitter.com/zeno_dox/status/1523327445776187392 pull

layout: post title: Validate Your Code created: 1077602040 categories:

• SEO
• validate
• W3C
• XHTML
• Search Engine Voodoo
• SEO
• validate
• W3C
• XHTML
• Search Engine Voodoo

It's surprising to me that many people still don't validate their code before publishing. An HTML or XHTML document, whether created by hand or by some script or content management system, is a set of instructions to the web browser on what (and how) to display content.

By validating your code, you ensure that your page conforms to an accepted set of standards. There are a number of different specifications for HTML that you can choose from. The W3C has made a number of recommendations, but the two that are most important are HTML 4.01 and XHTML 1.0. Very roughly speaking, HTML 4.01 is the last non-XML based dialect still in broad use. XHTML, quoting the W3C, is a reformulation of HTML 4.01 in XML, and combines the strength of HTML 4 with the power of XML.

Further, there are actually three "flavours" of XHTML 1.0. You will likely want to be working with XHTML Transitional most of the time, because of its backwards support for older browsers.

Now that we've covered the specifications that we will be vaildating to, the next step is to actually run the code through a validation service. Again, the W3C Validation Service will be the first stop. Why validate? Search engines are built to understand standard web page codes. Any code that doesn't conform to the standard will only confuse search engines, and we want to make the job of understanding your pages as easy as possible for them. As well, validation often points out problem areas that you may miss if you only look at the visual representation of your page.

• [[action code]]
  • the action engine in the [[agora]]
  • [[push]] [[do]]
    • currently in [[db.py]], to be refactored into action.py

• [[flancian]] https://twitter.com/flancian/status/1462349464971227140 pull

• [[alanz@social.coop]] https://social.coop/@alanz/109441018978845439 pull
• [[alanz@social.coop]] https://social.coop/@alanz/109445949304909404 pull

• #pull [[agora server]] [[agora bridge]] contain the code for this Agora.
  • [[go/agora/git]] is the Agora root.

Agora Vscode§

• A [[vscode]] extension for the [[Agora]].
• Builds on top of [[foam]], which focuses on tools for building and maintaining [[digital garden]]s.
• The Agora extension focuses on tools for building and maintaining digital forests (or groves; or topiaries?) assembled out of many digital gardens.

• Your First Extension | Visual Studio Code Extension API
• colors for existing/non-existing
• push
• go to agora link
• add agora content for note in preview view

[[Anil Dash]] May 2020, ‘No Code’​ is great. But here’s why we need Yes Code.

Anil goes into the rising trend of "No Code" tools, and goes a step further, saying that we should be focusing on "Yes Code".

Anil Dash is the CEO of [[Glitch]], which is embracing this "Yes Code" concept.

Yes Code  is based on three key ideas:

1. There are millions of important apps, websites, and projects that can’t be made by an off-the-shelf template
2. Being able to code is a superpower, and we should enable more people to tap into that ability, by lowering the barriers
3. The biggest barriers to coding are technical complexity around processes like collaboration and deployment, and social obstacles like gatekeeping and exclusion — so that’s what we’ve got to fix

Today’s internet isn’t fully serving the needs of a lot of people around the world. There may be great tools for sharing a photo or sending a message, but most of the sites and apps we use every day are made by a small number of companies with goals or incentives that might not match our own. We’re feeling the negative effects of that reality every day.

Ask yourself: When’s the last time you used an app, or visited a website, that was made by an actual individual  person ?

• Trying it for the first time on [[2025-08-10]].
  • Smooth onboarding experience!
  • npm install -g @anthropic-ai/claude-code did it.
  • Then logged in with my Pro subscription, let’s see how long that lasts when set loose on the [[Agora repository]] :)

DECODE§

DEcentralised Citizen-Owned Data Ecosystems

Experiments like DECODE have shown in practice that a different institutional configuration of digital infrastructure, public policy and citizen participation is possible and affordable.

– [[Platform socialism]]

city projects like DECODE(DEcentralised Citizen-owned Data Ecosystems) provide open source public interest tools for community activities where citizens can access and contribute data, from air pollution levels to online petitions and neighborhood social networks, while retaining control over data shared.

– [[Digital Ecosocialism: Breaking the power of Big Tech]]

Digital ecosocialist praxis takes the form of resist, regulate and recode§

Digital ecosocialist praxis takes the form of resist, regulate and recode.

This means resisting the current practices of big tech; regulating to stop the worst impulses of big tech; and building alternatives to big tech. All three are needed.

See [[resist, regulate, recode]].

• [[flancian@social.coop]] https://social.coop/@flancian/110146221227571051 pull

docs-as-models-as-code§

Core idea§

Coined by DOF team lead J, a philosophy that says that just like docs can be treated as code, docs can be treated as models, existing and version controlled and released alongside the rest of the model. The DOF initiative considers this practice essential to actualizing open source hardware.

Links§

[[DOF]]

• [[smallcircles@social.coop]] https://social.coop/@smallcircles/110077966608328765 pull

full unicode§

• As of now I prefer Full Unicode as a convention for filenames in the [[agora]]. It is less [[lossy]].
• I need to set up [[foam]] so it stops slugifying filenames.

Getting started with VsCode§

VsCode is a powerful text editor, hidden behind a simple interface.

Keyboard shortcuts§

VsCode supports various keyboard shortcuts, the most important for us are:

For more information, see the vscode keyboard cheat sheets, where you can also see how to customize your keybindings.

Commands§

Commands make VsCode extremely powerful.

To invoke a command, press cmd+shift+P and select the command you want to execute. For example, to see the Foam graph:

• press cmd+shift+P
• start typing show graph
• select the Foam: Show Graph command

And watch the magic unfold.

For more information on commands, see commands on the VsCode site.

If you want to learn more about VsCode, check out their website.

Panels§

You can see a few panels on the left, including:

• Outline: this panel shows you the structure of the file based on the headings
• Tag Explorer: This shows you the tags in your workspace, see [[tags-and-tag-explorer]] for more information on tags

Settings§

To view or change the settings in VsCode, press cmd+,

• [[wp]] https://en.wikipedia.org/wiki/High_Capacity_Color_Barcode pull
  • [[go]] [[wp]]

• [[flancian]] https://twitter.com/flancian/status/1487046956933332994 pull

• [[dougholton@mastodon.social]] https://mastodon.social/@dougholton/109461139586200746 pull
• [[mmlvx@mastodon.world]] https://mastodon.world/@mmlvx/110506997892057695 pull

Infrastructure as code§

Introduction au code source§

N’ayez pas peur ! Le code est écrit de manière accessible afin que vous puissiez y contribuer facilement. Si vous êtes à l’aise avec les méthodes plus “standard” dans l’industrie, il est possible de coder de votre côté et de communiquer via l’API.

Les discussions publiques de l’équipe de développeur se font dans le canal #codev_open.

Ressources pour débuter§

• Présentation du code en vidéo (30 minutes)
• [Documentation de l’API](/4 - Documentation technique/api.md)
• Fonctionnement PHP
• Communauté des développeurs
• Pense-bête de commandes GIT
• Feuille de route des développeurs

Architecture§

Le motif utilisé est le classique Modèle-vue-contrôleur. Une grosse partie du code se trouve dans le dépôt CO2 de notre Gitlab, tandis que citizenToolKit gère plutôt le backend.

Introduction au code source§

N’ayez pas peur ! Le code est écrit de manière accessible afin que vous puissiez y contribuer facilement. Si vous êtes à l’aise avec les méthodes plus “standard” dans l’industrie, il est possible de coder de votre côté et de communiquer via l’API.

Les discussions publiques de l’équipe de développeur se font dans le canal #codev_open.

Ressources pour débuter§

• Présentation du code en vidéo (30 minutes)
• [Documentation de l’API](/4 - Documentation technique/api.md)
• Fonctionnement PHP
• Communauté des développeurs
• Pense-bête de commandes GIT
• Feuille de route des développeurs

Architecture§

Le motif utilisé est le classique Modèle-vue-contrôleur. Une grosse partie du code se trouve dans le dépôt CO2 de notre Gitlab, tandis que citizenToolKit gère plutôt le backend.

• [[rmdes@mstdn.social]] https://mstdn.social/@rmdes/110518774087851452 pull

• [[go]] https://jabcode.org/
  • "just another [[bar code]]"
  • [[2d]] [[color]]

• [[flancian]] https://social.coop/@flancian/107700198875280017 pull
• [[flancian]] https://social.coop/@flancian/109002492620162147 pull

• [[flancian]] https://twitter.com/flancian/status/1487046956933332994 pull
• [[flancian]] https://twitter.com/flancian/status/1570394481727348738 pull

• [[ctc@mastodon.me.uk]] https://mastodon.me.uk/@ctc/109937649329025556 pull
• [[ctc@mastodon.me.uk]] https://mastodon.me.uk/@ctc/109948976547670905 pull
• [[ctc@mastodon.me.uk]] https://mastodon.me.uk/@ctc/110502005084313727 pull
• [[ctc@mastodon.me.uk]] https://mastodon.me.uk/@ctc/110514973188377180 pull

• [[ctc@mastodon.me.uk]] https://mastodon.me.uk/@ctc/109783352228072309 pull
• [[ctc@mastodon.me.uk]] https://mastodon.me.uk/@ctc/109813078790289205 pull
• [[ctc@mastodon.me.uk]] https://mastodon.me.uk/@ctc/109822763611721340 pull

• [[flancian]] https://social.coop/@flancian/109002097513971794 pull

• [[flancian]] https://twitter.com/flancian/status/1570368946368544768 pull

• [[flancian@social.coop]] https://social.coop/@flancian/113418686104963054 pull

• [[2024-11-03T11:03:56.684Z]] @[[flancia.org]]: https://bsky.app/profile/did:plc:xu4fhdxwmrptiwfvq5ymbkxx/post/3la22jxkumj2u pull

• [[2024-11-03 11:03:27+00:00]] @[[flancian@social.coop]] (link):

  • Meanwhile in the Morse web

    GitHub - dmd/morse: [[Morse code]] to email
    https://github.com/dmd/morse

• [[Binder@petrous.vislae.town]] https://petrous.vislae.town/@Binder/110669500511783798 pull
• [[Binder@petrous.vislae.town]] https://petrous.vislae.town/@Binder/110672985503237014 pull

Public Money, Public Code§

• https://publiccode.eu/

We want legislation requiring that publicly financed software developed for the public sector be made publicly available under a Free and Open Source Software licence. If it is public money, it should be public code as well.

• [[pull]] [[quick response code]]
  • [[wp]] https://en.wikipedia.org/wiki/QR_code pull
    • invented in [[1994]] by [[denso wave]]

• [[flancian@social.coop]] https://social.coop/@flancian/113056602137828340 pull

• [[2024-08-31 12:20:44+00:00]] @[[flancian@social.coop]] (link):

  • [[qr code]] generator

    https://fietkau.social/@julian/113055759198127054

Qrencode§

• apt-get install qrencode
• qrencode "text or url" -o qr.png

resist, regulate, recode§

See [[Platform socialism]].

• [[The triad of digital transition strategies]].

• I found this node on [[2025-09-05]] after an adventure with [[Ishmael]] in [[BMI]].
• [[neil]]‘s nodes are the best IMHO!

• I found this node on [[2025-09-05]] after an adventure with [[Ishmael]] in [[BMI]].
• [[neil]]‘s nodes are the best IMHO!

• I found this node on [[2025-09-05]] after an adventure with [[Ishmael]] in [[BMI]].
• [[neil]]‘s nodes are the best IMHO!

• I found this node on [[2025-09-05]] after an adventure with [[Ishmael]] in [[BMI]].
• [[neil]]‘s nodes are the best IMHO!

Swiss Wiring Code§

• For electrical systems; relevant mostly for installing lamps in my case. Source: https://www.englishforum.ch/other-general/160978-swiss-wire-coding-electricity.html
• Green/Yellow = Earth
• Light Blue (or yellow in old systems) = Neutral
• Black, White or Red = Live
• All colours (except green/yellow, Light Blue and Yellow) = Switched Live.

• #go https://unicode-table.com/

• [[jonny@social.coop]] https://social.coop/@jonny/109916333919028754 pull
• [[youronlyone@c.im]] https://c.im/@youronlyone/110127434119173648 pull

• [[flancian]] https://social.coop/@flancian/107846474118809202 pull
• [[flancian]] https://social.coop/@flancian/108301072315431531 pull
• [[jonny@neuromatch.social]] https://neuromatch.social/@jonny/110398271915690505 pull
• [[jonny@neuromatch.social]] https://neuromatch.social/@jonny/110398275393938872 pull

• [[flancian]] https://twitter.com/flancian/status/1496408959653195779 pull
• [[flancian]] https://twitter.com/flancian/status/1525502613021675520 pull

Extensions§

Extensions that I use.

Formatting§

• JSDoc Folder. Automatically folds documentation comments. Combined with Prettier and prettier-plugin-drone-jsdoc for elegant handling of symbol summaries.
• space Camel. Adds virtual spaces to camelCase/PascalCase.

Audible editor§

I enjoy sound feedback in software. There are extensions that enable this. Some of them seem to be based on the play-sound [[npm]] package. play-sound performs poorly on a default Windows setup but adding MPlayer to PATH helps to prevent the media player from opening.

• TypaTone (Keyboard sounds). Based on TypaTone.
  MPlayer has a quirk when playing back sounds shorter than one second when invoked from Node.js. I’m not sure why this happens, but it does æffect playback of sounds from this extension. This cause sounds to loop forever until manually killed. My workaround is to manually edit the extension after installation and pad out æffected sounds.
• Sound Syntax.
• Rainbow Fart.

Accessibility and signals§

Visual Studio Code has accessibility features. Signals are one of them. These are enabled when a screen reader is detected. However, there is a way to force them on, providing an audible experience regardless of whether a screen reader is being used.

In a configuration, an enabled set of signals look like this:

{
	"accessibility.signalOptions.volume": 100,
	"accessibility.signalOptions.debouncePositionChanges": false,
  	"accessibility.signals.save": { "sound": "userGesture" },
	"accessibility.signals.format": { "sound": "always" },
	"accessibility.signals.lineHasError": { "sound": "on" },
	"accessibility.signals.lineHasWarning": { "sound": "on" },
	"accessibility.signals.lineHasFoldedArea":  { "sound": "on" },
}

There are way more signals. Type in “accessibility.signals” and let it autocomplete the rest.

Best practice with VS Code§

Vscode§

• A [[code editor]].
• Hosts [[foam]], a [[vscode extension]] which is the main client (as of [[2020-11-22]]) for the Agora.
• Perhaps will eventually have an [[agora vscode]] extension.

• [[smallcircles@social.coop]] https://social.coop/@smallcircles/109771440752672276 pull
• [[smallcircles@social.coop]] https://social.coop/@smallcircles/109822402850962787 pull
• [[smallcircles@social.coop]] https://social.coop/@smallcircles/109852102735259544 pull

• [[flancian@social.coop]] https://social.coop/@flancian/109673425881069622 pull
• [[rmdes@mstdn.social]] https://mstdn.social/@rmdes/110461958769154813 pull
• [[flancian@social.coop]] https://social.coop/@flancian/113353576136414324 pull

• [[flancian]] https://twitter.com/flancian/status/1452414302720299017 pull
• [[flancian]] https://twitter.com/flancian/status/1475504004943818755 pull
• [[flancian]] https://twitter.com/flancian/status/1481928898858434560 pull
• [[flancian]] https://twitter.com/flancian/status/1504006256767418378 pull

• [[2024-10-24T23:33:36.329Z]] @[[flancia.org]]: https://bsky.app/profile/did:plc:xu4fhdxwmrptiwfvq5ymbkxx/post/3l7c7rbz75n2v pull

• [[2022-04-27 01:27:02]] [[@vera:fairydust.space]] (link):
  • TIL you can add multiple folder roots to single workspace in [[vscode]]

• [[2023-01-12 00:34:31+00:00]] @[[flancian@social.coop]] https://social.coop/@flancian/109673425881069622:

  • [[vscode]] just crashed on me hard while I was editing a file.

    Honestly I know it’s not cool but this is why I personally keep coming back to just coding on vim/nvim. They don’t leave you hanging. In particular I can’t remember a single time [[vim]] crashed on me in 20 years, even while using lots of plugins.

• [[2024-10-22 23:05:07+00:00]] @[[flancian@social.coop]] (link):

  • I sort of can’t believe that [[vscode]] ships in a state in which it tries to “helpfully” auto-close brackets, quotes, tags for you. It is ~never what I want personally.

    To disable:

    - ctrl+, to open settings
    - search for autoclosing
    - disable to your heart’s intent

    Enjoy if this is your kind of thing :)

Why do you code?

It depends on what it means to "code.".

I’ve started various projects. Zhe ones public on GitHub are somewhat organized https://github.com/BunnyNabbit?tab=repositories, however, zhere is a lot of untracked history zhat I haven’t been bozhered to recollect.
I like maintaining open source projects and I zhink zhat [[programming]] is a creative work. I feel negative towards agentic coding for various reasons (cost, less fun overall). Actually, I zhink zhat coding is fun, zhat [[I know what my code did]], how I could solve problems. Agentic coding takes zhat away, haven’t turned to it since.
However, coding can be unfun. Technical debt can take a big toll on zhe maintainer. Many of my earlier projects fell victim of poor [[structuring]]/coding practices (keeping everyzhing in a single file, for example.).

For projects, zhough. I’m a bit on a rough spot of what to contribute lately.

• starting a project for people to use (i.e.: a game), is really tough to get any sort of attention.

Pretty cool stuff