For your first printer I would recommend getting something you can build from scratch if you have the time. You’ll learn about all the different parts of a printer so you have an idea of what to do when something goes wrong. Prusa’s are great in that aspect as they have wonderful documentation and assembly instructions and it’s easy to buy replacement parts if you need it, plus they’re pretty low-maintenance once built. In your price range I think the MK4 kit would be a good option, just keep in mind that assembly can take upwards of 10 hours depending on how fast you go.

However, if you want to buy something and just forget about it, one of Bambu Lab printers would probably be a better option. Their parts are more proprietary and you won’t get the same learning experience, but its dead simple to setup and use. (Not to mention incredibly fast).

Either way, you’ll be getting a solid printer that should last you for a while, so have fun and be sure to post here if you have any more questions!

The problem is who decides when an instance contains “nothing of value”? You’re leaving that up to a small handful of admins. You could also encounter a situation where multiple admins collectively decide to defederate from anyone who doesn’t subscribe to the same block list, so any instances who hold different opinions are cut off from loads of content on other instances. We run the risk of splitting the fediverse up into multiple, totally isolated chunks which I don’t think is a good thing on the whole.

Personally, I’m not a huge fan of instance-level defederation as a concept. I’d rather leave it up to individual users to block certain instances/users/communities if they don’t like them. Otherwise you get a situation where admins can go on a power trip of blocking instances or users that they don’t like for petty reasons or just because that instance and it’s users don’t subscribe to the group think of the day.

I really like the fediverse, but this whole “instances blocking other instances” seems like a good way to kill it quickly, or create useless echo chambers that are as bad if not worse than the centralized platforms that people are seeking to avoid.

Free speech means having to deal with some bad apples from time to time. Even if people are saying things you don’t agree with, you need to remember that that also means that you’re allowed to say things that others might not agree with without being silenced.

Well, both, but if you’re just talking about the frontend, then yeah I’d use a frontend framework like React (though personally I’d rather use Vue or Svelte if I had the choice)

As a dad that loves the show, I’m in!

Same for me. The day Apollo died was the day I quit. I’m starting to warm up to Lemmy more and more over time as it scratches that same itch.

A Christian Carol. I know Christian movies are low-hanging fruit, but the awful CGI, terrible writing, horrible camerawork, and nonsensical story really just make it truly awful.

Does AppleTV have a Jellyfin app yet? We’ve got a few around the house and I’d love to switch to Jellyfin from Plex.

Started with an Ender 3 V2, which I tried modding with BLtouch because I hated the lack of auto bed leveling. Eventually I just got so frustrated that I got a Prusa i3 MK3S+ and I love it to death. It was just a quantum leap over the Ender and well worth the price bump. I’ve lately been selling prints for profit and have been eyeing the Bambulab X1 Carbon for its speed and the AMS.

No, not necessarily. React usually calls the backend through HTTP requests in order to fetch data. The backend code is written as an API, not a full-blown web application, that handles those requests, validates the request, permissions, business logic, etc, and then returns a response. The backend code is the gatekeeper between the client and any databases or external API’s in your application.

Traditionally you would use REST API’s, although there are more modern ways of communicating with a backend like with graphQL. But if you’re just starting I would learn how to write a REST API using PHP, Python, Ruby, C#, etc and go from there. REST API’s are pretty straightforward. Essentially your server just exposes a bunch of “endpoints” which are URL’s that represent a resource (for example https://mycoolwebsite.io/api/users) and making certain calls to those endpoints prompts the server to perform some action (for example, an HTTP GET request to api/users/123 gives you the information of the user with the ID ‘123’) the server typically serializes the response data to JSON, so that the client can then receive the response from the server and do something with it. When writing your backend, you are responsible for defining these endpoints in your code and writing the logic that executes whenever a given endpoint is called. For example, when creating a new user (with an HTTP POST request to api/users), you may want to send an email to the newly-created user for them to validate their email address. You would do this by calling some external email service like SendGrid, Mailchimp, etc. and sending a validation email to the address that the user sent in the request body. After that you would create a new user record in the database and initialize the “is_account_verified” field of that user to false. In another endpoint (api/users/{id}/verify-email) you would then check if the verification email has expired or not, then change the verified flag in the DB if it is a valid link.

React is a JavaScript framework. It is mainly used to make complex UIs for websites and apps with React Native. PHP is a server-side language that can communicate with databases, external API’s, other servers, etc. You could technically accomplish these same tasks with a front end framework as well, but generally a server-side application is used in practice as you would need to expose things like API keys, database connection strings, and so on that you wouldn’t want to pass to a client-side application, since they are inherently untrustworthy.

In a lot of my applications I use the SPA approach which has two (technically three) layers. I use Vue (another framework like React) for the frontend application, and C# (a server-side language that can do many of the same things as PHP) for the backend with SQL Server as the database.

Where it gets confusing is that you can actually just cut out the frontend framework entirely depending on the complexity of your application. PHP (And C#, and a bunch of other languages) can generate static assets like HTML and send them directly to the browser “pre-baked” This is known as server-side rendering. Essentially you fetch whatever data is needed for display on the page and then generate the page view on the backend, then send that entire view to the browser. With a single-page application using a framework like React, you would request the necessary data from the client-side app, and your backend code would process the business logic and send the data to display. The framework would then handle re-rendering the page with the updated data.