Kalcifer

joined 3 years ago
 

As far as I understand it, Forgejo is a soft-fork of Gitea, and, as far as I am aware, Gitea includes both the backend and frontend. But then I came across Codeberg, which appears to state:

Self-Hosting Forgejo, the software that powers Codeberg.

This makes it sound like Forgejo is the backend, and Codeberg is the frontend, but I'm not 100% sure. If so, did Forgejo separate Gitea's UI, and just soft-fork the backend?

[–] Kalcifer@lemmy.world 1 points 2 years ago

Apologies, I did not.

[–] Kalcifer@lemmy.world 1 points 2 years ago* (last edited 2 years ago)

Be that as it may, the comment is rather misonformative, as it is currently written. It is evident that the main topic of conversation here is Hexbear; therefore, people scrolling through the comments are going to be expecting that all comments will be talking about Hexbear. The posted quote could very easily be interpreted as a quote from Hexbear, given the context, if read in passing by someone who doesn't feel motivated enough to follow a link.

[–] Kalcifer@lemmy.world 4 points 2 years ago (2 children)

You do realize that you don't need to join Lemmy.world, right? There's plenty of other instances with different moderation policies that might suit you, or you could just make your own instance. That's kind of the whole point of the fediverse. The reason why there's so much contention around this post is because the people who have accounts here are somewhat stuck until account migration is added.

[–] Kalcifer@lemmy.world 0 points 2 years ago (3 children)

Your comment's intent is rather dubious -- why post a quote from Lemmygrad, when the original post was talking about Hexbear? I encourage you to state that your quote is from Lemmygrad within the comment itself, instead of hiding it behind a link.

 

The most common answer I see is something along the lines of "it's the equivalent of liking a post on twitter". It seems that this is not the case, as the Mastodon devs seem rather adamant that they don't want "likes" in Mastodon. Perhaps it's a method of saving posts? Well, that doesn't make sense either, since there is already the ability to "Bookmark" a post to save it.

It really just seems like a "Favorite" is just a bookmark that tells the poster, and the public that you bookmarked the post. And even if this was the reasoning -- which is baffling enough as it is -- it wouldn't make sense since the whole point of boosting something is to tell the public that you like a post.

It really seems like the "Favorite" button has no actual unique purpose. In my honest opinion, Mastodon should just federate "Likes" like normal, and be done with it.

 

cross-posted from: https://lemmy.world/post/2121242

Would I have to do anything on my end, or would everything be set up automatically when the update is pushed?

 

I'm not sure if it is entirely accurate to compare them in this way, as "Matrix" refers to simply the protocol, whereas "Signal" could refer to the applications, server, and protocol. That being said, is there any fundamental difference in how the Matrix ecosystem of federated servers, and independently developed applications compares to that of Signal that would make it less secure, overall, to use?

The most obvious security vulnerability that I can think of is that the person you are communicating with (or, conceivably, oneself, as well) is using an insecure/compromised application that may be leaking information. I would assume that the underlying encryption of the data is rather trustworthy, and the added censorship resistance of federating the servers is a big plus. However, I do wonder if there are any issues with extra metadata generation, or usage tracking that could be seen as an opsec vulnerability for an individual. Signal, somewhat famously, when subpoenaed to hand over data, can only hand over the date that the account was created, and the last time it was used. What would happen if the authorities go after a Matrix user? What information about that user would they be able to gather?

 

When I want to add a hole feature, I need to first sketch and constrain a circle where the hole is supposed to be. This would make a bit more sense if the hole actually followed the constraints of the circle, but it doesn't -- I could constrain the sketch of the circle to be one radius, and then, at the same time, specify that the hole be a completely different radius. I feel like it would make much more sense if the hole actually followed the dimensions of the sketch of the circle. If the sketch is just used for the placement of the hole, then it should be enough to simply place a point (which does not currently work -- I must sketch a circle).


Edit 1: It looks like there is an open issue for this on GitHub.

 

I have the following:

I want the center rectangle to be concentric with the outer rectangle (the separation of each edge should be equal). What's the best way to do this?