can those be used in very high flow channel conditioner / ventilation or is usual wheel blowers more efficient?
or external unit of split ac system to pack more radiator surface in less space(i understand the higher power comsumpion of it)?
thank you very much for it being free and open source.
can container repacking be avoided? currently hls ts container is being extracted which takes time.
seeking "unsupported videos" is much slower than supported
that's a "non issue" - commercial companies are vendor-locked with cloud on conscious decision so it doesnt matter - they pay for everything (an sometimes multiple times),
and any orgs that treasure open source philosophy either forking or not touching anything of redhat with a long pole.
so what? as long as there's no legaslation that "give data or leave" is explicitly prohibited it would happen with any social network service. everyone does that.
adguard is not epic games, nothing gonna happen.
and even more than that - cdns/antiddos gather more data that usually not directly available to social networks because clicks doesnt originate from tracked pages.
you can soundproof your sleeping room, just need to dampen frequencies that offer direction cues, they are above 1khz. electronics, car sound whooshing, rattling all produce those frequencies. if it's hard to dampen enough - dampen as much as you find economically viable and raise noise floor by running ventilation or big diameter fan, it will mask the rest of them.
also having fresh air ventilation (with soundproofed intake - they use quiet fan) is much more comfortable than having windows opened on busy street.
this is not so useful because your polls wont be search-indexed by search engines so people wont find them by searching app+keyword.
so usecase like uservotes to add/change feature will have duplicates.
plain polls in itself had their issues - people answering polls arent people using your app, unless poll is nagged in the app/app settings(so a/b running in parallel to poll can help evaluating user feedback - remember google chrome bookmark page fiasco),
if someone resorts to searching apps site they usually either evaluating if app has something that they need to accomplish with app; or if there's a workaround or a way to do something they dont understand how to accomplish with your app - so if they didnt find a way they will try another app or do it other way.
there's much simpler live chat/search forum(Discourse)/discord all in one approach:
allow users to create topics(akin to discord rooms) relating some aspect of your app.
create flat not nested, not collapsible live chat in each topic.
allow user either post new message in topic or reply with a button to existing message - creating a thread this way.
allow people to subscribe to threads, maybe in side panel.
auto color user messages and threads background - the way google wave did it
allow to +- rate messages in threads if user posted a message inside; if message rating is below threshold visually change it's backround - like paint half of message backround into different color, but dont hide it.
allow marking messages as offtopic - color them differently too.
for single messages without thread allow rating it only to people that answered at least a few times and doesnt have much of their replies as completely off topic.
this way you wont need much moderation besides removing obvious hate speech or creating topics not related to your app.
allow indexing every topic - either page them by day (hour if very chatty), then group day-pages into week pages, allow fulltext+exclude search.
no need for fancy discord/slack like webapp chats, their sole purpose is to limit outside access. your goal Is outside access - to make every aspect of your app(or its abilities/features) as discoverable and explained as possible, and to allow discussing user wants and approaches.
the main key is to make it as findable, searchable, readable(people often dont wat to fight search and just skim read) and approachable(by not having echo chamber hate community) as possible.