fistons :rust: :java: :godot:
-
Just read that http://ozark.hendrix.edu/~yorgey/forest/00FD/index.xml and, yeah, I can relate, as a father, not as a teacher.
It hurts more than it should.
-
I made a new release of #youtube-to-opml
Now it can access your YouTube subscriptions through the YouTube API (using Google OAuth), among other things.
Oh, and it's my first stuff published on #crateio !
Please check it: https://crates.io/crates/youtube-to-opml
If you found a bug or have any idea for improvements, please open an issue: https://codeberg.org/fistons/youtube-to-opml/issues or leave me message here
-
#imadethis : https://codeberg.org/fistons/youtube-to-opml
I learnt that we can follow #Youtube channels as #RSS feed, so I used Google takeout to export all my YouTube subscriptions and build this tool in #rustlang to make an #OPML so I can import it with my #RSS client.
No need for a Google Account anymore!
Now I need to implements opml import/export in #harss ...
-
It has been way to long since I posted about this.
I regain some motivation lately, maybe a will be able to do a "real' release of the first usable version of the API (There is no v1. Never.).
And then... the frontend.
-
And it works! I think I will be able to move #harss on #codeberg quite easly!
Many thanks to @teotwaki and @jornfranke
-
Urgent poll that will probably make a flop:
Doom's Cacodemon vs Pokemon's Pikachu, who wins?
-
My first blog post on #HaRSS development, my #RSS aggregator #API in #rustlang !
https://pedr0.net/harss-users-management/
I hope my english is understandable, and that the post is somehow interesting.
Please let me know!
-
Slow progress, but still progress. I'm a bit tired at the moment and prefer to keep my free time resting and doing stuff with my family.
But It's taking shape! Maybe a first usable version of the API will be released soonish ™️ ?
After that, I will need to focus a bit on the front-end. And ow boy, it scares me. #egui? #leptos? Something else? Oh, and I suck at UI/UX.
-
A bit a progress today, I was able to use tokio-cron-scheduler crate in the API to schedule the fetch process.
I removed the old fetcher crate, and basically plan to merge everything in one fat crate instead of having a workspace. I hope it will speed up the compile process a bit. Will I regret this decision later in the far future? Probably. I will let future me handle this and hate present me.
It needs some testing but then it should be good!
-
Some progress were made!
I will now merge the fetching process in the API.
For now I have a separate crate doing this, and it's cron scheduled. For a project this small, I think I can just create a scheduled task in the API.
I have implemented a kind of mutex to prevent fetching the same feed several times at the same time, so having several instance of the API won't be an issue.
Thanks @catsalad for the done item idea!
-
As predicted, I added a new item on my #todo list before finished one, BUT I have almost finished the current one so that's fine
With this, a user will be able to add notes (in #markdown of course) on an article he reads. A feature I found on #inoreader and even I never used it myself, it may prove useful and it's pretty cheap to implement.
-
I remembered that I have a blog, so I wrote a little something about building a #multiarch #docker images for #rust #rustlang stuff, with #githubactions, in a reasonable time.
Here it is: https://blog.pedr0.net/multi-arch-docker-image-rust-and-github-actions-a-love-story/
-
I just fell in love with #sqlx testing features. Using it with the #speculoos crate for test assertions is a pleasure.