libmedium
libmedium copied to clipboard
An Alternative Medium Frontend | Development continues at: https://git.batsense.net/realaravinth/libmedium
My local copy says ``` libmedium-7ff7db5b79-586gv libmedium thread 'actix-rt|system:0|arbiter:0' panicked at src/data.rs:183:73: libmedium-7ff7db5b79-586gv libmedium called `Option::unwrap()` on a `None` value libmedium-7ff7db5b79-586gv libmedium thread 'actix-rt|system:0|arbiter:0' panicked at src/data.rs:183:73: libmedium-7ff7db5b79-586gv libmedium called...
These can be viewed through Google/Bing's cache for example. Example URL: https://medium.com/@steve_mullen/an-introduction-to-lean-canvas-5c17c469d3e0 Here's a tool that can read it: https://www.smry.ai/proxy?url=https%3A%2F%2Fmedium.com%2F%40steve_mullen%2Fan-introduction-to-lean-canvas-5c17c469d3e0
In the first paragraph of [this article](https://medium.com/@mustafaakin/indexing-icloud-photos-with-ai-using-llava-and-pgvector-fd58182febf6), the author includes a small `` block: ```html ``` When rendering this article [via libmedium](https://md.vern.cc/@mustafaakin/indexing-icloud-photos-with-ai-using-llava-and-pgvector-fd58182febf6), the parser doesn't realize that the `` is...
https://github.com/libreddit/libreddit/discussions/709 Like Libreddit, the name of the project includes the trademarked "Medium" so the project is in risk of trademark infringement. Pls rename the project
``` thread 'actix-rt|system:0|arbiter:0' panicked at 'called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Decode, source: Error("expected value", line: 1, column: 1) }', src/data.rs:156:22 stack backtrace: 0: 0x562f2586073a - std::backtrace_rs::backtrace::libunwind::trace::h79937bc171ada62c...
https://pagespeed.web.dev/report?url=https%3A%2F%2Flibmedium.batsense.net%2F&hl=en&form_factor=desktop 
https://validator.w3.org/nu/?doc=https%3A%2F%2Flibmedium.batsense.net%2F 
https://webbkoll.dataskydd.net/en/results?url=http%3A%2F%2Flibmedium.batsense.net%2F 
This issue tracks all rendering bugs in libmedium. To report a rendering bug, please comment the URL of article which caused the bug and I'll try to investigate and fix...