I'm this close to archive.

Offen
#367 2 Kommentare 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 5 Tagen

@WebReflection arbeitet bereits daran.

Seit 07.11.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

help wanted

This is likely the only real issue I have with this project.

Folks, if you ask me to improve legacy methods such as live-collections, you are telling me you didn't read anything about this project and you are not contributing at all if not by forcing me to kill it.

I do not care about stuff documented and described as legacy support, meaning if your getElementsByTagNames('*') doesn't work, I don't care, and so it goes for anything that is a live collection which is documented to not work and you should stop writing code that trust any of those legacy methods ... I'd like to say "it's not you, it's me" ... but honestly "it's you, not me", because if you don't read the premises of this project and you just keep piling up issues when my last quest was for maintainers and contributors and nobody showed up, 'cause nobody is paying me to maintain this project and I am not using this daily neither, I am afraid you can use your noisy tokens to reproduce and replicate by all means this project in Rust, directly WASM, whatever it fits your bill because I have enough of irrelevant noise about a genuine project with a scope and goal most latest "issues reporters" didn't dare to even read is extremely disappointing from an OSS community driven project side of affairs.

If you never used AI to create your issue, use YE instead (Your Eyes - apologies for blind contributors, I know you fully understand not reading/understanding means, that's my current curse) to understand what we do here, how we do that, what's the goal and how we can improve.

If you are here pretending to contribute with tons of stuff nobody should need in 2026, fork this project and leave me alone, can you?

Thank you all for helping me out not killing this project already, 'cause I am doing my best out of my non-existent free time to move forward with stuff that matters (see latest CSS improvements) but I am not willing to stress myself out of your poor duty as OSS contributor.

Regards.

Vorherrschende Sprache
HTML
Sterne
2.1k
Forks
117
Ø Merge
4 T. 13 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus WebReflection/linkedom

Alle Issues in WebReflection/linkedom

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.