Tech report for 2022

Everything About Fiction You Never Wanted to Know.
Jump to navigation Jump to search

About the Author

avatar I helped Vorticity/Labster found this site because not everyone wanted to trope on Wikia, and because, honestly, there needs to be an alternative to TV Tropes, especially since allegiance to advertisement sponsors and an increasingly oppressive "Stop Having Fun!" Guys atmosphere seems to have replaced the laid back wiki many members of this site used to enjoy.

I'm the tech guy around here, and I mostly just make sure everything is working properly and manage one of the current approved site bot accounts for maintenance edits and other needed projects.

I'm not a fan of admin fiat decision making and prefer to solicit suggestions from the community before making any major decisions, so drop by the The Forums or my talk page if you have a question.

I also do some game reviews for ChristCenteredGamer as of 5/22/2019.

Other recent contributors

Make this page better by editing it.
GethN7
1

2022 has begun for All The Tropes with a few things that have become quite apparent as issues for which we need to consider solutions.

For quite awhile now, we have used Flow (the StructuredDiscussions) extension as our standard talk page extension. It served us well for some time, but we are likely going to need to depreciate (if not remove) the extension for the following reaons.

First off, Flow is not being maintained regularly aside from periodic patching for security issues. Second, it has acquired several performance issues and limitations that have resulted in timeouts and poor performance across All The Tropes. Finally, a more lightweight option has become available which we believe would better suit our needs.

Accordingly, our prospectus is as follows:

  • Depreciate Flow for user and article talk. It will be retained for the Reviews space and all existing Flow pages will be archived to preserve history. The extension will remain active but cease to be actively used except for the areas specified.
  • Enable CommentStreams and make it the default for user and article pages. It also has built-in operability with SocialProfile which is quite desirable. Finally, it is more lightweight and performance friendly.

Another issue is that Miraheze has reconsidered how to implement an Elasticsearch cluster this year (January projected ETA). If successful, we will be able to offload search on that and enjoy finer-grained search capability than we have had prior.

If and when this happens, we may need to make further changes to categorization structure to accommodate this, but that will be determined when it occurs.

No other issues appear to be pressing, but if they are ATT staff will keep users apprised of further developments.

Finally, we would like comments on this report and users may vote on the proposal to switch from Flow to CommentStreams below.


Link to extension with technical documentation:

https://www.mediawiki.org/wiki/Extension:CommentStreams


Should Flow be depreciated for CommentStreams as outlined above?
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 6 votes since the poll was created on 15:28, 1 January 2022.
poll-id 44A885F867498F08D275098EBE7B7192



NOTE: Comments has been disabled temporarily, so feel free to comment below this notice, please sign your name with four tildes and bullet point your comments.









Loading comments...