Just your normal everyday casual software dev. Nothing to see here.

People can share differing opinions without immediately being on the reverse side. Avoid looking at things as black and white. You can like both waffles and pancakes, just like you can hate both waffles and pancakes.

  • 0 Posts
  • 360 Comments
Joined 2 years ago
cake
Cake day: August 15th, 2023

help-circle




  • I know they don’t wanna rock the boat after the ridicule they had after last review updates but, their review comments and forums could really use a little more tender love and care. Especially in the toxicity department. I know that a big portion of responsibility is publisher but, there is a lot of easily identifiable toxicity that if they did more moderation on (or even read existing reports) would be resolved really fast and make both areas a lot better for the user to enter. Like I personally don’t even allow comments on my reviews anymore because it very rarely allows for an actual constructive discussion, usually it devolves into toxicity from someone.


  • Honestly, this is a really innovative project. I wish it came in an extension because I feel that is likely your biggest bottleneck for getting people to try it. I don’t think many are going to build a browser from source & then port all their stuff over strictly for the integration. Plus it looks like a primary advertisement for it is that integration, but it also disables a lot of the QoL features that FF has that some don’t have any problem with. Like the fact that Sync is removed as a whole is a major dealbreaker for me, as I do like the feature and I am not concerned about the privacy aspects of having it on.

    If an extension version ever releases for the lemmy integration though, I would for sure be looking at that!



  • I think my only real complaint about the deployment of this, is from a security standpoint. The password is hardcoded as “changeme” for the GitLab Runner container. which when run from an automated script like this the script itself doesn’t make the user aware of that. Like the script itself mentions that you should move credentials.txt but it never makes you aware of the hardcoded password.

    it would be nice if it prompted for a password, or used a randomly generated one instead of that hardcode




  • I think everyone’s basically hit my complaints with Ubuntu. It’s a very bloated OS with a hard dedication into snaps, which I dislike(but I also hate flatpak so yea)

    Being said if this is your first Linux distribution, you can’t go wrong with Ubuntu. It’s a very beginner-friendly distro. The only other one that I would have recommended aside from that would have probably been Mint. But Ubuntu is going to have quite a bit more tutorials and guides for it.


  • Just to make sure we are on the same page then, cause I don’t see the issue with my post.

    I am using the term “Graceful Degradation” which is meant as a fault tolerance for tech stacks to allow for a critical component to be removed.

    This critical component people are talking about is Javascript which is used for all dynamically loaded content, and used for fallover protection so one service going down doesn’t make it so the entire page goes down (also an example of fault tolerance).

    The proposed solution given would remove that fault tolerance for the reasons I provided in the original reply, while degrading the users experience due to increased page load time (users reloading the page inconsistently vs consistently to get new information) and increasing maintenance costs and overhead on the provider.

    Additionally, the new processing system that you mentioned already exists generally doesn’t, because they(websites) mostly use a dynamic load style nowadays, not a static(as in the client doesn’t change it) page, which is what this type of system would require.

    note: edits were for phrasing, and a typo



  • my only issue with this ideology(the require page load) is, this setup would essentially require a whole new processing system to handle, as instead of it being sent via events, it would need to be rendered and sent server side. This also forces the server to load everything at once instead of dynamically like how it currently does, which will increase strain/load on the server node that is displaying the web page, while also removing the potential of service isolation between the parts of the web page meaning if one component goes down(such as chat history), the entire page handler goes down, while also decreasing page response and load times. That’s the downside of those old legacy style pages. They are a pain in the ass to maintain, run slower and don’t have much fallover ability.

    It’s basically asking the provider to spend more to: make the service slower, remove features from the site (both information and functionality wise) and have a more complex setup when scaling, to increase compatibility for a minor portion of the current machines and users out there.

    this is of course also ignoring the increase request load as you are now having to resend entire webpages to get data instead of just messages/updates too.