4 ms·

strong agree, though with the caveat that it's "bad" for my tastes and priorities, but is clearly ok for other folks. it feels all too common for folks to rage

strong agree, though with the caveat that it's "bad" for my tastes and priorities, but is clearly ok for other folks. it feels all too common for folks to rage against bloaty interfaces (i agree, they're terrible!) but swing wildly back towards clunky browser-default randomness. you can have a consistent, polished interface without javascript and tons of images! one thing w/ sourcehut that i find adds confusion is their choice to make their various services (source vs tickets vs mailing lists) completely separate apps. start on this page: https://sr.ht/~martijnbraam/photoflow/ https://sr.ht/~martijnbraam/photoflow/ when you click on the "source" tab what do you expect will happen? i expect i'll go to a page with a source tree, listing files and directories. i also expect that i'll now be on the "source" tab at the new page, and will have the option to click back to the "summary" tab or any of the others that i currently see. instead, you're taken to basically the same exact summary page (displaying README content) but with some git commit info on top. the highlighted tab is now... SUMMARY, AGAIN and there's a completely different tab set available to you. there is no way to click anywhere to get back to the previous version of the summary page and explore that tab group further. i'm sure this makes sense to some folks (and they'll explain why i'm wrong below), but to me it feels like a cohesive user experience is not being prioritized here, and that's something i value ¯\_(ツ)_/¯

gspr 4y ago
This is the one thing I, too, struggle with with sr.ht. I keep on using it, but I can't wrap my head around why this is supposed to be a good way to do it.
olalonde 4y ago
The repository's description also changes for no apparent reason ("Photo management solution" vs "A web picture gallery").
- mariusor 4y ago
  The link parent posted is not of the repository but of the project. Sourcehut doesn't use the 1 to 1 relationship between projects and repositories, wiki, and issue tracker that the other source forges employ. A sourcehut project can have as many as them as there are required. Therefore the Source tab takes you to the main git/HG repo that you have added for your project. That's also the reason why the descriptions are different, one is of the project, the other is of the repository. It's only confusing if you dismiss everything that's not a clone of github without investing the little time it takes to learn about the differences.

gspr 4y ago

This is the one thing I, too, struggle with with sr.ht. I keep on using it, but I can't wrap my head around why this is supposed to be a good way to do it.

olalonde 4y ago

The repository's description also changes for no apparent reason ("Photo management solution" vs "A web picture gallery").

mariusor 4y ago
The link parent posted is not of the repository but of the project. Sourcehut doesn't use the 1 to 1 relationship between projects and repositories, wiki, and issue tracker that the other source forges employ. A sourcehut project can have as many as them as there are required. Therefore the Source tab takes you to the main git/HG repo that you have added for your project. That's also the reason why the descriptions are different, one is of the project, the other is of the repository. It's only confusing if you dismiss everything that's not a clone of github without investing the little time it takes to learn about the differences.