Telegram is a proprietary messenger that gained some popularity recently. It has FOSS client, API and binding for the API. It has private chats, group chats and "channels". Channels are content feeds.
RSS allows users to access updates to online content in a standardized, computer-readable format.
Telegram requires an account to read channels. Creating an account requires you to give Telegram your phone number. Unfortunately, some good content is being posted to Telegram channels. But it is unacceptable for some people to give phone number to Telegram, which is ran by some Russian billionaires, who might turn out to be evil. Also, RSS/Atom is standardized and has a lot of great readers.
The idea is to create a FOSS gate that would allow to convert Telegram channels to RSS/Atom. The gate will be hosted somewhere.
UI: A user posts channel name into input, presses "submit" and URL with RSS/Atom feed is being created. Posts from channels should be fetched in the background, for example, with cron jobs
No Hackers yet
This project is part of:
Hack Week 17
Activity
Comments
Be the first to comment!
Similar Projects
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/
Recipes catalog and calculator in Rails 8 by gfilippetti
My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.
TO DO
- Index page
- Product page
- Admin area -- Supplies calculator based on orders -- Orders notification
- Authentication
- Payment
- Deployment
Day 1
As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.
Day 2
Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.
Hackweek 24
For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.
Day 1