go-readability
website
go-readability | website | |
---|---|---|
2 | 9 | |
131 | 141 | |
- | 2.1% | |
0.0 | 8.6 | |
almost 2 years ago | 8 days ago | |
HTML | HTML | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-readability
-
Which library/project do you wish was ported to golang?
https://github.com/go-shiori/go-readability https://github.com/mauidude/go-readability
-
Blog with Markdown and Git, and degrade gracefully through time
In terms of extracting the actual blog content from pages, there is a go library that implements the readability algorithm:
https://github.com/mauidude/go-readability
This is the kind of thing pocket/instapaper do to extract the main content from a page in a format that's easier to read (and also probably to programmatically modify)
website
-
35M Hot Dogs: Benchmarking Caddy vs. Nginx
Oh, just saw this. You wrote your comment while I wrote mine. If you can enumerate specifically what you want to see, please submit it to our issue tracker: https://github.com/caddyserver/website
Generally we encourage examples in our community wiki though: https://caddy.community/c/wiki/13 -- much easier to maintain that way.
-
Caddyhttp: Enable HTTP/3 by Default
Yes, the docs have been updated at https://github.com/caddyserver/website but haven't been deployed yet. There is a new protocols option:
protocols h1 h2
- The appeal of using plain HTML pages
-
Show HN: Caddy v2.5.0
Could you be more specific about these complaints? What examples don't work? We can't work on improving the docs if we don't get specific and actionable feedback. The docs are found at https://github.com/caddyserver/website if you want to propose any changes.
-
I'm Using SNI Proxying and IPv6 to Share Port 443 Between Webapps
Protip: you can click almost everything in code blocks in the docs. For example, if you click `[]`, it brings you right to the request matcher syntax section, which explains what you can fill in there.
It would be redundant to write on every page what you can use as a matcher. The Caddyfile reference docs assume you've read https://caddyserver.com/docs/caddyfile/concepts which walks you through how the Caddyfile is structured, and it'll give you the fundamentals you need to understand the rest of the docs (I think, anyway).
If you think we need more examples for a specific usecase, we can definitely include those. Feel free to propose some changes on https://github.com/caddyserver/website, we could always use the help!
- Generate Static Sites from Markdown Files with Caddy
- Blog with Markdown and Git, and degrade gracefully through time
What are some alternatives?
docs - This is a repo of the RetroArch official document page.
neocities - Neocities.org - the web site. The entire thing. Yep, we're completely open source.
blissue - A blog based on github issues
wayback-machine-downloader - Download an entire website from the Wayback Machine.
simonwillisonblog-backup - Backups of the database for simonwillison.net
temporalite-archived - An experimental distribution of Temporal that runs as a single process
souin - An HTTP cache system, RFC compliant, compatible with @tyktechnologies, @traefik, @caddyserver, @go-chi, @bnkamalesh, @beego, @devfeel, @labstack, @gofiber, @go-goyave, @go-kratos, @gin-gonic, @roadrunner-server, @zalando, @zeromicro, @nginx and @apache
bdv32 - This is my website
beleyBlog - The non-content portion for my blog at www.chrisbeley.com
Vegeta - HTTP load testing tool and library. It's over 9000!