Request for comment: On utilities extensions

[GarboMuffin]

I am considering a requirement that new extensions (ones that are not already merged) must have a single unified theme that all the blocks adhere to. This would affect most broad utilities extensions.

Motivations:

• Discoverability is zero if the extension does not actually describe what it does.
• Utilities extensions are frequently bloated with blocks that are completely unrelated to what most people will actually use.
• In an attempt to reduce that bloat, utilities extensions tend to be very shallow and can only afford a small handful of blocks per category.
• It results in duplication of functionality across several extensions, sometimes in subtly different or broken ways.
• It allows bugs to remain hidden for longer, especially in duplicated functionality.
• Making unique images for extensions is more difficult when the extension doesn't have a unified idea.
• The time available to review new extensions and maintain the existing ones is finite. I would like that time to be spent on extensions that do something new.
• They take longer to review as unrelated logic all needs to be reviewed at the same time instead of in chunks. Much more likely to get one problem that blocks the entire extension for a long while.

[yuri-kiss]

so they need a base of what they actually do to make it easier, so split them into different extensions?

[yuri-kiss]

i understand the issue, as it can be hard to make an image based on an extension that has really no base.

[yuri-kiss]

should I close my PR?

[GarboMuffin]

Other mitigating factors that make this not a large problem:

• Our extension library has grown massively. There are fewer gaps to fill than ever.
• You can just load extensions from files now. They get stored in the project.

so they need a base of what they actually do to make it easier, so split them into different extensions?

Yes, the proposal is that those should be split into separate extensions. If another extension in the same category exists, consider adding to that one instead of making a new one.

i understand the issue, as it can be hard to make an image based on an extension that has really no base.

Yes, see the RixxyX image for an image that don't really represent the functionality because it's just too broad

should I close my PR?

It's only been 30 minutes so this discussion is not closed. However I would encourage you to pick specific parts of 0tils to focus on and make extensions that go deep in each specific area.

[yuri-kiss]

should I just add my extra hashes, and the AES function into encoding?

[GarboMuffin]

Encoding has always been a strange collection of blocks, but you could start there

[yuri-kiss]

ok.

[XeroName]

I have a question about Deltatime extension ( PR #622 ).

I know the FPS block is already exists at some of different extensions,
but the "FPS" block on that extension works not samely from others.
This works based on adjustable noise filter value, so user anyone use this extension can determine about updating time of FPS.

Although, could these elements are treated as same blocks?

[LilyMakesThings]

I was hoping something like this would be brought up. This not only encourages originality, but it encourages contribution. 100% support.

[yuri-kiss]

i already fixed mine.

[CST1229]

IMO utilities extensions should be accepted, but not be listed on the homepage.

[LilyMakesThings]

IMO utilities extensions should be accepted, but not be listed on the homepage.

People making a utilities extension to add 1 useful block and 20 dupe blocks not only encourages bloat, but discourages contribution.

[LilyMakesThings]

IMO utilities extensions should be accepted, but not be listed on the homepage.

People making a utilities extension to add 1 useful block and 20 dupe blocks not only encourages bloat, but discourages contribution.

I think making an extension for yourself so you have all the blocks you want in one place is perfectly fine. For the most part, unlisted extensions are only on the website for ease of access of the creator, it's our job to make sure they're safe but not really to judge what's in them.

It's Garbo's job, not ours. I get your point though, just refuse to list the extensions I guess

[GarboMuffin]

Unlisted extensions still need to be reviewed for safety and maintained indefinitely, the same as any other extension, except now that work only benefits a very small handful of people

[qxsck]

我正在考虑一项要求，即新扩展（尚未合并的扩展）必须具有所有块都遵循的单一统一主题。这将影响大多数广泛的公用事业扩展。

动机：

• 如果扩展实际上没有描述它的作用，则可发现性为零。
• 实用程序扩展经常充斥着与大多数人实际使用的内容完全无关的块。
• 为了减少这种膨胀，实用程序扩展往往非常浅，每个类别只能承受少量块。
• 它会导致跨多个扩展的功能重复，有时以微妙不同或中断的方式。
• 它允许错误隐藏更长时间，尤其是在重复的功能中。
• 当扩展没有统一的想法时，为扩展制作独特的图像会更加困难。
• 可用于查看新扩展和维护现有扩展的时间是有限的。我希望把时间花在做新事情的扩展上。
• 它们需要更长的时间来审查，因为不相关的逻辑都需要同时审查，而不是分块审查。更有可能遇到一个长时间阻止整个扩展的问题。

That is to say, all blocks of the same expansion should follow the type of expansion?

[Faris90]

IMO utilities extensions should be accepted, but not be listed on the homepage.

People making a utilities extension to add 1 useful block and 20 dupe blocks not only encourages bloat, but discourages contribution.

I never understood the existence of RixxyX

[LilyMakesThings]

IMO utilities extensions should be accepted, but not be listed on the homepage.

People making a utilities extension to add 1 useful block and 20 dupe blocks not only encourages bloat, but discourages contribution.

I never understood the existence of RixxyX

RixxyX existed before TurboWarp ever supported extensions. One of the first, which might've been why it was included on here, for familiarity.

I understand why it exists but I don't understand why it is on the gallery

[Faris90]

I think it has some outdated blocks

[Faris90]

that should be hidden from palette

[DNin01]

Chrome Web Store also requires that each browser extension has a "single purpose".

[DNin01]

It might also be better for privacy to have extensions with one, easy-to-understand theme. General utilities extensions could be anything.

One example: I mention the name of each extension I use in Scratch projects I share to GitHub just so people know what kind of additional features they are using. I would particularly like to know when a project I'm using is capable of doing things I may not want it to be capable of doing, like connecting to the Internet. With this guideline, I don't have to worry about seeing an extension called "Utilities" and being left with questions.