thirdplace_

i think more bugs reside here.

if tarball or path is user input then they could be used to inject tar command options.

like it. rss is so simple and cool. problems:

* how to make it easier for users to start using feed readers

* how to make it easier to subscribe to feeds

* how to help users discover new content

I am an insecure renter and this scares me. What should I do??

> It’s very clear that large companies do abuse their market power (price-fixing and collusion)

Can we get some examples of this? (not implying otherwise)

php's composer[0] in 2012 had package namespaces

[0] https://getcomposer.org/

wayback machine for current url:

javascript:window.location='https://web.archive.org/web/*/'+document.location

seems kinda biased. not a single bad word of Allende's Chile.

reminds me of the similar sentiment that a failure may be required in order to get all parties to accept that a change/improvement is needed.

rss-bridge also has xpath-style bridge: https://rss-bridge.org/bridge01/#bridge-XPathBridge

Related to this topic, I made a website/api that finds feeds for you:

https://discovery.thirdplace.no/?q=vimeo.com/user4464579

It's pretty rudimentary but alleviates some manual work.

An alternative is to use rss-bridge: https://rss-bridge.org/bridge01/?action=display&bridge=Teleg...

For sites that don't offer feeds you may want to check out rss-bridge: https://github.com/RSS-Bridge/rss-bridge/

I built a small tool that helps to discover feed urls. It uses various hardcoded and dynamic rules: https://discovery.thirdplace.no/?q=https://www.tek.no

It's FOSS and has an http json api.

My small contribution here is a web tool [0] which helps to discover feeds.

See also https://github.com/RSS-Bridge/ and https://www.jsonfeed.org/

[0] https://discovery.thirdplace.no/?url=&q=https://tfos.co/

[1] https://discovery.thirdplace.no/api?q=https://tfos.co/

They probably justify it morally by thinking they deserve more because they bring in the big sales and "do all the hard work". You could offer up some stock ownership for free to heal the relationship. Some people couldn't live like this and would rather burn it to the ground. So, depends on your position, goals and preferences etc.

Here's how to live: Pursue pain

Earlier in the poem he says that the two roads were equally worn. But looking back on it he remembers the chosen one as less worn. Unclear what is the meaning. Self-delusion maybe because our memories change?

I also attempted to build a feed reader a while back. In the process I built a feed discovery service:

https://discovery.thirdplace.no/?q=jackevansevo.github.io

It's not perfect but it's better than a simple parsing of <link> tags in the html.

Congrats on the success. If I were to use this product I would be concerned about broken urls when the operation is shut down.

You are mostly right. There is some additional value provided:

With known feed urls e.g. https://www.meetup.com/%s/events/rss/ we can save the network call to meetup.com and produce the feed url immediately. This is also an argument for making a browser addon or at least some client code that can produce it.

Discovered feed urls are cached which saves the direct network call to a possibly slow site.

The service produces third-party feeds for websites that don't have it e.g. https://twitter.com/elonmusk => https://nitter.net/elonmusk/rss

59% would sacrifice their own life for five people? Someone been messing with the votes.

I wrote a tool that finds rss feeds for you:

https://discovery.thirdplace.no/?q=https://www.youtube.com/w...

It was a personal pain point for me.

Do you mean it's kind of like a red flag when they don't use git?

In a previous life I worked at a successful 30-person company. We used SVN and just didn't think the migration to git was worth it.

Interesting that twitch still uses IRC as their messaging infrastructure. Wonder how they were able to scale it up.

I don't see big problem here. At some point in the future we probably can't increase our consumption any further. Maybe even have to reduce it. It's gonna be painful but not catastropic.

I don't see this is a trap. More like an inevitability.

Early php used to store the session id in urls: https://example.com/?PHPSESSID=23d2332d2 All links in the page contained the same id.

I believe it must have been before browser cookies was widely supported?

That blog post is packed with useful info.

See also https://discovery.thirdplace.no/?q=kevincox.ca for feed discovery. Disclaimer: I built it.

The subjective value placed on the cost of complexity.