use them with the version they last worked with

The front-end has to be compatible with the version of the engine. So you can either 1: use old versions of the engine (I don't recommend it) 2: update the front-end to the new specifications (kinda laborious) 3: throw the things you want from the FE you want into another FE that's updated. That isn't too hard, specially if all you want is just the css. The errors you saw were probably about missing elements.

>>409 So the older third party frontends just aren't compatible with the latest version of Lynxchan. That makes a lot more sense. The repo sounds like newer frontends were incompatible with older versions of the engine, so I was assuming older fes were still supported in the newer engines.

>>410 Nope. There is no compatibility at all because elements can be removed or added to the specs.

>>411 I see. What would I need to do if I wanted to change a bunch of the older third party FEs to work with the current build? Also, is it safe to say that yanking the CSS from another compatible FE and just overwriting it into the CSS in /fe on the server would be enough to change the global CSS for a site only running one? I don't see any specific problems with it but CSS isn't my specialty. Thanks for replying in person. Its cool that you do all this.

>>412 >I see. What would I need to do if I wanted to change a bunch of the older third party FEs to work with the current build? These version changes are listed on doc/SpecChangeLog. >Also, is it safe to say that yanking the CSS from another compatible FE and just overwriting it into the CSS in /fe on the server would be enough to change the global CSS for a site only running one? I don't see any specific problems with it but CSS isn't my specialty. For the most part, yes. It doesn't change that much from version to version that most of the css would become too invalidated. These changes fall mostly on elements that change for the html and on back-end changes for the forms and js. Naturally there would be new elements that wouldn't be covered by the old css, so some adjustements would be very probably necessary. This is the most practical way to get what you want from a discontinued FE, IMO. Yank the css and adjust where necessary. That's way easier than adjusting the HTML and js. >Thanks for replying in person. Its cool that you do all this. Is the least my neet ass could do :v

>>413 Do you know if there's a known issue with getting mongo to run on Debian 9? I''m tinkering with this little site idea and I'm getting odd dependency errors. Mongo 4.0.x needs mongodb-org-server which requires libcurl4, and Deb9 says that libcurl4 doesn't exist. It looks like people running Spotify have a similar problem, something with libcurl3 and libcurl4 trying to coexist. I purged mongo and curl completely to work from a clean slate but I'm not sure how to approach the issue.

And when I installed MongoDB from the private repo to get the correct version, attempting to start Lynxchan throws this mess. [Error: connect ECONNREFUSED 127.0.0.1:27017 at T*****ConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) { name: 'MongoNetworkError', errorLabels: [Array], [Symbol(mongoErrorContextSymbol)]: {} }] at Pool.<anonymous> (/home/admin/LynxChan/src/be/node_modules/mongodb-core/lib/topologies/server.js:431:11) at Pool.emit (events.js:310:20) at /home/admin/LynxChan/src/be/node_modules/mongodb-core/lib/connection/pool.js:557:14 at /home/admin/LynxChan/src/be/node_modules/mongodb-core/lib/connection/connect.js:39:11 at callback (/home/admin/LynxChan/src/be/node_modules/mongodb-core/lib/connection/connect.js:261:5) at Socket.<anonymous> (/home/admin/LynxChan/src/be/node_modules/mongodb-core/lib/connection/connect.js:286:7) at Object.onceWrapper (events.js:417:26) at Socket.emit (events.js:310:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) { name: 'MongoNetworkError', errorLabels: [ 'TransientTransactionError' ], [Symbol(mongoErrorContextSymbol)]: {} }

>>414 he doesn't use debian

>>414 No idea. I recommend centos and personally I think debian is downright a trash distro. >>415 Can you connect to mongodb through localhost on that port?

>>415 MongoDB probably isn't running. Did you systemctl enable mongod and then systemctl start mongod?

>>415 does this front end use typescript?