@mana looking back at your original question, I think you're misunderstanding how that header works.
Your browser is refusing to load the mp4 file because the source site (vfx.mtime.cn) doesn't have a permissive Access-Control-Allow-Origin header. I don't think it has anything to do with your forum's ACAO header.
@aleksei Sounds like potentially a cool idea. But also potential for abuse. For e.g. many forum admins invest significant effort to foil file scrapers, etc. and this could facilitate/exacerbate. Maybe mitigated to some degree by permission restrictions to logged in users but..... then the bots just create a sock puppet account.
Another potential issue: long running threads sporting hundreds of images, etc. How to display? Could be a UX conundrum, eh?
Hmmmm... Still could be interesting for some situations.
Not a dev but will hazard a guess that this might should be a plugin rather than core front end function as you suggest. Sorry I cannot offer more targeted insights.
@鄭宇佋 A less biased answer would be - they aren't entirely equivalent, and the choice is a combination of specific needs and preferences that IMO can't be generalized to "x is better in general".
phpBB is the oldest forum, and as such it embodies the older style of forums from before social media made things like tags, real time interactions, feeds etc. popular. However, it is probably the most feature rich of all offerings if you have time and knowledge to set it up.
Flarum (and I think the Laravel community software too? Never used it :V) is a simpler forum that is tag-based. You can nest tags once in Flarum, but only once and it seems to more encourage a feed approach where your main page is filled with topics sorted in some way and you use tags to go somewhere if you're looking for something specific. This is in contrast to the "classical" structure I mentioned, where you will have subforums/categories that you can infinitely nest and the idea is that the user first goes to the category that will have the topics that will be interesting to them.
However, NodeBB and Discourse are both somewhere closer to the middle, but on the opposite sides. In both you will find categories and tags, but from what I've seen the emphasis is different - NodeBB is categories that can have tags, Discourse is tags that can have categories 🙂
Of course, there are a lot of other differences. As mentioned, more modern software is better at doing stuff real-time. Notifications, chats (Discourse and NodeBB have some form of private conversations built in. Flarum and phpBB have extensions that add it), loading new posts without reloads etc.
AFAIK NodeBB is the only one of these using WebSockets (socket.io)
Discourse uses some custom polling based protocol.
Flarum actually doesn't do much live stuff by default (just kilke phpBB), but it does have notifications that can use officially-supported pusher extension to work.
One major difference though - phpBB, Flarum and Laravel.io are PHP-based, so you can make them work on generally cheaper shared web hosting, meanwhile Discourse and NodeBB will require a server that can run Ruby or Node respectively - for example a Linux VPS.
Which one is better depends on what you want then. Laravel.io seems to be most limited in terms of customization, unless there are some undocumented features on that front. So if there are any things you don't like about the way it looks or feels - don't choose it.
If you like the Flarum tag structure and don't mind it lacking some things (well, it's a beta after all), it seems like the most performant option.
phpBB? If you are willing to buy/develop some modern theme and spend time to configure it, sure. Otherwise I wouldn't recommend it.
The decision between NodeBB and Discourse is harder, and while I prefer NodeBB, I'd say it's mostly down to your preferences, specifics of what you want to use the forum for and the preference for technology stack (Node, Express, MongoDB/Redis/Postgres + no major js framework outside of jQuery on front-end for NodeBB vs Ruby on Rails, Postgres + Ember.js on front-end for Discourse).
Some unfortunately older topics on this (some will have much more recent replies, so might be useful to read them; I tried to include topics from meta-forums of other forum software and user forums based on software in question):
BTW, why do I have a browser window? Is it because Iam using Android, or I am running nodebb 1.14?
It's because you're running 1.14 actually. The actual scripts for installable PWA only appeared in 1.15.
However, browsers are confusing so they also offer the option to "add to home screen" any website, but instead of actually considering its manifest for how it's supposed to run and using the service worker properly it will be just an icon to open that website in the browser.
I would've recommended checking this website to see how it's supposed to work, but it seems to be broken in 1.16.2 unfortunately (mentioned in this issue - service worker was moved to its own directory so only paths starting with /assets/src/ are in its scope.)
EDIT: while it was mentioned in the issue #9193, it wasn't the main focus. I commented on it on #9127, solution to which actually broke the service worker
Posts are sorted incorrectly in the feed in case of updates (at the time of the update of the post)
In the XML/RSS, the order of the posts is correct, but the publication date of the edited post is updated. At least this confuses my feed reader