home.social

#harss — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #harss, aggregated by home.social.

  1. : codeberg.org/fistons/youtube-t

    I learnt that we can follow channels as feed, so I used Google takeout to export all my YouTube subscriptions and build this tool in to make an so I can import it with my client.

    No need for a Google Account anymore!

    Now I need to implements opml import/export in ...

  2. #imadethis : codeberg.org/fistons/youtube-t

    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 ...

  3. #imadethis : codeberg.org/fistons/youtube-t

    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 ...

  4. 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.

    #rust #rustlang #api #devdiary #harss #rss #todolist

  5. 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.

  6. 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.

    #rust #rustlang #api #devdiary #harss #rss #todolist

  7. 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.

    #rust #rustlang #api #devdiary #harss #rss #todolist

  8. 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.

    #rust #rustlang #api #devdiary #harss #rss #todolist

  9. Should I works on #harss a bit? It's been a while...

    ...Naaaaah let's try to gain 0.02 seconds on my #1brc in #rust

  10. Should I works on a bit? It's been a while...

    ...Naaaaah let's try to gain 0.02 seconds on my in

  11. Should I works on #harss a bit? It's been a while...

    ...Naaaaah let's try to gain 0.02 seconds on my #1brc in #rust

  12. Should I works on #harss a bit? It's been a while...

    ...Naaaaah let's try to gain 0.02 seconds on my #1brc in #rust

  13. Should I works on #harss a bit? It's been a while...

    ...Naaaaah let's try to gain 0.02 seconds on my #1brc in #rust

  14. And it works! I think I will be able to move on quite easly!

    Many thanks to @teotwaki and @jornfranke

  15. And it works! I think I will be able to move #harss on #codeberg quite easly!

    Many thanks to @teotwaki and @jornfranke

  16. My first blog post on development, my aggregator in !

    pedr0.net/harss-users-manageme

    I hope my english is understandable, and that the post is somehow interesting.

    Please let me know!

  17. My first blog post on #HaRSS development, my #RSS aggregator #API in #rustlang !

    pedr0.net/harss-users-manageme

    I hope my english is understandable, and that the post is somehow interesting.

    Please let me know!

  18. Of course I didn't post anything interesting yet. But I plan to post about #harss, #rustlang and probably others stuff on the most irregular basis

  19. Of course I didn't post anything interesting yet. But I plan to post about , and probably others stuff on the most irregular basis

  20. Of course I didn't post anything interesting yet. But I plan to post about #harss, #rustlang and probably others stuff on the most irregular basis

  21. Of course I didn't post anything interesting yet. But I plan to post about #harss, #rustlang and probably others stuff on the most irregular basis

  22. Of course I didn't post anything interesting yet. But I plan to post about #harss, #rustlang and probably others stuff on the most irregular basis

  23. I took a few days off and can works a bit on Harss.

    I moved the dev instance from my raspi to my stardust on scaleway, fixed a few bugs and discovered a lot more

    #rust #rustlang #api #devdiary #harss #rss

  24. I took a few days off and can works a bit on Harss.

    I moved the dev instance from my raspi to my stardust on scaleway, fixed a few bugs and discovered a lot more

  25. I took a few days off and can works a bit on Harss.

    I moved the dev instance from my raspi to my stardust on scaleway, fixed a few bugs and discovered a lot more

    #rust #rustlang #api #devdiary #harss #rss

  26. I took a few days off and can works a bit on Harss.

    I moved the dev instance from my raspi to my stardust on scaleway, fixed a few bugs and discovered a lot more

    #rust #rustlang #api #devdiary #harss #rss

  27. I took a few days off and can works a bit on Harss.

    I moved the dev instance from my raspi to my stardust on scaleway, fixed a few bugs and discovered a lot more

    #rust #rustlang #api #devdiary #harss #rss

  28. 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.

    #rust #rustlang #api #devdiary #harss #rss

  29. 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. ? ? Something else? Oh, and I suck at UI/UX.

  30. 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.

    #rust #rustlang #api #devdiary #harss #rss

  31. 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.

    #rust #rustlang #api #devdiary #harss #rss

  32. 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.

    #rust #rustlang #api #devdiary #harss #rss

  33. It's been a while since I worked on it, but I tried to work on my #RSS Api.

    I'm trying #helix as a code editor now (thanks @mo8it for the tips!), so I'm a bit slower than usual, not that I was particularly fast at first.

    #rust #rustlang #api #devdiary #harss

  34. It's been a while since I worked on it, but I tried to work on my Api.

    I'm trying as a code editor now (thanks @mo8it for the tips!), so I'm a bit slower than usual, not that I was particularly fast at first.

  35. It's been a while since I worked on it, but I tried to work on my #RSS Api.

    I'm trying #helix as a code editor now (thanks @mo8it for the tips!), so I'm a bit slower than usual, not that I was particularly fast at first.

    #rust #rustlang #api #devdiary #harss

  36. It's been a while since I worked on it, but I tried to work on my #RSS Api.

    I'm trying #helix as a code editor now (thanks @mo8it for the tips!), so I'm a bit slower than usual, not that I was particularly fast at first.

    #rust #rustlang #api #devdiary #harss

  37. It's been a while since I worked on it, but I tried to work on my #RSS Api.

    I'm trying #helix as a code editor now (thanks @mo8it for the tips!), so I'm a bit slower than usual, not that I was particularly fast at first.

    #rust #rustlang #api #devdiary #harss

  38. 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!

    #rss #rust #rustlang #api #devdiary #harss

  39. 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!

  40. 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!

    #rss #rust #rustlang #api #devdiary #harss

  41. 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!

    #rss #rust #rustlang #api #devdiary #harss

  42. 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!

    #rss #rust #rustlang #api #devdiary #harss

  43. 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!

    #rss #rust #rustlang #api #devdiary #harss

  44. 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!

  45. 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!

    #rss #rust #rustlang #api #devdiary #harss

  46. 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!

    #rss #rust #rustlang #api #devdiary #harss

  47. 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!

    #rss #rust #rustlang #api #devdiary #harss

  48. 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.

    #rss #rust #rustlang #api #devdiary #harss

  49. As predicted, I added a new item on my 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 of course) on an article he reads. A feature I found on and even I never used it myself, it may prove useful and it's pretty cheap to implement.

  50. 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.

    #rss #rust #rustlang #api #devdiary #harss