by cumlord » Sun Jul 21, 2024 7:16 pm
these are good ideas, i have a half-baked version. maybe more of a quarter-baked version. a more fleshed out site with federation would be great for this sort of thing. i'd never thought about going down the federation route for this
here's some pics in it's current state which aside from the pope icons has been untouched for months:
http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkb ... /pope.jpeg
http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkb ... 8/new.jpeg
http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkb ... isode.jpeg
http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkb ... eason.jpeg
http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkb ... /INFO.jpeg
i originally made it to be a separate way to get hashes out in a fully automated way, but it's become an organization thing for myself. I use it to see what needs repacking and it controls the scripts for finding new episodes and making season packs, blah blah.
but to what you were saying, when my compiler scripts are finished doing their thing they shoot out a .csv. compressed the csv isn't very big, and is picked up by this script, which parses out the info from the csv and adds new content.
since the webapp is a separate thing, i think what could be done for federation is the webapp could follow some addresses where updated zipped .csv's could be found, and then unzip and combine the data from multiple "feeds" when parsing. As of now since it's hastily hacked together, it always exports and reads the whole feed. Maybe then have two separate feeds per content, one with everything and one with only new things. There's probably better ways to do this though so let me know, i chose .csv because it was easy, not because it's efficient or any other reason really.
I have a separate torrent CLI toolpack i'll release soon, and i think in the future something like this could be bundled with it. the toolpack could control the webapp and releases made with the toolpack sent to your own "feed," and anyone running the toolpack could then run their own instance.
just ideas though, the toolpack is a thing and nearly ready, but the webapp would need a lot of work, especially hardening it. unless there's something else farther along that could be adapted to this maybe?
these are good ideas, i have a half-baked version. maybe more of a quarter-baked version. a more fleshed out site with federation would be great for this sort of thing. i'd never thought about going down the federation route for this
here's some pics in it's current state which aside from the pope icons has been untouched for months:
[url]http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkbnpjjsn6ddevqbchz3rta.b32.i2p/file/b0/b0608cc217b2c44946fbb1e97c53147eccb1efcb1b7b9af4367da42f03976dd1/pope.jpeg[/url]
[url]http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkbnpjjsn6ddevqbchz3rta.b32.i2p/file/df/df7f0d55fb09557ebf05597dffb4ec36ac72ecdcf2e7b2d6e6c00f7c61315828/new.jpeg[/url]
[url]http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkbnpjjsn6ddevqbchz3rta.b32.i2p/file/25/255d9187183a65f716cfffd885fa0efc485e293f24347607f7f025d3f80c9ec2/episode.jpeg[/url]
[url]http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkbnpjjsn6ddevqbchz3rta.b32.i2p/file/51/51dfea4ce3ec0b3816080f026dc47ea653310ad7c76a4dc5f505bd52d7fdee00/season.jpeg[/url]
[url]http://o7jgnp7bubzdn7mxfqmghn3lzsjtpgkbnpjjsn6ddevqbchz3rta.b32.i2p/file/fe/fec3d5bd1030e3cc02ebd088c3ce2d6a33504760da3ea2f73d4851ea8b353553/INFO.jpeg[/url]
i originally made it to be a separate way to get hashes out in a fully automated way, but it's become an organization thing for myself. I use it to see what needs repacking and it controls the scripts for finding new episodes and making season packs, blah blah.
but to what you were saying, when my compiler scripts are finished doing their thing they shoot out a .csv. compressed the csv isn't very big, and is picked up by this script, which parses out the info from the csv and adds new content.
since the webapp is a separate thing, i think what could be done for federation is the webapp could follow some addresses where updated zipped .csv's could be found, and then unzip and combine the data from multiple "feeds" when parsing. As of now since it's hastily hacked together, it always exports and reads the whole feed. Maybe then have two separate feeds per content, one with everything and one with only new things. There's probably better ways to do this though so let me know, i chose .csv because it was easy, not because it's efficient or any other reason really.
I have a separate torrent CLI toolpack i'll release soon, and i think in the future something like this could be bundled with it. the toolpack could control the webapp and releases made with the toolpack sent to your own "feed," and anyone running the toolpack could then run their own instance.
just ideas though, the toolpack is a thing and nearly ready, but the webapp would need a lot of work, especially hardening it. unless there's something else farther along that could be adapted to this maybe?