@Kitten If you're seeing that error it looks to be something served directly from MinIO, and not via nodeBB...
Staff
Employees & Interns of NodeBB
Posts
-
Access from the forum to VDS to a home computer with MinIO via nodebb-plugin-s3-uploads -
Is it possible to override client side javascript from my plugin?You should be able to overwrite a core module completely using your plugins
modules
section. For example to overwrite the navigator module with your own you can do."modules": { "navigator": "public/navigator.js" },
Copy the navigator module from core and make your changes and it will replace the core module during build.
-
There is some questions when I use the nodebb-plugin-composer-quillI've updated the plugin for 3.2 and up in this pull request https://github.com/NodeBB/nodebb-plugin-composer-quill/pull/477. Should look like below on latest nodebb.
-
nodebb-plugin-reactions slow after selectingLet's say you open the reactions dialog, and in the dev tools you see a bunch of network requests to load the images (makes sense).
After you close the dialog, do you continue to see additional emoji-related network requests in the dev tools, when navigating through the site?
-
FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea)@[email protected] whether we decide to use
as:context
or not to represent second-order collections is still to be determined, but we can hold off on that until we figure out first-order collections. I'm not saying we hold off on it for years, just months.FEP 7888 doesn't disallow other uses of
context
. It just gives direction for implementors who wish to use it to represent a first-order collection of objects. The key here is whether that context is resolvable to a collection, and (maybe) whether that collection contains items of interest (as:Note
-like objects or otherwise).The ForumWG with input from other interested parties (@[email protected], @[email protected], among others) have provided an oral history that suggests that
as:context
is effectively unused, and what usages are found in the wild already conform to FEP 7888.Do I think
as:audience
is the solution to second-order collections? No. It's just the way it is now, but not the way it will be forever. -
It's interesting to see a lot of the proposed solutions to the problems botsin.space faced are solved problems on AT and part of why Bluesky made their own protocol instead of using AP.@[email protected] said in It's interesting to see a lot of the proposed solutions to the problems botsin.space faced are solved problems on AT and part of why Bluesky made their own protocol instead of using AP.:
Yeah, it's weird that every instance has to have a copy of every file, usually on expensive cloud storage. A shared resource would help there!
That's funny you consider that a protocol deficiency.
It's not specified by ActivityPub at all. It's completely a Mastodon-ism.
-
FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea)@[email protected] said in FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea):
If not, what is holding us back from creating something new for categories?
Nothing. Being able to traverse remote contexts would be absolutely wonderful, and is in line with my goals for the ForumWG.
However that comes after we hammer down a solid recommendation for conversational contexts. Let's hold off for now, we'll get there.
-
FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea)@[email protected] @[email protected]
@[email protected] said in FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea):
i am slightly dissatisfied with how
audience
ended up being usedI am as well, although I was willing to implement it for the sake of compatibility until a better solution arrived.
While I alluded earlier that a NodeBB post could have multiple contexts (the topic and the category), it is better described by levels. Posts in Topics, Topics in Categories.
I suppose then a context would have a context. Makes sense to me.
-
FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea)@[email protected] ah, but we do, and like I said earlier, NodeBB achieves this by following the
audience
property aspect of FEP 1b12, which is in use by several other implementations already.A NodeBB post is part of the topic/thread context, and it is also part of a category, just like your "projects". Different name, same thing (more or less).
-
FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea)@[email protected] How to handle multiple contexts is indeed a topic that is well worth visiting. I hear you when you say that given multiple contexts, you don't know which one is the thread. I don't have the answers today, but I want to set the framework so that when we do find the answer, we won't be hamstrung by a past decision.
Right now my thinking is that if you have multiple contexts:
- You might not need to use multiple contexts (
as:context
for the thread,as:audience
for the collection one level higher) - We should recommend that contexts be ordered from narrowest scope to widest
That ought to handle practically all situations (ready to take my words back on this one hah!)
The one sticking point would be situations where an object is part of multiple contexts at the same scope, e.g. a software that lets you
inReplyTo
multiple context-independent objects. In that case, not even @[email protected]'sthr:thread
property would help because we'd want to set two threads there too! Now we're back at square one.So at least for today, we can probably safely declare that if multiple contexts are defined, and they both/all point to resolvable collections, you could treat them all like thread-like data structures, if that's your software's thing.
- You might not need to use multiple contexts (