I say "I'm not making yet another account to report this bug". Tangled is trying to solve that problem but we'll see.

myaccountonhn 2 hours ago | parent | next [-]

That's the beauty of email-based approaches. You can just clone, do your changes and `git send-email`. Done.

I think it would've been far easier to build a decent GUI around that flow, with some email integration + a patch preview tool, rather than adding activitypub, but oh well.

▲

some_furry 2 hours ago | parent | prev | next [-]

I literally logged into codeberg using my GitHub account. It's two clicks of the mouse to do this.

▲

fsflover 2 hours ago | parent | prev | next [-]

https://news.ycombinator.com/item?id=33730417

▲

3 hours ago | parent | prev | next [-]

[deleted]

▲

phoronixrly 3 hours ago | parent | prev [-]

[flagged]

▲

crimsoneer 2 hours ago | parent | next [-]

Wait, how is Tangled VC controlled? As far as I Know, it's actually decentralised properly on atproto, with barely any bluesky dependencies?

	▲	phoronixrly 2 hours ago \| parent [-]
		Is it not backed by a registered in Finland limited liability company? Haven't they acquired pre-seed funding by Antler, a VC company?

▲

hinkley 3 hours ago | parent | prev [-]

So how many bugs did you file on sourceforge when GitHub hadn’t quite killed it off?

	▲	cyberax 2 hours ago \| parent \| next [-]
		I used to submit quite a few back in the day. How many projects are still actively maintained on Sourceforge? The last time I needed to go there was to get the GPC (General Polygon Clipper) library with the last modification in 2014.
	▲	phoronixrly 3 hours ago \| parent \| prev [-]
		Maybe I wasn't quite clear. As an open-source author, bug reports are what makes open-source feel like a job. This is because Github has created a sense of entitlement that an open-source project is supposed to take bug reports. That its authors are its 'maintainers' and are expected to fix them. No. You are the person with an issue. You have all the means to fix the issue -- the source code has been shared with you. Now go ahead and fix your bug yourself. Then share the source code with your users as per its license. Notice how I don't even care much for 'pull requests'. Another detrimental notion started with Github -- that the authors of an open-source project are expected to review change requests and merge them. Guy, open-source licenses do not require you to share the derived code with upstream. They require you to share it with your users. I, as the original author, mostly don't care as the original code I wrote works for me. Yes, sending fixes back upstream is a courtesy and a way to thank the original authors. However it is neither required, nor one must expect that the fixes will be accepted or even looked at at all.