Medium has their RSS feed right here https://help.medium.com/hc/en-us/articles/214874118-Using-RSS-feeds-of-profiles-publications-and-topics

Requesting bridge support for Medium website

Try to keep the original feed icon.

I would like to work on this (considering integrating php-bridge into selfoss rss reader). Of course I would make sure all previous modes of usage are supported.

I'm looking at https://dokku.com currently. Small, selfhosted paas in the likes of heroku. Would work with a vps

That's awesome!

I think if we do one big cleanup, it would make sense to prepare the whole testing scenario first and then make it mandatory (and rework all older bridges) to include a test section like in #2108 .

Then, this test could be run regularely and even open up new issues automatically if you do it right :)

This is a great idea. I've gone through and found 20 issues and 2 pull requests that can be closed https://gist.github.com/VerifiedJoseph/538d693834cee8a24c136380d875b2b7

I have the feeling that there are many bridges that are still included in rss-bridge that dont work anymore and have been known for a long time.

Ideally, we need a tool that runs regularly to test each bridge and report broken ones so they can be fixed or removed. I've written a very basic script for checking each bridge's URI.

• Add timestamp and other info related to article.
• Remove the option 'Full Article' checkbox from the parameters.
• All the articles will have their full-text by default.
• Some article that requires JS to do interactive thing will not be supported.

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

Bumps urllib3 from 1.25.8 to 1.26.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/urllib3/urllib3/releases">urllib3's releases</a>.</em></p> <blockquote> <h2>1.26.5</h2> <p>:warning: <strong>IMPORTANT: urllib3 v2.0 will drop support for Python 2</strong>: <a href="https://urllib3.readthedocs.io/en/latest/v2-roadmap.html">Read more in the v2.0 Roadmap</a></p> <ul> <li>Fixed deprecation warnings emitted in Python 3.10.</li> <li>Updated vendored <code>six</code> library to 1.16.0.</li> <li>Improved performance of URL parser when splitting the authority component.</li> </ul> <p><strong>If you or your organization rely on urllib3 consider supporting us via <a href="https://github.com/sponsors/urllib3">GitHub Sponsors</a></strong></p> <h2>1.26.4</h2> <p>:warning: <strong>IMPORTANT: urllib3 v2.0 will drop support for Python 2</strong>: <a href="https://urllib3.readthedocs.io/en/latest/v2-roadmap.html">Read more in the v2.0 Roadmap</a></p> <ul> <li>Changed behavior of the default <code>SSLContext</code> when connecting to HTTPS proxy during HTTPS requests. The default <code>SSLContext</code> now sets <code>check_hostname=True</code>.</li> </ul> <p><strong>If you or your organization rely on urllib3 consider supporting us via <a href="https://github.com/sponsors/urllib3">GitHub Sponsors</a></strong></p> <h2>1.26.3</h2> <p>:warning: <strong>IMPORTANT: urllib3 v2.0 will drop support for Python 2</strong>: <a href="https://urllib3.readthedocs.io/en/latest/v2-roadmap.html">Read more in the v2.0 Roadmap</a></p> <ul> <li> <p>Fixed bytes and string comparison issue with headers (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2141">#2141</a>)</p> </li> <li> <p>Changed <code>ProxySchemeUnknown</code> error message to be more actionable if the user supplies a proxy URL without a scheme (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2107">#2107</a>)</p> </li> </ul> <p><strong>If you or your organization rely on urllib3 consider supporting us via <a href="https://github.com/sponsors/urllib3">GitHub Sponsors</a></strong></p> <h2>1.26.2</h2> <p>:warning: <strong>IMPORTANT: urllib3 v2.0 will drop support for Python 2</strong>: <a href="https://urllib3.readthedocs.io/en/latest/v2-roadmap.html">Read more in the v2.0 Roadmap</a></p> <ul> <li>Fixed an issue where <code>wrap_socket</code> and <code>CERT_REQUIRED</code> wouldn't be imported properly on Python 2.7.8 and earlier (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2052">#2052</a>)</li> </ul> <h2>1.26.1</h2> <p>:warning: <strong>IMPORTANT: urllib3 v2.0 will drop support for Python 2</strong>: <a href="https://urllib3.readthedocs.io/en/latest/v2-roadmap.html">Read more in the v2.0 Roadmap</a></p> <ul> <li>Fixed an issue where two <code>User-Agent</code> headers would be sent if a <code>User-Agent</code> header key is passed as <code>bytes</code> (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2047">#2047</a>)</li> </ul> <h2>1.26.0</h2> <p>:warning: <strong>IMPORTANT: urllib3 v2.0 will drop support for Python 2</strong>: <a href="https://urllib3.readthedocs.io/en/latest/v2-roadmap.html">Read more in the v2.0 Roadmap</a></p> <ul> <li> <p>Added support for HTTPS proxies contacting HTTPS servers (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/1923">#1923</a>, Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/1806">#1806</a>)</p> </li> <li> <p>Deprecated negotiating TLSv1 and TLSv1.1 by default. Users that still wish to use TLS earlier than 1.2 without a deprecation warning should opt-in explicitly by setting <code>ssl_version=ssl.PROTOCOL_TLSv1_1</code> (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2002">#2002</a>) <strong>Starting in urllib3 v2.0: Connections that receive a <code>DeprecationWarning</code> will fail</strong></p> </li> <li> <p>Deprecated <code>Retry</code> options <code>Retry.DEFAULT_METHOD_WHITELIST</code>, <code>Retry.DEFAULT_REDIRECT_HEADERS_BLACKLIST</code> and <code>Retry(method_whitelist=...)</code> in favor of <code>Retry.DEFAULT_ALLOWED_METHODS</code>, <code>Retry.DEFAULT_REMOVE_HEADERS_ON_REDIRECT</code>, and <code>Retry(allowed_methods=...)</code> (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2000">#2000</a>) <strong>Starting in urllib3 v2.0: Deprecated options will be removed</strong></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/urllib3/urllib3/blob/main/CHANGES.rst">urllib3's changelog</a>.</em></p> <blockquote> <h2>1.26.5 (2021-05-26)</h2> <ul> <li>Fixed deprecation warnings emitted in Python 3.10.</li> <li>Updated vendored <code>six</code> library to 1.16.0.</li> <li>Improved performance of URL parser when splitting the authority component.</li> </ul> <h2>1.26.4 (2021-03-15)</h2> <ul> <li>Changed behavior of the default <code>SSLContext</code> when connecting to HTTPS proxy during HTTPS requests. The default <code>SSLContext</code> now sets <code>check_hostname=True</code>.</li> </ul> <h2>1.26.3 (2021-01-26)</h2> <ul> <li> <p>Fixed bytes and string comparison issue with headers (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2141">#2141</a>)</p> </li> <li> <p>Changed <code>ProxySchemeUnknown</code> error message to be more actionable if the user supplies a proxy URL without a scheme. (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2107">#2107</a>)</p> </li> </ul> <h2>1.26.2 (2020-11-12)</h2> <ul> <li>Fixed an issue where <code>wrap_socket</code> and <code>CERT_REQUIRED</code> wouldn't be imported properly on Python 2.7.8 and earlier (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2052">#2052</a>)</li> </ul> <h2>1.26.1 (2020-11-11)</h2> <ul> <li>Fixed an issue where two <code>User-Agent</code> headers would be sent if a <code>User-Agent</code> header key is passed as <code>bytes</code> (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/2047">#2047</a>)</li> </ul> <h2>1.26.0 (2020-11-10)</h2> <ul> <li> <p><strong>NOTE: urllib3 v2.0 will drop support for Python 2</strong>. <code>Read more in the v2.0 Roadmap <https://urllib3.readthedocs.io/en/latest/v2-roadmap.html></code>_.</p> </li> <li> <p>Added support for HTTPS proxies contacting HTTPS servers (Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/1923">#1923</a>, Pull <a href="https://github-redirect.dependabot.com/urllib3/urllib3/issues/1806">#1806</a>)</p> </li> <li> <p>Deprecated negotiating TLSv1 and TLSv1.1 by default. Users that still wish to use TLS earlier than 1.2 without a deprecation warning</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/urllib3/urllib3/commit/d1616473df94b94f0f5ad19d2a6608cfe93b7cdf"><code>d161647</code></a> Release 1.26.5</li> <li><a href="https://github.com/urllib3/urllib3/commit/2d4a3fee6de2fa45eb82169361918f759269b4ec"><code>2d4a3fe</code></a> Improve performance of sub-authority splitting in URL</li> <li><a href="https://github.com/urllib3/urllib3/commit/2698537d52f8ff1f0bbb1d45cf018b118e91f637"><code>2698537</code></a> Update vendored six to 1.16.0</li> <li><a href="https://github.com/urllib3/urllib3/commit/07bed791e9c391d8bf12950f76537dc3c6f90550"><code>07bed79</code></a> Fix deprecation warnings for Python 3.10 ssl module</li> <li><a href="https://github.com/urllib3/urllib3/commit/d725a9b56bb8baf87c9e6eee0e9edf010034b63b"><code>d725a9b</code></a> Add Python 3.10 to GitHub Actions</li> <li><a href="https://github.com/urllib3/urllib3/commit/339ad34c677c98fd9ad008de1d8bbeb9dbf34381"><code>339ad34</code></a> Use pytest==6.2.4 on Python 3.10+</li> <li><a href="https://github.com/urllib3/urllib3/commit/f271c9c3149e20d7feffb6429b135bbb6c09ddf4"><code>f271c9c</code></a> Apply latest Black formatting</li> <li><a href="https://github.com/urllib3/urllib3/commit/1884878aac87ef0494b282e940c32c24ee917d52"><code>1884878</code></a> [1.26] Properly proxy EOF on the SSLTransport test suite</li> <li><a href="https://github.com/urllib3/urllib3/commit/a8913042b676c510e94fc2b097f6b514ae11a537"><code>a891304</code></a> Release 1.26.4</li> <li><a href="https://github.com/urllib3/urllib3/commit/8d65ea1ecf6e2cdc27d42124e587c1b83a3118b0"><code>8d65ea1</code></a> Merge pull request from GHSA-5phf-pp7p-vc2r</li> <li>Additional commits viewable in <a href="https://github.com/urllib3/urllib3/compare/1.25.8...1.26.5">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

dammit...

"For security and billing reasons, Heroku does not automatically create review apps for pull requests to public repos that are sent from forks."

Maybe we can find a solution. Maybe an action button or so... Will have to think about it.

We could set this up right now btw, without the PR. The only problem is, that it's going to use the default whitelist. So if someone adds a bridge, its not going to be shown on the heroku build because the bridge is not in the whitelist.

We could do some fancy scripting to only whitelist a new bridge, but then it would fail on PRs that dont change something in regards to bridges. So I would just whitelist all and be done.

@VerifiedJoseph you've been quite active, what are your thoughts?

I'm not sure on how to fix the issue that the test has.

@em92 ?

Hi,

I've tested this on my fork and it's working, thats why I wanted to introduce it here as well:

Automated Heroku Builds on Pull Requests!

What is it?

Heroku can deploy builds of the application with the code from a PR automatically and add it to the PR. These builds run for 1-30 days (or until the PR is closed/merged) and will give us the ability to review the PR directly online and test the functionality.

Costs?

Nothing. The Heroku free tier lets you do everything (app, pipeline and "review apps" which is the name for the PR builds). I've tested it with rss-bridge, have not added a creditcard anywhere and everything works. I dont know (and I haven't seen) a limit on the amount of pull requests but at least 3 at the same time are possible :)

What do we need to change to get it?

Not a whole lot.

Heroku: Setting up the Heroku pipeline takes about 30 minutes and will need to be done by an admin of the repo (since heroku directly interacts with the PRs etc). It's pretty much straight forward because we do exactly what the "how-to" tutorial explains. In addition, an environment variable needs to be created for the app review pipeline called "RSS_HEROKU_REVIEW" with value "TRUE". The reason is: rss-bridge: My PR #2100 needs to be merged. This will pull environment variables into the configuration. The whitelister then checks if the "RSS_HEROKU_REVIEW" variable is set and will add all bridges to the whitelist. After the merge, it will just work.

See my test-pr in my repo: https://github.com/Bockiii/rss-bridge/pull/13 There is a link to the deployed heroku app.

Links to read:

• Create Heroku Pipeline: https://devcenter.heroku.com/articles/pipelines
• Create Heroku Review App: https://devcenter.heroku.com/articles/github-integration-review-apps

If I had the MJPEG stream loaded on a page, it seems to freezes up all other requests, including my SocketIO server which is from the flask-socketio library. Even for navigating to another page, since the MJPEG stream is still being streamed on the page, I had to unload it with document.getElementsByTagName('img')[0].src = '' first before it can hyperlink to another page successfully. Is there any way around this?

If I am on a page where the live stream does not need to be loaded, the SocketIO server loads fine.

I'm using eventlet. I think I'll split it into two Flask servers in that case as a workaround. Thanks a lot for the quick assistance!

@NRockhouse Okay, you didn't mention that you were using Socket.IO before. Are you using eventlet or gevent? Try removing them, these are likely incompatible with your camera hardware and will block when you access frames.

I'm only on Flask which is routed through SocketIO's Flask wrapper, I didn't proxy it through nginx or any external servers. I've only just learnt about using Flask's web server so I'm not sure about the intricate details, but while checking the source code of SocketIO, since SocketIO's is already calling Flask with threaded=True, wouldn't that be threaded?

This is my arguments for calling Flask/SocketIO.

if __name__ == "__main__":
    socketio.run(app, host='127.0.0.1', debug=True, use_reloader=False)

Yes, you have to use a server that can handle more than one request at a time. Either with multiple processes or multiple threads. What is your current web server?

If I had the MJPEG stream loaded on a page, it seems to freezes up all other requests, including my SocketIO server which is from the flask-socketio library. Even for navigating to another page, since the MJPEG stream is still being streamed on the page, I had to unload it with document.getElementsByTagName('img')[0].src = '' first before it can hyperlink to another page successfully. Is there any way around this?

If I am on a page where the live stream does not need to be loaded, the SocketIO server loads fine.

Nothing as easy as motion-jpeg. You can implement your own streaming protocol, and then implement a video renderer in your front end. Or maybe you can use a more advanced streaming protocol that supports subtitles or closed captions and then you have a place to enter your strings. Either way, this code will not work and cannot be easily adapted.

any alternatives?

Sorry, the Motion-JPEG format does not allow metadata to be sent along with video frames.

Yes, one solution is to download the images on a proxy, but I don't know if it is a practical solution for public bridges. I think that there is no other solution, except if there is other links for the same images on instagram without the CORS header "same-origin".

def gen(camera):
    while True:
        frame = camera.get_frame()
        
        # here i want a new string to send along with each frame

        yield (b'--frame\r\n'
               b'Content-Type: image/jpeg\r\n\r\n' + frame + b'\r\n')

<html>
  <head>
    <title>Video Streaming Demonstration</title>
  </head>
  <body>
    <h1>Video Streaming Demonstration</h1>
    
    <p><!-- string to be shown here --></p>
  </body>
</html>