this post was submitted on 24 Jan 2025
31 points (100.0% liked)

Programming

17975 readers
289 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
31
sourcehut is super confusing (self.programming)
submitted 5 days ago by verstra to c/programming
17 comments fedilink hide all child comments
 

Anyone using soucehut (sr.ht)? Can you please explain to me how you navigate the site?

I really like the minimalist approach and extremely fast website UI, but I just cannot navigate the site.

If I'm looking at source of a repo on https://git.sr.ht/ and want to see open tickets, how do I navigate to https://todo.sr.ht/ ? If I click on "todo" at the top, it takes me to my todo lists, not todo of the project I was just looking at.

all 18 comments
sorted by: hot top controversial new old
[–] [email protected] 9 points 5 days ago* (last edited 5 days ago) (1 children)

I agree, it's a great UI in terms of speed and no JS, but it's not super intuitive and not helped by the way it's been split into modules.

Basically, each subdomain (git.sr.ht, todo.sr.ht etc) doesn't link to the others - the only one that links everywhere is the root "sr.ht". You can think of sr.ht as a "hub" that links to the others. So - to take an example:

  • You can open "tickets" (todo.sr.ht) from https://sr.ht/~delthas/senpai/
  • But - if you click on "source" (git.sr.ht), the references to the other pages anymore (including back to the hub)

So, in your case, if you replace git.sr.ht with just sr.ht in the URL, it should take you back to the "hub" for that project. Then, if the tickets feature is enabled, you should see a link to "tickets" there.

[–] verstra 16 points 5 days ago

Well, editing urls is not a convenient way of navigating a website.

I wish there would be at least a link from each of the modules back to the "hub" for that project.

[–] FizzyOrange 6 points 5 days ago* (last edited 5 days ago) (3 children)

Yeah I just took a look at it. First thing I did was click on the "source" tab on a repo. That actually makes the source tab disappear? Clearly not designed by anyone who has any experience designing sane UI.

I think Gitlab and Forgejo are better options, and not run by a creep. Forgejo is similarly fast and actually has a sane UI. The tabs don't disappear!

[–] [email protected] 5 points 5 days ago (1 children)

What did DeVault do?

[–] [email protected] 9 points 5 days ago (2 children)
[–] cd_slash_rmrf 3 points 4 days ago* (last edited 4 days ago)

was this taken down? website connection times out, and is "excluded" from the way back machine

edit: found it archived from here (I'm not really sure what to think about this response article tbh) https://blenderdumbass.org/articles/Is_The_DeVault_Report_a_Spiteful_Metajoke

archived report: https://dmpwn.info/

[–] [email protected] 2 points 5 days ago

Well, that was disappointing. I guess that explains why he deleted his Mastadon account recently.

[–] [email protected] 1 points 5 days ago* (last edited 5 days ago) (1 children)

Forgejo

I believe https://codeberg.org/ is a hosted Forgejo instance. It has a more familiar UI, similar to GitHub.

Although, they have restrictions on the types of projects they're willing to host.

[–] starshipwinepineapple 2 points 2 days ago

Notably codeberg is not a corporate owned like github/gitlab, and you can become a voting member of the nonprofit through donations. Pretty neat imo. I made an account there last year but just got around to creating a repo there for a smaller project. It was straightforward and familiar.

One thing that's holding me back though is the CI is in closed testing but you can request access.

[–] [email protected] 3 points 5 days ago

https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3CCAJ8xHvVg2nRrystBjv8rLPCdMRijuaHQb8DsopiBtrW=1oF+BQ@mail.gmail.com%3E

https://todo.sr.ht/~sircmpwn/hub.sr.ht/15

This. It is a problem and it is prioritized. —Drew DeVault, 3 years ago

As a fellow sr.ht fan, I strongly sympathize.

[–] [email protected] 4 points 5 days ago

to connect sub-functionalities (like git and todos) i think one needs a top-level project. from the project you can navigate to all the connected apps/functionalites (or however they are called on sr.ht)

[–] [email protected] 3 points 5 days ago* (last edited 5 days ago) (2 children)

I don't navigate the site at all.

I just use the commandline to push commits to repos.

For creating a new repo on sr.ht I have written a script that uses the GraphQL API (which is horribly documented in my opinion and required days of trial and error). It is not meant for general users and is specific to my needs, but anyone who is interesred can find it linked below.

If you want to use it, you have to run git init and do a commit first. Everything else should be explained in the help. The script does some other stuff that I wanted when migrating all my projects from github, which you should be able to easily modify.

https://clbin.com/EII4R

(unlicense)

[–] [email protected] 6 points 5 days ago (1 children)

Create a new repo locally.

git init
git add .
git commit -m "Initial commit"

Then to create a new remote repo, you can do this.

git remote add origin [email protected]:~user/my-new-repo
git push origin main

You'll get a message that says.

remote: 
remote:         NOTICE
remote: 
remote:         You have pushed to a repository which did not exist. ~user/my-new-repo
remote:         has been created automatically. You can re-configure or delete this
remote:         repository at the following URL:
remote: 
remote:         https://git.sr.ht/~user/my-new-repo/settings/info
[–] [email protected] 1 points 4 days ago* (last edited 4 days ago)

You forgot a small detail.

Afaik you can not change repo visibility this way (without using the web UI or the GraphQL API). So if the goal is to avoid the web UI you'd have to add a step (which you can read up on in the script I shared).

Same for the repo description (but maybe there is a git native way, idk).

Great write up otherwise, thank you!

[–] [email protected] 2 points 5 days ago (1 children)

but the question is about navigating to tickets

[–] [email protected] 0 points 5 days ago (1 children)

I would have known that if I had the attention span to read all that text from OP

[–] [email protected] 2 points 5 days ago

have you tried bionic reader?