chromodynamic

joined 1 month ago
[–] chromodynamic@piefed.social 6 points 4 days ago

Since anyone can create their own subreddit and become a mod there, does this mean that anyone can look at these profiles?

[–] chromodynamic@piefed.social 16 points 1 week ago (3 children)

But why do people want their text editors to do completely unrelated tasks? Genuine question.

[–] chromodynamic@piefed.social 33 points 1 week ago* (last edited 1 week ago) (5 children)

The main differences are:

  • package management (how you install new programs)
  • release model (fixed vs rolling)
  • default desktop environments (the GUI / look and feel)
[–] chromodynamic@piefed.social 21 points 2 weeks ago (1 children)

If a Fedi or BSky instance wants to support connecting to the other side, they should implement both protocols. Bridges are just a duct-tape solution.

[–] chromodynamic@piefed.social 82 points 2 weeks ago (29 children)

I saw an interesting video suggesting that the real motivation is to give megacorps like Google a new business acting as "banks" for identity, i.e. the Internet would get so inconvenient that people would just save their identity with Google (or Meta, etc) and then use them to log in to other websites.

I probably explained it badly, but the video I saw is here. https://www.youtube.com/watch?v=tAd-OOrdyMw

People in the comments pointed out that those companies would also have the ability to delete or suspend your identity verification if you did something they didn't like (or refused to do something they wanted). Reminds me of the SIN from Shadowrun .

[–] chromodynamic@piefed.social 5 points 3 weeks ago

If you want to message them about it, now is the time most likely to work.

[–] chromodynamic@piefed.social 6 points 3 weeks ago

I've often felt that the web should work more like Git, so you can keep the content locally and just pull updates when you need.

[–] chromodynamic@piefed.social 6 points 1 month ago (1 children)

You can view and post in channels on other instances from your home instance without switching. For example, I'm commenting from piefed.social

[–] chromodynamic@piefed.social 17 points 1 month ago (3 children)

The term "social media" is already toxic. When I started using the Internet, socialising and media were two separate things. Conflating the two implies that every time we say something, we are publishing an article and should care about how many views and likes we get, instead of making a genuine attempt at connection. And it suggests that every reply should be some kind of review of the post it replies to.

In the days of forums, people would just post what came into mind. They were more honest because there was no number next to your comment rating how good it was.

[–] chromodynamic@piefed.social 21 points 1 month ago (2 children)

Browsers should be designed from the start for the benefit of the users. There are too many "features" that only benefit the server owners. It's been this way for a long time. Like the "Referer" header. Old as dirt, but how do I benefit from telling a server what page I was visiting beforehand?

[–] chromodynamic@piefed.social 55 points 1 month ago (5 children)

Client-side scripting is a hack. HTML didn't have all the tags people wanted or needed, so instead of carefully updating it to include new features, they demanded that browsers just execute arbitrary code on the user's computer, and with that comes security vulnerabilities, excessive bandwidth use and a barrier-to-entry that makes it difficult to develop new browsers, giving one company a near-monopoly.

[–] chromodynamic@piefed.social 8 points 1 month ago

Quite the opposite in fact. Microtransactions offer the promise of fun, but never deliver, because in order to incentivise users to purchase them, the player must feel like the game is 90% of the way to being fun and that tiny additional purchase will get it there.

It's like the cartoon image of the donkey rider holding a carrot on the end of a rod. The donkey keeps moving to try to get the carrot, but never quite reaches it.

view more: next ›