Search results

But as i say that i see which part about it is confusing. will fix

when you click on a thread, it puts in FORUMS after the HOME so you have both

Dev forums are up, which is similar to what we recently started doing with canary frontend, a way for us to roll out things before it hits production. Work has mostly completed for the initial release and will continue after, but we're at a comfortable spot where it makes sense to reign in some...

@Tamerlane tags curation will remain with the staff.

tags are already planned

@Matrixik good point, we'll see what we can do with that

hey @Matrixik thats a good idea you have and something we definitely want for v5 you also identified the exact problem why we are having the database issues that we are currently struggling with. first i'll give some context to what we're currently dealing with and then describe the plan we...

@Agent4T7 If you have a bad connection to our ddos-guard provider, that's unfortunately nothing we can help you with. An alternative is the fileurl upload, where you can paste a dropbox or googledrive link and have the server download it that. As a groupleader you have access to this feature on...

@belgopolac no idea, sry

@MiBi250 keeping track of total chapter counts is difficult with the current database. Things like total chapter counts will be much easier to calculate and make available through the api in the future.

@Lexical good suggestions, that is similar to what I have in mind @nonindustrial there are different search indexes for all types of resources, there is manga, chapter, author, user, scanlationgroup (and probably more...) because its way faster and less resource-intensive to query elasticsearch...

@Lexical can you make an example what you would expect in relation to the end tag? how would you want to use the search where it is relevant?

@Tamerlane good call with the tags. we have them planned but i kinda forgot about them because they arent modeled in our databases yet. I'll try to update the list in OP soon. Generally I dont see a reason to overengineer them in terms of how they interact with the search. There might be a way...

@Tamerlane zero (that i know of) the good thing is that its voluntarily and enough variety in tasks you can pick up if you want to. (thats also why it takes so long to make new stuff sometimes) @waterflame we will probably have to implement something similar to this, as thats how 3rd party apps...

@Ivegotnolife for the main site. Anything related to forums or comments is another topic, XF will hopefully handle that. For the entities that i listed (manga, chapter, artist/author, group, user) we will have to craft our own solution.

@waterflame same reason windows went from 8 to 10

@Altaki Unfortunately not. There is an internal overview of the individual components but I dont think its anywhere near a roadmap. Development pace has picked up a lot in the past 2-3 months so I hope i can start sharing more information. This is the first step

@blackyawgdom the current plan for v5 is to migrate the self-coded forum to Xenforo. Manga, Chapter and Group comment pages will be fully migrated. I like the current way to have a "thread" for each of those pages, dont see a reason to change that. With some API magic they should be easy to...

Current search is very limited, i want to find out what requirements i need to work with. At the present moment, v5 will use Elasticsearch There are 5 endpoints that will support search queries, /search/manga, /search/chapter, /search/author, /search/user, /search/group I will not directly...

What this forum is about: Our future rewrite of the MangaDex site code is called v5 I will make threads here for ideas I have that I need pushback on. I also found that even if I don't like a suggestion, there sometimes are bits of it that I like or that want to read up on. Or that make me...