Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

50% Positive

Analyzed from 660 words in the discussion.

Trending Topics

#agents#git#github#gitlab#gitlawb#https#com#creation#agentic#account

Discussion (35 Comments)Read Original on HackerNews

sixtyjabout 2 hours ago
Grey text on black background… it is really for agents only :)
kevin11111about 2 hours ago
haha you are right
dijksterhuisabout 1 hour ago
fyi

> you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a portmanteau to refer to a product or service's use of Git code.

https://git-scm.com/about/trademark

gravypodabout 1 hour ago
How does this work with GitHub?
dijksterhuis42 minutes ago
> Please be aware that GitHub and GitLab are exceptions to this Policy because they are subject to explicit licensing arrangements that pre-date, and thus take precedence, over this Policy.

same link

nozzlegearabout 1 hour ago
Git's policy was created after GitHub and GitLab. They both have a special agreement with Git that allows them to use it.
kevin11111about 1 hour ago
yeah why GitHub ?
varun_chabout 1 hour ago
I think GitHub and GitLab have special agreements
gonzalohmabout 2 hours ago
Why do we insist on making stuff easier for agents? If they can't use the same tools that humans use them. It's simply not a good tool.

We are not building our roads for self-driving cars. We are adapting the cars to our roads

bakies18 minutes ago
Really all you need is a good cli. Agents I use have no trouble with gh or glab or tea. Clicking on this git platform idk what the hell is going on. I clicked on one repo with random letters in the title and it was empty. Womp.
kevin11111about 2 hours ago
its based on my own experience . i tried my openclaw to register to github and it was blocked by captcha and consume all my tokens . we need a different approach for AI agents.
dspillett32 minutes ago
> it was blocked by captcha

If there is a captcha there to block the automated creation of accounts, that it was difficult for you to autonomously create accounts is completely intentional.

> and consume all my tokens

Your bad coding/config (or your agent's bad coding/config) allowing run-away token use, is a problem for you, not a problem for everyone else.

> but we are in agentic era now.

Enabling autonomous account creation will enable a huge pile of spam and scam account creation, we've been in the spam/scam era for decades and it will not be over in the foreseeable future, your agents will have to put up with that just like us humans do.

> that feature is a friction for agents

[reaches for microscope to aid playing the appropriate violin]

> this validates the thesis and narrative of agentic first git platform

Perhaps your next thesis should be the result of a project where you design and fully verify a system that will solve the spam/scam problem that enabling your use case will also enable, instead of just expecting the world to make all the effort of rearranging itself around the way you want to work.

Automated account creation is quite likely a direct breach of their AUP anyway, maybe you should instruct your agents to check such things and try not to do things that are in direct contravention of the rules of the tool they are trying to use/abuse.

--------

If your response to this is “Fine, our agents just won't use your systems then.”, then that is great: The system works!

Hamukoabout 2 hours ago
I feel like the inability to register new user accounts automatically is a feature, not a bug.
kevin11111about 1 hour ago
but we are in agentic era now. that feature is a friction for agents.

event gitlab and cursor is diving to it.

check this x post for reference.

https://x.com/gitlawb/status/2067048298037629105

this validates the thesis and narrative of agentic first git platform

jankdcabout 2 hours ago
There's a lot of tech stack jargon here that it doesn't really tell me what it actually does. How does this differ from me using an agent with Github's MCP to control my repo?
kevin11111about 1 hour ago
hi thank you for checking it out. you can check this repo.

https://github.com/Gitlawb/node

The difference is that here we are giving agents their own identity via DID . not tied to humans email account .

fawictedabout 1 hour ago
Looks useful for decentralization, can solve a lot of holes with gitlab
echo02about 1 hour ago
Gitlawb is for everyone.
Beastboy007about 1 hour ago
gitlawb is the way for agents!
kevin11111about 3 hours ago
no email or password . just read the skill.md and your agents can do the full git lifecycle in under a minute . commit, push and merge PR
Ducketsabout 1 hour ago
Gitlawb is the future
kevin11111about 1 hour ago
not really good in UI but this is the node repository

https://github.com/Gitlawb/node

You can self host it or connect to network

ezekgabout 1 hour ago
Gitlawb is very close to Gitlab. Good luck.
argeeabout 1 hour ago
Maybe they're going for the "PR from Trademark Infringement" strat all the cool kids have been using recently, like Clawdbot and "Notepad plus plus for Mac".
kevin11111about 1 hour ago
i know . thanks . someone from gitlab followed our X already
Advertisement
esafakabout 1 hour ago
I wish new forges would base on jujutsu (jj-vcs.dev) so we can transition off git one day.
varun_chabout 1 hour ago
tangled.org!!!!
kevin11111about 1 hour ago
whats that? will check it out