Django-link-archive VS graphql-api

I am running my of YouTube front-end.

Link: https://github.com/rumca-js/Django-link-archive

Demo: https://renegat0x0.ddns.net/apps/catalog

Allows me to add channels, download individual videos, bookmark videos, etc. Uses iframe to display the video.

I have no problems with viewing videos:

- I use ff with adblock

- videos are embedded using no-referrer-when-downgrade policy

I have literally no ads.

There are some drawbacks:

- YouTube may change their policies, change embedding strategies

- To have control over videos, you still have to manually download them

I wrote bookmark manager in Django.

https://github.com/rumca-js/Django-link-archive

You can self host it.

You can add RSS sources and auto import new links regularly.

It may not be stare of the art, but gets the job done.

Demo below, but may not be working when you look at it. It runs on raspberry pi.

https://renegat0x0.ddns.net/apps/catalog/entry/11503/

I have myself dabbled a little bit in that subject. Some of my notes:

- some RSS feeds are protected by cloudflare. It is true however that it is not necessary for majority of blogs. If you would like to do more then selenium would be a way to solve "cloudflare" protected links

- sometimes even selenium headless is not enough and full blown browser in selenium is necessary to fool it's protection

- sometimes even that is not enough

- then I started to wonder, why some RSS feeds are so well protected by cloudflare, but who am I to judge?

- sometimes it is beneficial to cover user agent. I feel bad for setting my user agent to chrome, but again, why RSS feeds are so well protected?

- you cannot parse, read entire Internet, therefore you always need to think about compromises. For example I have narrowed area of my searches in one of my projects to domains only. Now I can find most of the common domains, and I sort them by their "importance"

- RSS links do change. There need to be automated means to disable some feeds automatically to prevent checking inactive domains

- I do not see any configurable timeout for reading a page, but I am not familiar with aiohttp. Some pages might waste your time

- I hate that some RSS feeds are not configured properly. Some sites do not provide a valid meta "link" with "application/rss+xml". Some RSS feeds have naive titles like "Home", or no title at all. Such a waste of opportunity

My RSS feed parser, link archiver, web crawler: https://github.com/rumca-js/Django-link-archive. Especially interesting could be file rsshistory/webtools.py. It is not advanced programming craft, but it got the job done.

Additionally, in other project I have collected around 2378 of personal sites. I collect domains in https://github.com/rumca-js/Internet-Places-Database/tree/ma... . These files are JSONs. All personal sites have tag "personal".

Most of the things are collected from:

https://nownownow.com/

https://searchmysite.net/

I wanted also to process domains from https://downloads.marginalia.nu/, but haven't got time to read structure of the files

"""

Disclaimer: I have a automated RSS reader enabled in my network: https://github.com/rumca-js/Django-link-archive

On the other hand it is not 1995. Time has moved on. I wrote a Simple RSS feed, that also serves as search engine for bookmarks.

I am able to run it in attick on raspberry pi. We do not have to rely so heavily on google.

https://github.com/rumca-js/Django-link-archive

It is true that it does not serve me as google, or kagi replacement. It is a very nice addition though.

With a little bit off determination I do not have to be so dependent on google.

Here is also a dump of known domains. Some are personal.

https://github.com/rumca-js/Internet-Places-Database

...and my bookmarks

https://github.com/rumca-js/RSS-Link-Database

Some more years, and google can go to hell.

[4] https://github.com/rumca-js/Django-link-archive

These are exported then to github repositories:

[5] https://github.com/rumca-js/RSS-Link-Database - bookmarks

[6] https://github.com/rumca-js/RSS-Link-Database-2023 - 2023 year news headlines

[7] https://github.com/rumca-js/Internet-Places-Database - all known to me domains, and RSS feeds

My own repositories:

- bookmarked entries https://github.com/rumca-js/RSS-Link-Database

- mostly domains https://github.com/rumca-js/Internet-Places-Database

- all 'news' from 2023 https://github.com/rumca-js/RSS-Link-Database-2023

I am using my own Django program to capture and manage links https://github.com/rumca-js/Django-link-archive.

A list od blogs mentioned by hacker news, some were adres manually by me:

https://github.com/rumca-js/Django-link-archive/blob/main/an...

I have a project. I have posted it once herenon HN. I have not received any feedback then, it hasn't received much traction.

It is a link aggregation. Can be used as a RSS client, or YouTube front end for subscriptions.

It is intended for light, personal use, therefore it is not much scalable, but supports user management.

https://github.com/rumca-js/Django-link-archive

Ha, I have also wrote something similar

https://github.com/rumca-js/Django-link-archive

I support not only youtube, but also any RSS source.

It functions as link aggregation software. I can also fetch meta for all videos in channel, and download videos, audios.

I am using standard Django auth module.

It still lacks polish, and it is under development. I am not a webdev, so I am still struggling with overall architecture

I created an open source library that turns structured text data (YAML) in a Git repository on the fly into a GraphQL API with CRUD queries / mutations.

All that is needed in the repository is a plain text GraphQL schema file that defines what the data structures look like. The Git repository itself can be located on GitHub, GitLab, or in the local filesystem.

https://github.com/commitspark/graphql-api

I'm working on https://commitspark.com , a headless CMS where all data is stored in a GitHub repository with branching/merging workflow support for content.

Reading/writing content from/to GitHub happens through an Open Source API library I released. For the content data schema, I simply require a plaintext GraphQL type file inside the repository. The schema then automatically determines the API structure as well as the editor-friendly UI that I can generate on the Commitspark website when you log in via GitHub.

Even though Commitspark is already publicly available, it is still 100% a side-project that doesn't earn me any money (yet).

Hi HN,

I built Commitspark, a Git-based headless CMS that runs on top of GitHub.

The primary purpose is to enable non-technical content editors to take advantage of Git workflows based on branches, pull requests and merges, without them having to learn Git.

Behind the scenes, everything content-related is driven by GraphQL and an open source library I released ( https://github.com/commitspark/graphql-api ), and for all the workflow features like PRs, commenting and diffs, I built a CMS-centric view onto GitHub using the GitHub API.

For content editors, this should feel the same as working in any other headless CMS, except now with support for much more powerful workflows. For developers, this means all the strengths of Git and GitHub can now also be applied to content (pipelines, tags, commit hashes for caching, branches for migrations, etc.).

There are many other things I am also excited about here that I'm happy to discuss, so please leave your questions below.

Have you considered that content might come from Git? If so, how would content branches fit into this?

(Disclosure: I'm building a library that turns a Git repository into a branch-enabled GraphQL content management API. See https://github.com/contentlab-sh/contentlab )