removed

[FLH]

removed

[FLH]

removed

[mimzy]

Great initiative!

[FLH]

removed

[FLH]

removed

[mimzy]

Do I understand correctly that in addition to thumbnail grid, ALL full-size images are embedded behind spoiler tags? I don't like this very much, because the images behind spoiler tags are still loaded every time the thread is opened (unless the images are in browser's cache), which wastes network bandwidth and makes the site slower.

[E9A7F3bD]

Do I understand correctly that in addition to thumbnail grid, ALL full-size images are embedded behind spoiler tags? I don't like this very much, because the images behind spoiler tags are still loaded every time the thread is opened (unless the images are in browser's cache), which wastes network bandwidth and makes the site slower.

If you have a suggested alternative, I'd love to know.
I don't like clicking through the pictures one by one to view full-size.
There is not much to do in the external way, under the existing framework.

The best way is of course to implement:
Unified previews upload path and optimized layout

And FLH includes signatures to make it easy for you to make batch replacement in the future.

@FLH, thanks very much to developing this toolbox, it greatly improved my life.

[E9A7F3bD]

which wastes network bandwidth and makes the site slower.

I think it should be trivial for most people's local bandwidth.

For servers, why not cache static resources such as images in CF CDN?
This will drastically reduce the number of requests fallback to the source.

[mimzy]

Do I understand correctly that in addition to thumbnail grid, ALL full-size images are embedded behind spoiler tags? I don't like this very much, because the images behind spoiler tags are still loaded every time the thread is opened (unless the images are in browser's cache), which wastes network bandwidth and makes the site slower.

If you have a suggested alternative, I'd love to know.
I don't like clicking through the pictures one by one to view full-size.

Usually the thumbnails already give a good enough overview for me. I only click maybe on 1-2 images.

Sometimes full-size images are important, so the poster may want to post those. But I don't want that every time somebody posts 20 thumbnails, all full-size images are embedded also.

So at least there should be a switch: "☑ Embed full-size images" or something like that.

Moreover, it would be good to explain what is behind the spoiler tag. It could be mediainfo, for example, or something about the plot that I should not read before watching the movie.

There is not much to do in the external way, under the existing framework.

The best way is of course to implement:
Unified previews upload path and optimized layout

One possibility would be to develop a user script similar to flmify that I did a while ago. In that case the purpose of the script was to "improve" LMA and RFF, but a similar script could be implemented to "improve" FLM. (Note: I don't think flmify still works, because LMA no longer even exists and the structure of RFF has probably changed).

Of course, if you develop a javascript that is of general interest, we can include it in FLM directly.

And FLH includes signatures to make it easy for you to make batch replacement in the future.

I'm not sure I understood. Can you elaborate?

which wastes network bandwidth and makes the site slower.

I think it should be trivial for most people's local bandwidth.

Most, yes, but we don't want to exclude those few people with bandwidth problems.

For servers, why not cache static resources such as images in CF CDN?
This will drastically reduce the number of requests fallback to the source.

Static resources are already cached by CF, but FLiM images are not static, because you have to log in to see those. I don't want FLM to be used as a generic image host.

@FLH, thanks very much to developing this toolbox, it greatly improved my life.

I'm sure FirstLoveHelper will be helpful for many people

[E9A7F3bD]

People have different habits.

I like both forms, seeing all thumbnails, and browsing all the larger images in sequence.

I don't want to argue about the define of the spoiler tag, but I think a lot of people also treat it as avoiding the interference of the mainline "details" blocks.

I know about user script, but the problem is that it has high permissions and threshold for people to use.

"include it in FLM directly" sounds like a viable idea, maybe FLH can consider that too.

FLH has a fixed format relative to each version number, so matching and replacing will be much easier than something without pattern.

You can never take care of all the minority and should not be the price to make things better.
To save them bandwidth, should you ship a website version without pictures or even styles?
How many mainstream websites do you think are correctly implementing a11y recommended practices today?

Why not cache images? I can't see the contradiction between log in to see and not be a image host.
Even with the static images, you can still control the content returned by the page and refuse to be linked by cross-site restrictions.
Processing and returning images through php is a huge waste, both in terms of calculation and bandwidth.