lemmydividebyzero

joined 11 months ago
[–] lemmydividebyzero@reddthat.com 8 points 4 months ago

not interested in that.

[–] lemmydividebyzero@reddthat.com 10 points 4 months ago (5 children)

Pretty much all my experiences with that instance and similar ones have been disgusting.

Pushing people who post burning flags of a country and posts about it to be fully wiped out are accepted... Criticism regarding this gets your comment remove and a ban from the community.

I don't need that again. Where can I block this pseudo-left pro-authoritarian instance in Voyager?

[–] lemmydividebyzero@reddthat.com 30 points 4 months ago

Is it that hard to understand? They are barely producing enough to keep up the war in Ukraine, but much compared to some European countries. When the war "ends" end they continue with their war economy for a few years, they are still producing a lot more than the European countries. Russia can continue with their strategy, but some Nato states need to change theirs.

[–] lemmydividebyzero@reddthat.com 6 points 4 months ago

I'm not sure what you are trying to say.

My point was from the beginning that I don't want to create 2 accounts when I report a bug a bug on Forgejo instance 1 and on instance 2.

The suggestion whether I have heard about git does not solve anything about that...

Some one else here mentioned that it's possible to login with Mastodon on each of the instance, which is the correct direction (allows to report a bug on both instances via an external account). Disadvantage is still: My 2 bug reports are not linked to each other, because there is no shared Forgejo profile, which would actually require something like federation.

[–] lemmydividebyzero@reddthat.com 1 points 4 months ago* (last edited 4 months ago)

FYI Forgejo supports mastodon login

That's interesting. Did not even know, Mastodon supported doing something like this...

There is still a difference: There is no profile in the end. I might create 2 bug reports, bit they won't be linked to each other.

[–] lemmydividebyzero@reddthat.com 3 points 4 months ago (1 children)

I agree that it's already kind of decentralized, so I also added the word "federated" to my original post.

[–] lemmydividebyzero@reddthat.com 3 points 4 months ago (1 children)

Yeah, that was my point in the first comment... But not only that...

The development with multiple people is decentralized, yes...

But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don't have an account on each of these... Try pushing code or making a pull request and see how it fails, because you are not authenticated...

[–] lemmydividebyzero@reddthat.com 3 points 4 months ago

I did not mean decentralized hosting of the projects (e.g. your project will be on all instances).

I meant decentralized account usage (e.g. you can use your example.com forgejo account to create an issue on otherexample.org)... Just like Lemmy... I could use my reddthat.com lemmy account to create a post on your instance lemmy.world without having to register there.

[–] lemmydividebyzero@reddthat.com 8 points 4 months ago (3 children)

There is no command git issue create [hostname] [title] [description] and if there was such a command, it'd require authentication on the specific instance to prevent spam.

You still need to create an account on each Forgejo instance to report a bug there...

And even, if you commit code or make a pull request... Git might be decentralized (you can develop with your friend independently from each other and merge it), but try to commit code to a GitHub project, GitLab instance or Forgejo instance without having an account there to authenticate yourself... It won't work.

[–] lemmydividebyzero@reddthat.com 45 points 4 months ago* (last edited 4 months ago) (34 children)

We need something like Forgejo, but decentralized and federated, like Lemmy. I don't want to create a new account for every Forgejo instance, just to be able to report a bug...

Edit: Added "and federated"

view more: ‹ prev next ›