Mars

1.- That would make Lemmy servers ultra unsafe to host. Server owners would not be able to moderate content hosted in their machine. It would make a good distributed solution, but not a federated one.

Maybe we’d prefer a centralized organization, with distributed resources. But seeing the defederation drama every week, it doesn’t look the path anyone wants to follow.

It’s a solution, but I don’t like it.

1.- It’s less resilient. If (more like when) one server goes down it could take the only community in a topic with it.

2.- If the moderators for the community of your interest are kind of dickwads, or absent, or malicious, you have no alternative.

3.- Federation can create weird problems. If your account instance is not the community’s one, you could be effectively banned, without doing anything wrong.

4.- Creates a perverse incentive for using the biggest instance you can for both creating communities and users. Some of the bigger Lemmy instances already are under heavy load and having problems to stay online. Imagine if we discourage using small instances.

Some mechanisms to “merge” communities across servers would be cool addition. Every Android community in every server that still federates with each other lists every post in all of them. Moderators moderate the posts in their instance. Link repetition is the same as inside of one single community. If one of the composing communities moderator team doesn’t does it’s part it could be expelled from the composite. Like a soft de-federation.

Just rambling. It’s a complex problem.

It’s a solution, but I don’t like it.

1.- It’s less resilient. If (more like when) one server goes down it could take the only community in a topic with it. 2.- If the moderators for the community of your interest are kind of dickwads, or absent, or malicious, you have no alternative. 3.- Federation can create weird problems. If your account instance is not the community’s one, you could be effectively banned, without doing anything wrong. 4.- Creates a perverse incentive for using the biggest instance you can for both creating communities and users. Some of the bigger Lemmy instances already are under heavy load and having problems to stay online. Imagine if we discourage using small instances.

Some mechanisms to “merge” communities across servers would be cool addition. Every Android community in every server that still federates with each other lists every post in all of them. Moderators moderate the posts in their instance. Link repetition is the same as inside of one single community. If one of the composing communities moderator team doesn’t does it’s part it could be expelled from the composite. Like a soft de-federation.

Just rambling. It’s a complex problem.

Multiple communities with the same theme in diverse servers mean lots of repeated information in my home page.

I find hard to find new niche communities. All is all, the common denominator. My home is what I already have subscribed. Local instance communities are there. But I don know a good way to get offended content from communities outside of those categories.

Vivaldi is a chrome derived browser. Using it entrenches Google power over the web.

The manifest v3 debacle, weird “standards” like the recent Web Environment Integrity and more are only posible because Google controls most of the web clients through Blink and V8. They can make or break standards thanks to the massive amount of Chrome and Chromium related browsers, like Vivaldi, Brave, Opera, Edge, etc.

So, glad you like Vivaldi, but you are not that far from google and are in fact an asset for their goals.

We need Firefox alive and well. If we lose it, Google will be THE web and will control it’s foreseeable future.

It’s not that huge of a userbase. Pinterest is bigger. Twitter just have a disproportionate amount of celebrities, politicians and journalists addicted to the instant feedback and drama.

Elon is hooked and high on his own supply, so he seems incapable of understand what Twitter actually IS for most users and that “ego boosting machine for the rich and famous” is not a business plan.

Enshitification implies a degree of planning and success that he seems incapable of right now. And you can’t jump to step three without achieving steps one and two. Never good for (most of) the users, never good for the advertisers. Nothing to squeeze.

I mean, it has gone to shit, but it doesn’t seem intentional. Even in the best of circumstances these changes would not be better for the bottom line than just doing nothing.

“Prompt Engenieer” is one of the funniest thinks that have happened in the recent history of the world.

“Learn to ask questions to a prediction algorithm and get rich! Is the work of the future! Software engineers and writers will lose their jobs, but asking questions is an evergreen field!”

Dude, if the algorithm only understand correctly formatted input is a parser. We have those.

This looks more like trining to make it run in a stolen raspberry pi in Elon’s basement than trining to extract value.

Let’s be real, there is no value left to extract.

I had a problem with my family account on Spotify and my options for asking for support were twitter dms or some meta stuff (Facebook dms?)

I was 🤏🏻 this close to cancel my account right there, but my partner still has social media accounts, so they solved it in my name.

Get a freaking email inbox…

They are completely disconnected, with the exception of the occasional spinoff or direct sequel, but those are easy to identify. The last game is probably the easier one of the series to pick up and play (this statement has been true for the whole existence of the series)

Where to start? Depends. Everyone of them is a huge game and a big time investment.

Taking into account you have no nostalgia for the series, I’d say your options, in order of what I think would stick are:

• Option 1: the last one. If you just want to play a modern action/rpg game with AAA sensibilities but weird enough, is not a bad option. You have no need for any previous knowledge, the gameplay is completely different to the one in previous entries, etc. Haven’t played so I do t know if it’s any good.
• Option 2: the 7 remake. One of the biggest milestones in the series retold for modern audiences, with updated graphics and narrative.
• Option 3: 16bit retro experience: FFVI, SNES or GBA version. The pinnacle of the formula for the 8 and 16 bit consoles. Upcoming titles in the series are way different. Great in every way a game can be good.
• Option 4: the 7 vanilla. The first international massive mainstream success for the series and one of the more influential video games in history. After this one, if you loved it:
  • Option 4a: the PSX trilogy. Go for FFVIII and FFIX for the full pre-render backgrounds and 3d models god killing trio.
  • Option 4b: the complication. If you are really into the setting and characters you have a few games complicating this one under the “Final Fantasy VII Compilation”. Some aren’t even RPGs.

If you go completely Final Fantasy insane after any of those, start with FF, the first one from the NES and make your way through them all. Prepare a couple thousand hours.

I’m sorry but framework and library in this post are going to be used loosely, because even React, Vue, Angular, Svelte, etc devs use the terms loosely.

React is mostly a UI library like you would find in most native app development. Of them all them JS frameworks/libraries is one of the less opinionated and with less batteries included. By design it does not does everything. Most other frameworks do way more.

It lets you define custom components. The components can have properties that their parent component defines and internal state. If the state or the properties change the component gets redrawn (magically). There are some lifetime functionalities (things to do on first render for example) and performance improving stuff (memoization) but mostly that’s it.

All the other features you talk about are third party libraries or frameworks that can operate with react or are build on top of and cover the bases, like routing, fetching, caches, server side rendering, styling utility libraries, component libraries, animation libraries, global state management, etc.

The big difference with the vanilla way is that the approach is mostly declarative. The runtime takes charge of updating the DOM when your components state or properties change.

You take a big performance hit, and an even bigger bundle size one, but the speed of development and huge ecosystem of readymade solutions can be really important for some use cases.

Other frameworks take different approaches to solve the same problems:

• Component system for code reuse and organization.
• Some way to manage state
• Some way to decide what to re-render and when.
• Extra stuff. Some frameworks end here, some have tools for everything you would need for a web app.