currently the data follows /path/to/content/UUID/ as naming format for blog posts.
Would /path/to/content/video-title--UUID/ be better?
Same as #10
currently the data follows `/path/to/content/UUID/` as naming format for blog posts.
Would `/path/to/content/video-title--UUID/` be better?
Hi,
Thank you!
This patch doesn't take in to account the check to see whether a file needs to be deleted which is based on the filename:
See https://git.autonomic.zone/ruangrupa/lumbunglib/src/commit/77b8c9e0af2c2fd8f28b9c496450b9e776fdb0f8/lumbunglib/video.py#L119
and https://git.autonomic.zone/ruangrupa/lumbunglib/src/commit/77b8c9e0af2c2fd8f28b9c496450b9e776fdb0f8/lumbunglib/video.py#L125
It checks for the existence of UUID but you write a file which is Name+UUID: https://git.autonomic.zone/ruangrupa/lumbunglib/src/commit/77b8c9e0af2c2fd8f28b9c496450b9e776fdb0f8/lumbunglib/video.py#L122
Possibly the same in https://git.autonomic.zone/ruangrupa/lumbunglib/issues/10
This patch doesn't take in to account the check to see whether a file needs to be deleted which is based on the filename
you're right, thanks for pointing this out!
> This patch doesn't take in to account the check to see whether a file needs to be deleted which is based on the filename
you're right, thanks for pointing this out!
Probably because of the whitespaces in the title. Rather than using self-rolled sanitization logic: in the other scripts I've relied on slugify to make the post names. It strips much more, but is also multilingual etc and is already a dependency for this repo.
Thanks! More things coming up out of this. Maybe you already saw in nongkrong but the links are broken.
https://lumbung.space/tv/lumbung%20konteks-%20Listening%20to%20The%20Land-%20-4df9e52b-bcbc-41a7-a986-2463464db6e5/d96aeed2-4ea3-409e-b60e-69af5c1f402f.jpg
Probably because of the whitespaces in the title. Rather than using self-rolled sanitization logic: in the other scripts I've relied on [slugify](https://https://git.autonomic.zone/ruangrupa/lumbunglib/src/branch/master/lumbunglib/feed.py#L241) to make the post names. It strips much more, but is also multilingual etc and is already a dependency for this repo.
edit: perhaps related? https://git.autonomic.zone/ruangrupa/lumbung.space/issues/31
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Same as #10
currently the data follows
/path/to/content/UUID/as naming format for blog posts.Would
/path/to/content/video-title--UUID/be better?closed in
77b8c9e0afHi,
Thank you!
This patch doesn't take in to account the check to see whether a file needs to be deleted which is based on the filename:
See
77b8c9e0af/lumbunglib/video.py (L119)and
77b8c9e0af/lumbunglib/video.py (L125)It checks for the existence of UUID but you write a file which is Name+UUID:
77b8c9e0af/lumbunglib/video.py (L122)Possibly the same in ruangrupa/lumbunglib#10
you're right, thanks for pointing this out!
fixed in
58024c775aThanks! More things coming up out of this. Maybe you already saw in nongkrong but the links are broken.
https://lumbung.space/tv/lumbung%20konteks-%20Listening%20to%20The%20Land-%20-4df9e52b-bcbc-41a7-a986-2463464db6e5/d96aeed2-4ea3-409e-b60e-69af5c1f402f.jpg
Probably because of the whitespaces in the title. Rather than using self-rolled sanitization logic: in the other scripts I've relied on slugify to make the post names. It strips much more, but is also multilingual etc and is already a dependency for this repo.
edit: perhaps related? ruangrupa/lumbung.space#31
fixed (we hope 🙏)
34d84dcde2