[main] Server #236
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea here is to have a normal server (with a hook up link? api link?) that records (writes) viewed and/or published mods events on degmods.com (as well as blogs), scrap its data (event id, author npub/nprofile, name, thumbnail image url, tags, publish date, edit date, nsfw, game, repost, categories, and maybe more in the future), and have them on a list (so two types of lists: mods first, then blog).
If the user views a mod post (or publishes a mod which would also result in them viewing it after the publish), there'd be a scan on that list to see if its there. If it's there then nothing happens, and its cached on the user end so that it doesn't perform the scan again. If it's not there then it records/writes it to the list. An entry should also consider if the data has changed and update accordingly.
(to also think about other methods to decrease the potential load on the server? Perhaps have a version number for each list that gets updated (ex: 1 to 2) every time the list gets updated so the user's local cache would only scan the cache server and update their local cache if there's a mismatch)
This list would be running in parallel with normal nostr operations. Running on the landing page (latest section), /mods, /profile, /game/name, /blog, /search.
In the settings page, there'd be a new tab called 'Caching server' that has a field with a link to that server with the list. The user can change it and hit 'save' if they desire (local change), with a warning popup mentioning that they might have a worse experience on the site if they do so (having an empty field or changing it from the default server).
If the user removes that connection link, then it just won't work and the site behaves as it current does,. If the user adds their own link, it would check if they have a similar server structure as how we've done it; if it's the same then it should behave normally, and if not then it just won't work (shouldn't break the site).
The reason this feature is needed is because of a big issue:
Users visiting the site are seeing maybe 10 to 20 mods, when in fact there are 100+ and eventually a lot more.
This would also potentially solve the pagination issue and we'd have correct numbering now on the mods and blog pages and elsewhere (profile of a user), since there's a hard reference (the caching server).
Based on the talk, the DB list will have non-changing data:
nadd
author
publish date
source (url)
source (client name that we added recently)
I'm thinking we should also include the non-static details as well in the list (like if it's a repost, and tags, etc), as they'd play a role in the site's performance as well with filters and pagination, and load times (considering the future of potential millions of posts).
If they get changed, then the DB would get updated as well. If it's changed on degmods, then it'll be detected easily, same if it wasn't but if someone views it then it would.
From the latest discussion:
The server will be developed normally, then make it work with a DVM, so that in the future if DVM becomes unreliable, we can just remove the DVM part and just have a server with an IP hooked up / domain.
To also see if we can make the client just target this specific DVM only and not look for other DVMs (so that we can have it in the settings page and users can remove it / swap it if they want, or add more if that's decided).
[main] Caching serverto [main] Server