@o_o
@programming.devHi all,
I'm seeing a lot of hate for capitalism here, and I'm wondering why that is and what the rationale behind it is. I'm pretty pro-capitalism myself, so I want to see the logic on the other side of the fence.
If this isn't the right forum for a political/economic discussion-- I'm happy to take this somewhere else.
Cheers!
Hey folks, was just thinking that one of the major benefits of forums is that it stores and indexes knowledge for the rest of time. I still regularly look up stackoverflow questions written years ago.
Are lemmy instances (such as https://programming.dev) going to be similarly indexed?
If there's been no thought on how to implement this, I was thinking that meta tags could be used to indicate to search engines that homegrown content (i.e. content that belongs to your own instance) should be indexed while federated content (i.e. content on your instance that was federated from other instances) should remain non-indexed.
That way, searching the title of this post on Google will only lead to a single result on the single instance that owns it.
Thoughts?
Thought this might interest the general programming community as well! If you've ever been interested in the different types of ways websites can render themselves....
cross-posted from: https://programming.dev/post/223726
Here’s a quick summary of the different ways you can load a website.
SSR (Server Side Rendering): The classic way. Browser makes request to server, server creates an HTML/CSS/JS bundle, sends it to browser.
CSR (Client Side Rendering): The vanilla React way. Browser makes a request to server, server sends back JS code which runs on browser, creating the HTML/CSS and triggering browser to further make requests to load all assets.
SSG (Static Site Generation): The “gotta go fast” way. Server creates an HTML/CSS/JS bundle for web pages at build time. When browser requests a page, the server just sends this pre-built bundle back.
ISG (Incremental Static Generation): The “imma cache stuff” way. Server may create some HTML/CSS/JS bundles for web pages at build time. When the browser requests a page, the server sends this pre-built bundle back. If a pre-built bundle doesn’t exist, it falls back to CSR while it builds the bundle for future requests. The server may auto-rebuild bundles after certain time intervals to support changing content.
ESR (Edge Slice Re-rendering): The “cutting edge, let's get latency down so low it's practically in hell” way. Server does SSG and tells the CDN to cache the bundles. Then, it instructs the CDN to update the bundle in the event that page content needs to change.
In order of performance, usually: (SSG = ISG = ESR) > CSR > SSR
In order of SEO: (SSR = SSG = ISG = ESR) > CSR
In order of correctness (will users be shown “stale” information?): (SSR = CSR) > ESR > ISG > SSG
Instances, of course, have some bot-mitigation tools which they can use to prevent signups, etc.
However, what’s stopping bots from pretending to be their own brand new instance, and publishing their votes/spam to other instances?
Couldn’t I just spin up a python script to barrage this post, for example, with upvotes?
EDIT: Thanks to @Sibbo@sopuli.xyz ‘s answer, I am convinced that federation is NOT inherently susceptible, and effective mitigations can exist. Whether or not they’re implemented is a separate question, but I’m satisfied that it’s achievable. See my comment here: https://programming.dev/comment/313716
Hey folks! Just realized something that makes Lemmy different from Reddit. Because of the federation, your votes are not technically anonymous on Lemmy. At least, I think.
Although there’s no UI to look at a user’s voting history yet, one could conceivably be built by an instance. Perhaps coincidentally, I hear there’s instances out there populated by mostly bots?