Skip Navigation

  • I no longer look forward to updates.[...]It seems to me that some software is actually getting worse, and that this is a more recent trend.[...]Why does this happen? I don't know, but my own bias suggests that it's because there's less focus on regression testing. Many of the problems I see look like regression bugs to me. A good engineering team could have caught them with automated regression tests, but these days, it seems as though many teams rely on releasing often and then letting users do the testing.

    The problem with that approach, however, is that if you don't have good automated tests, fixing one regression may resurrect another.

    Every time I see a new update, I think: "I wonder what will break after this update" and postpone them as much as I can. Software updates shouldn't cause anxiety. But they do these days...

  • I think this may also be a problem with malicious clients. Currently the user enters the username and password via the client's login dialog. It's an effective way to collect credentials.

  • I think you have a better chance if your instance focuses on a topic instead of being general purpose. That's the reason I chose programming.dev. All communities there are related to programming so when I sort by "local" I see something interesting even though I haven't subscribed to that community. And that increases my interaction with those communities.

  • There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.-- Leon Bambrick

  • That may be due to "the Hacker News hug". This link had a high score in HN a few hours ago. High traffic may have caused scalability problems.

  • Ok, maybe I misunderstood your question. I though you were proposing # instead of $ sudo and I meant to say that being explicit is better.

  • That sounds cool. Thanks for the recommendation.

  • What about the packages that are not available in flatpak? I assume there must be some packages that are only available in certain corners of the internet?

  • Thanks

  • Are there any other distros that are flatpak-only?

  • I don't work much with Linux systems these days, but I would vote for $ sudo over #. Two reasons:

    1. It's easy to overlook the prompt. That part is basically "some characters before the actual command", so I don't normally pay attention to it.
    2. # is also used for comments. I think it would be confusing to use the same character for two wildly different things.
  • It doesn't look very good, no. It would be good to bring Lemmy to OAut2.1 where the self-contained token with a sensible lifetime is passed in the Authentication header. Currently it's either passed in the URL (GET) or in the model (PUT/POST).

    I have some OAuth experience, but I'm not a Rust developer. So, I thought of offering some help regarding design and testing of an OAuth mechanism, but since I cannot really contribute to implementation, that may not be that much of a help. Also, this kind of a change will break at least some of the existing clients. I don't know if the core team would be willing to make such a change.

  • Would love to see a browser based implementation of this.

  • Unflushable Cache

    [...] Other implementations, such as hand cranks in memory caches or even caches provided by mainstream frameworks will not expose any cache management tools. This leaves ops with the only option, to restart the service to flush the memory. (Or worse, know enough about the cache implementation to find it’s location on file system and clear it out manually.)

    This is a mistake I have made. It's easy to overlook during development but difficult to handle afterwards if restart is not trivial.

  • Fixed, thanks

  • Thanks. I didn't know that when one adds an image it would override the URL. Even though the post contains the URL, clicking on the title only shows the image. I included the URL in the post body, but it's not as visible, unfortunately.