Kalcifer

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

As shown below, it appears that all Firefox tabs are just named "Firefox" within the volume mixer. This doesn't exactly make differentiating them very easy. Is it possible to make the volume mixer show the names of the tabs instead? If not, is there any feature in the works for this that anyone may be aware of?

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?

I'm not sure how practical/sustainable of a project this would be, but I feel that it could possibly be a useful project in the future if instances begin to purge old content due to storage constaints. The archiving service could store all the data using Object storage to archive it in read only. That way, at least people can still view old content in the possible scenario of rampant data loss across the Fediverse.

On Reddit, one frequently runs into posts that are archived, and thus the user cannot interract with them anymore -- motive is stated here. I'm curious if Lemmy would ever do the same.

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

From my experience, it seems that any service that offers cryptocurrency payments seems to always set them up as a one time purchase that you manually must renew periodically. Is there any standard that exists, or is in the works that supports recurring payments to a service directly from a wallet?

I'm trying to find a good method of making periodic, incremental backups. I assume that the most minimal approach would be to have a Cronjob run rsync periodically, but I'm curious what other solutions may exist.

I'm interested in both command-line, and GUI solutions.

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?

It seems that most information that I can find on the subject is about a year old, so I am wondering if anyone has any up-to-date info.

I apologize in advance if this is the wrong community for this post. If so, please point me in the right direction of where I should post this.

I'm thinking of trying out KeePassXC, and, when creating a new database, I came across the following settings:

Some of this is somewhat self explanatory to me ("Encryption Algorithm", and "Key Derivation Function"), but some of it not so much -- namely, "Transform Rounds" (I'm assuming that "Memory Usage", and "Parallelism" are more specific, not to the database on the whole, but, instead, to the decryption itself within the app, or, maybe, even just for the benchmark). What exactly is "Transform Rounds"? Does it mean that the passwords are encrypted over, and over again, in attempt to protect against dictionary attacks? I haven't been able to find any concrete information.

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 been trying to understand how the caching of content from other Lemmy instances works. From what I have gathered, the local Lemmy instance will automatically download and store posts made to any communities that are followed by users on the local instance.

To me, this seems somewhat unsustainable in the long term - I am aware of the fact that it's only storing the text of the posts, and not any media. I'm curious if it's possible to configure the local instance to only cache the stored data for a certain amount of time (it might be better to just periodically purge the entire cache with a cronjob, or something); however, the data that I would like to store permanently is posts to any other community by users on the local instance, as well as posts made to communities on the instance (I have a suspicion that the communites data is permanently stored by default).