is there a way to browse Twigls ? all / per user ?

[FabriceNeyret]

is there a way to browse Twigls ? all / per user ?

• sorted by date, likes, etc.

[doxas]

@FabriceNeyret

Some code edited on twigl remains on the back end of the system.
But not all.

There are no plans to implement so-called sign-up or sign-in functions in the future, and we do not intend to make the service like Shadertoy, where data is tied to individual users.

For various reasons, my own unchanging feeling is that I want to provide twigl as a simple and easy-to-use application as possible.

[FabriceNeyret]

I do see an author name at the bottom right of twigls ( at least the ones I checked )...
Oh, I get it : it means you, not the author of the given twigl !

Still, having a gallery of existing twigls would be cool ( + even more attracting ).
( And you do have a "like" count that could allow sort by like or date, but ok it is easy to fake likes since no registration ).

[doxas]

As you pointed out, it is possible to increase the number of Likes if one wants to do so illegally.
The twigl Like function was initially implemented as a dedicated function for real-time distribution. Since we went to the trouble of creating it, we are able to give a Like when we generate a link to a work, and this is just a bonus feature.

I do not plan to make any changes that are likely to bloat the system, such as managing users or listing submitted shaders, at least not in the future myself.

However, many of the shader creations that have been uploaded to the web can be found on Twitter by searching for twigl or #つぶやきGLSL.

https://twitter.com/search?q=(%E3%81%A4%E3%81%B6%E3%82%84%E3%81%8DGLSL%20OR%20twigl)&src=recent_search_click&f=live

[baodinhaaa]

I have a few quick suggestions for you about UI: add an edit mode that the layer edits and displays as vertical and separate; resizable rendering layer for faster rendering; FPS display. This will make coding on twigl faster.

[doxas]

@baodinhaaa

Thanks for the suggestion.

I'm of the opinion that twigl should be simple and I don't want to make it more complicated, especially when it comes to the interface.

The idea of displaying the FPS is a good one, but I don't see the point of it beyond being somewhat useful on each editor's local environment, since WebGL's performance is always variable depending on the platform it runs on.

[Kamoshika-vrc]

Currently it is possible to click the Like button multiple times repeatedly.
Is it possible to prevent this by referencing the IP address or something?

[doxas]

@Kamoshika-vrc

Hi Kamoshika!
Thanks for always using twigl.

Like in twigl was originally implemented with the intention of conveying the excitement of the audience to the editor by having them hit the Like button repeatedly during broadcast mode delivery.
Therefore, the current specification of being able to hit the Like button multiple times is intentional.
What is your reason for wanting to suppress it?

[Kamoshika-vrc]

@doxas

The reason is that many of the users who opened twigl's link probably recognize "Like count" as "the number of people" in the same way as twitter, Shadertoy, NEORT, etc.
At first I thought I would be able to click the Like button only once.
Twigl doesn't have user accounts, but I think the users' intuition is that they can click the Like button only once.

That is just my personal opinion.
And I cannot imagine the time, financial and human cost of this change.
So, please make your own decision.

If you will not change the behavior of the Like button, how about adding the description to the "information" or mouseover text of Like button that users can click it as many times as they want?

[doxas]

@Kamoshika-vrc

Hmmm...

Personally, I have a strong sense that "it doesn't matter if I can Like multiple times" in the first place, rather than the cost of implementation.
It is true that for general account creation type web services, including Shadertoy, Like may be a one-time thing, but I am fine with twigl being an exception.

If I wanted to allow a user to like a work only once per work, I could do so by using localStorage or something similar, but I don't see the need to do that.
I can imagine that from the point of view of someone like you who uses twigl a lot, the number of Likes could be important. However, if, for example, consecutive Likes would be detrimental to fairness, then editors themselves should not be able to Like the site in the first place, and many other related problems and issues would arise.
Because twigl does not want to consider these issues, the interface design is not designed to create accounts.

Do you think it would be better to hide the Likes?

I think it would be fine to have the Like button there as it is now.

[FabriceNeyret]

... or maybe to have no "like" feature at all, as it is has no real significance, while being deceiving, and it doesn't help me to find again the shader I once liked ;-)

[Kamoshika-vrc]

@doxas

I don't think you should hide the Likes.
I respect your thoughts.