Project appears unmaintained — community forks available

Abierto
  • ¿Algo no está bien?
#39 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Refactorización
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
go
Área
cli

Línea de trabajo

Comienza revisando el fork de la comunidad enlazado y el README y las configuraciones de ejemplo del repositorio; después inspecciona las issues #10, #16, #20, #23, #27, #28, #30, #31, #33, #36 y #37 para separar las correcciones propuestas del trabajo pendiente. Darlo por terminado requeriría un plan de mantenimiento acordado o issues de seguimiento específicas, en lugar del amplio conjunto de cambios descrito aquí.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

It seems this repository has not been actively maintained since 2021. There are currently 11 open issues and 5 open PRs, some dating back several years, with no responses from the maintainer. The project cannot be built with modern Go (>= 1.22) due to the deprecated Gopkg dependency management, and the example configs contain deprecated Chromium flags.

I asked Claude to get this to work on my laptop, and also to have a look at outstanding issues and pull requests. The results are available at https://github.com/tobixen/captive-browser. It's totally "vibe-coded", I haven't even bothered to look at it - but I would guess it's in a better state than the original project. There is also a fork available at https://github.com/pacoorozco/captive-browser that seems maintained.

Claude claims to have incorporated those fixes from community contributions and added those new features:

  • Go modules migration — builds with modern Go (addresses #23, #33)
  • Fixed deprecated --host-resolver-rules flag — replaced with --proxy-bypass-list in all configs (closes #31)
  • Added --disable-features=HttpsUpgrades — prevents Chromium from breaking captive portal HTTP pages
  • NetworkManager support — nmcli-based DHCP DNS detection (addresses #10)
  • Wayland support — --ozone-platform=wayland for Sway, Hyprland, etc.
  • Firefox config — comprehensive privacy-hardened config from community contributions in #20
  • Improved README — better docs, troubleshooting section (addresses #16, #23, #28, #37)

It did not touch #27 (KDE integration - wishlist item, and I don't use KDE myself), #30 (should be fixed, but wasn't considered low-hanging fruit by Claude) not #36 (Windows support - I don't use Windows).

Dear maintainer - if you happen to read this, I would ask you to either spend some few hours on maintenance here, or share the maintenance-burden with someone else. I don't think I'm the right person for it, for me this is just "yet another rabbit hole" that I would have avoided falling into if I couldn't have outsourced it to the AI - but I would accept such a role nevertheless.

Lenguaje dominante
Go
Estrellas
483
Forks
30
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FiloSottile/captive-browser

Todos los issues de FiloSottile/captive-browser

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.