-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Teddit.net[0] solves a lot of these problems and paired with Redirector[1], it's a transparent switch out.
https://github.com/teddit-net/teddit
JIRA is unrivalled in my opinion. Just loaded up a random ticket page with one comment and no attachments.
- 105 requests
- 3.9MB transferred
- 13.9MB resources
- 32.57s load time
Here's a nice repo of other examples: https://github.com/dominictarr/your-web-app-is-bloated
Originally it was just a fullscreen nag div on top of the already rendered content, so if you can delete elements, it should work for viewing or you can use something like Nitter.net
Nitter.net[0] solves a lot of these problems and paired with Redirector[1], it's a transparent switch out.
There's an expired cert issue 3 days ago, but there are other instances[2]
https://github.com/zedeus/nitter
https://addons.mozilla.org/en-US/firefox/addon/redirector/
https://github.com/zedeus/nitter/wiki/Instances
GitLab Product Design Manager here Thanks for your feedback!
You bring up quite a few great points. We have worked hard on bringing every tool from the DevOps lifecycle into our platform, and I agree with you that quite a few areas have become overwhelming, especially for new users or people who don't use our entire set of features.
We are actively working on refining that, but as you can imagine, that's no easy feat, as we have a vast variety of project types, workflows, use cases, user types, etc...
One of the most problematic areas, as you perfectly mentioned, is the left sidebar. We already enable project administrators to remove items from there by going to Settings -> General -> Visibility, project features, permissions, and then toggling off the areas you would like to remove. However, this is a project setting, not per user.
At the same time, we also work on making that left sidebar better for everyone, in multiple smaller iterations. As first step, we are making some small changes to the visual design (https://gitlab.com/gitlab-org/gitlab/-/issues/322680) and make the navigation easier to understand (https://gitlab.com/gitlab-org/gitlab/-/issues/322687). We are also aware that our left sidebar has become too crowded with too many top-level/sub-level items, and we are validating an idea that would be the first step for us to get out of this (https://gitlab.com/gitlab-org/ux-research/-/issues/1421). There are already a few follow-up ideas (e.g. grouping items into larger groups or pinning most important items per user), but they are a bit further away.
I hope that gives you a better understanding how our UX team at GitLab thinks about this. Let me know if you have any other feedback or ideas
GitLab Product Design Manager here Thanks for your feedback!
You bring up quite a few great points. We have worked hard on bringing every tool from the DevOps lifecycle into our platform, and I agree with you that quite a few areas have become overwhelming, especially for new users or people who don't use our entire set of features.
We are actively working on refining that, but as you can imagine, that's no easy feat, as we have a vast variety of project types, workflows, use cases, user types, etc...
One of the most problematic areas, as you perfectly mentioned, is the left sidebar. We already enable project administrators to remove items from there by going to Settings -> General -> Visibility, project features, permissions, and then toggling off the areas you would like to remove. However, this is a project setting, not per user.
At the same time, we also work on making that left sidebar better for everyone, in multiple smaller iterations. As first step, we are making some small changes to the visual design (https://gitlab.com/gitlab-org/gitlab/-/issues/322680) and make the navigation easier to understand (https://gitlab.com/gitlab-org/gitlab/-/issues/322687). We are also aware that our left sidebar has become too crowded with too many top-level/sub-level items, and we are validating an idea that would be the first step for us to get out of this (https://gitlab.com/gitlab-org/ux-research/-/issues/1421). There are already a few follow-up ideas (e.g. grouping items into larger groups or pinning most important items per user), but they are a bit further away.
I hope that gives you a better understanding how our UX team at GitLab thinks about this. Let me know if you have any other feedback or ideas