search

vampiricwulf / tanoshiine

Real-time imageboard in node v14.5.0 and redis
MIT License
5 stars 1 forks source link

Working backwards from meguca #85

Closed vampiricwulf closed 4 years ago

vampiricwulf commented 9 years ago

AKA: I'm better at taking steps backwards than forward :^)

bakape commented 9 years ago

Spectrograms for non-artwork audio files

Blue is reportedly working on no-artwork MP3 and deduplication. But knowing him, that could take a while. You should drop in /g/, that's where most of the dev talk happens. Also, if any questions arise.

vampiricwulf commented 9 years ago

Ohho? I was also thinking about Identicons. What do you think about that?

bakape commented 9 years ago

Needs to be benchmarked. I don't want to add too much overhead. And a static thumbnail is always an option.

vampiricwulf commented 9 years ago

I see, I was keeping duplicates in mind, since I currently have no idea how you even handle them with album artwork. /tano/s would post albums at a time, so the spectrogram was to keep the duplication in check.

bakape commented 9 years ago

Duplicates are a non-issue. I'll let Blue handle it. I'm more concerned on what to put on MP3s with no covers.

vampiricwulf commented 4 years ago

Discontinued

bakape commented 4 years ago

killing off a piece off history

vampiricwulf commented 4 years ago

It had to be done, the historical landmarks must be killed. The code was made during a time of oppression and thus was upsetting my feelings!

Nah but for real if I was to go work backwards from meguca again, using such ancient code would just be a bad idea since any bugs you found woulda been patched by now and there'd be so many newer features. Since tano is still somehow running with its spaghetti code and Reiner performed major updates to get us on newer Nodejs versions, my interest is just be going back to pushing tano forward with features rather than pulling backwards features from meguca.