The power of ASD compelled me.

1. AGENTS.md is a contributor configuration file telling AI coding assistants how to work in the repo. It doesn’t say AI built the project any more than a .editorconfig file means VS Code wrote the code.

2. “Ready for use with LLM tools you choose” describes ONE OF WikiDocs’ use cases, not its construction.

3. The author of the project repeatedly says they coded it, not Claude coded it. Given they are a professional developer that created this project for use in their team, I am apt to believe them. See: https://www.youtube.com/watch?v=x2nVq9RbG54

4. Rule 7 and the expanded AI rules consistently use language like “your promotional post,” “if you are promoting a project,” and “if you are promoting a project where AI was used.”

I explicitly disclaimed affiliation in my post, because I have none. A community member sharing something they use is not a promotional post in the rule’s meaning. I refer you to direct precedent from one of our mod team:

https://lemmy.world/post/48847985/24538274

" Promo, to be clear, is a self promotion post. ‘I found a neat project’ doesn’t apply, because you aren’t affiliated and wouldn’t know how it was developed, if AI was used and how, etc. You also wouldn’t be trying to get stars, clicks, donations, or payment for that software, so the promotion rules do not apply. It’s just a regular post".

And discussed again by the same mod here:

https://aussie.zone/post/36810313/25081612

5. For your convenience, I have tagged the mod here, because you appear to be confused by how [AIT], [AIP] and [CBH] work while simultaneously wanting to police them. @curbstickle@anarchist.nexus

6. Your [META] thread is on lemmy.world. My post originates from aussie.zone. Whether that’s a temporary federation issue or just an oversight, you’ve opened a moderation discussion about my post somewhere I can’t easily participate in it, on a topic that has already been settled by the mod team, sticked and sign posted. That’s poor netiquette regardless of intent.

Shall we next audit every IDE autocomplete suggestion the dev ever accepted, look at their CV, review their commit history and inspect what they ate for lunch? Or can we just share cool things we find and let end users make up their own minds?

Good to know that Odysee is a legitimate alternative.

That intentional, for exactly the reason you imply: I refuse to pay exorbitant prices for RAM, GPUs, SSD…I will code my way around.

“Force has no place where there is need of skill”

1. No, it isn’t.

2. and even if it was, it’s not my project ; I’m simply sharing it. Tagging is required by devs that share their project.

Do you have any evidence to support your “this project is AI oriented” claims, per the forum rules?

https://lemmy.world/post/48725669

Boom motherfukka! I stayed up all night but POI population is DONE! I now have 1,809, dynamically generated, ZIM Wikipedia-linked POIs for Western Australia running entirely locally on my Raspberry Pi map server.

The POIs themselves come from the WA OSM dataset. This works because a lot of OSM features already carry wikipedia=* and wikidata=* tags…which gives me a link from a mapped place to its corresponding Wikipedia article.

I can then resolve those article titles against my locally hosted Kiwix Wikipedia ZIM and only publish POIs that actually exist in that local copy. I used wikipedia_en_all_mini_2026-06/Wikipedia ZIM (~13GB) as the test.

Meaning, clicking a marker now opens the article lead inside the map, fetched from Kiwix, with a “Read full article” link to the full locally hosted article (see pic)

And just to confirm - this is all local. No calls out to Wikipedia or Wikidata.

Seeing folks want this in their hot little hands, I’ll delay fucking around adding / solving those 4 outstanding ticket items and yeet this onto Github (after I get a few hours of sleep).

How do you find them as replacements?

To my reading of the rules, tagging is required when promoting a project. For reference, see -

https://lemmy.world/post/49151085

Specifically

Post Tagging

There are three types of tags for project promotional / AI posts.

    [CBH] - Code By Human - A project promotional post with a project that did not use AI in any capacity. No disclosure necessary.
    [AIP] - AI Project - A project promotional post with a project that used AI in development in any capacity. Disclosure is required for how it was used.
    [AIT] - AI Topic - A discussion topic that includes AI. This may be for a discussion on hardware to self-host on, llama.cpp vs ollama, your experience using vulkan, etc.

I am not promoting anything - the code literally does not exist outside of my hard-drive. I am sharing some small measure of success I’ve had in my own work.

If this is objectionable to the PttB, I am happy to remove this post.

TubeArchivist is:

1. heavy (Redis, Elasticsearch).
2. doesn’t have a native TV app.
3. will not play nicely with the Raspberry Pi (table stakes are 2 GB RAM, which is more than half my RAM budget).

I like TA a lot, but not for what I have in mind. What I have in mind should use about 100 MB of RAM, run as a systemd service, with videos served directly to the front-end via Samba, in such a manner that they are indistinguishable from the cloud sources when displayed in-app (well, apart from a core badge saying LOCAL).

I’m not coding a simple Jellyfin plug in.

You check them.

AI disclosure is required when posting a promotion. This is neither a promotion, nor AI coded. I am simply sharing something fun I made for myself by myself. If you have an objection to my post, click report and lets have the mods weigh in. In fact, here, let me help you. Tag - @curbstickle@anarchist.nexus

Yes in spirit, but it is a Docker Compose stack rather than one container. That works better for my set up. IOW nginx/MapLibre/PMTiles, the SQLite search service, and BRouter are separate containers, but they are managed as one project. Like this -

pi-maps          → nginx + MapLibre + PMTiles
pi-maps-search   → Python + SQLite FTS5
pi-maps-brouter  → BRouter

No, the battery swaps out (or at least the external one) - it’s attached by clips and pogo pins. Hell, you can deconstruct the battery and replace the cells yourself, if you’re technically inclined and know what you’re doing.

You’ll have to contact them directly, but I’ve have heard that they can service or replace the internal one too, rather than replacing the whole unit.

You don’t have to ditch the whole unit - what a waste that would be.

Contact them; they’re pretty responsive.

support.au@ecoflow.com

Here’s what I’m thinking:

• Driving-focused routing; easy. BRouter already supports separate car, bicycle and foot routing modes/profiles, and its server accepts a profile= per request. So that one is universal.

• Live turn-by-turn navigation and rerouting - should be easy. GPS position, route geometry, turn hints, destination coordinates and a local routing API are all sorted. The browser would track position against the active route, advance through manoeuvres as you approach them, detect when you move sufficiently off-route, then call BRouter again from current GPS position to the existing destination.

The main work is a navigation state machine…which…I might need to ask GPT or Claude for help tbh.

• Spoken navigation: probably the easiest next thing. Turn hints are already converted into human-readable text. If a browsers expose SpeechSynthesis (which can speak text through the device’s speech system) then…yeah, done. The navigation state says “150 m from next manoeuvre”, Pi Maps can literally issue speechSynthesis.speak(…).

For guaranteed offline speech you would want an on-device voice installed on the phone, but almost every phone has that (unless you cut TTS out).

• Address coverage - this one is a cheat…because we have Geocoded National Address Files here. G-NAF “…contains the details of every physical address in Australia, with more than 15 million addresses and coordinates, free to the public and updated quarterly”.

I’d be stupid not to use that (though I need to figure out the slice and dice). Obviously, that won’t translate to every place on Earth, but I am coding this for me, so … :)

What I can’t solve is the Traffic. Not really. I mean…sort of. Where I am, Main Roads WA exposes public ArcGIS services with incidents, roadworks, events, road closures, detours and traffic-signal outages, all queryable as JSON, all updated live. In theory, that means a live traffic layer with with road closures, traffic incidents, speed zones etc.

No live traffic congestion / data tho.

Let me sit on it for a bit. I never thought to release this…and these 4 are nagging me…but I really want to move onto the SmartTube project fully. Maybe I’ll just patch the first two or three low hanging fruit. The big issue is field testing it for weeks/months before I can call it properly done.

Honestly, I just wanted my own Google maps. I never thought to apply spit and polish for general release.

Ha ha! The external battery is user serviceable / replaceable :)

Welcome to the new disease: “can I run my home-lab entirely off grid”

I mean…if there’s interest? Just let me figure out those last four nagging pains in the ass and I will put it up. The thing itself is pretty simple lego: frontend, nginx config, SQLite/FTS search service, index-builder scripts, BRouter integration, route-anchor logic.

Right now, I have a few irons in the fire, including a fork called SmartTube Local that is turning into a passion project.

That one is basically: “what if YouTube was local-first, self-hosted and yt-dlp-backed, with the local archive integrated directly into the app and automatically kept up to date…so if the internet died, your kids might not even notice?”

…I just did google maps…why not take on Youtube next, amirite?

Dunno. Try it, see what happens. Probably nothing good :)

OTOH, if you have a local LLM, you should be able to get it to template your existing .md into a sane wiki structure.

Aha! Yes.

Dunno how much juice you need, but I am installing one of these, tied into solar and a smart power switch:

https://au.ecoflow.com/products/ecoflow-river-3-max-plus-portable-power-station

Part of the reason I chose it is exactly what you are talking about. It has a direct DC output, so you can avoid the battery DC --> AC --> router power supply --> DC conversion chain. I have a bunch of DC capable gear (Raspberry Pi, router etc) and I’d rather not incur the losses in conversion.

FWIW, the car-style DC outlet supplies 12.6 V at up to 10 A, or 126 W. So it has more than enough current capacity for a 12 V 5 A router. (It also has USB power, if that’s an option for you).

You’d still need to check whether your router is happy with 12.6 V rather than exactly 12 V though. You’d also need the correct barrel size and polarity.

On the plus side, It gives you 858 Wh of storage (depending on which model you do with), a <10 ms UPS transfer time, and enough AC output to keep quite a bit of your other electronic junk alive during a blackout or brownout.

In any case, please enjoy the delicious overkill. I’ve seen the River 3 plus + extra battery on sale for as low as A$599 / 420 USD. And yes, they can be charged by normal wall socket (and also yes, the DO pass-thru as well)

https://www.ecoflow.com/au/river-3-series-portable-power-station

Bold of them to assume I use Google.

On revisions, I am not actually sure how WikiDocs stores the old versions internally. The project advertises unlimited revisions and rollback despite using flat files rather than a database. So…dunno.

Gitit looks very capable too, especially if you already want Git as the storage and revision layer.

What appealed to me about WikiDocs was less that it had some unique technical trick and more that it packaged the things I wanted into one nice interface: Markdown files, WYSIWYG editing, namespaces, attachments, Mermaid, etc etc

EDIT: “WikiDocs stores revisions as timestamped Markdown snapshots alongside each page”.

my-page/
├── content.md
└── versions/
    ├── 1790201234567.md
    ├── 1790287654321.md
    └── 1790374567890.md