Kalcifer

1. Show the timer for all the succeeding stacked pixels. Currently, you can only see the timer for the first pixel. I propose that the timer should be shown for all of the pixels in the stack, and not only the first.
2. A neat feature that r/place had was that you could click on a pixel and see the username of the account that placed it. I propose the same feature.
3. Consider creating a permanent canvas. It could be neat to see how a large, permanent canvas evolves over a long period of time.

If any of these suggestions require the modification of underlying code, and are not simple config changes, then I will suggest them upstream -- please let me know.

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?

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.

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

This is, of course, assuming that the instance is not hosted on the same network that the device your account is using is accessing it from.

EDIT (2023-07-31T22:18:52Z): I have realized that I was not clear in my original intent for this post -- it could be interepereted to mean that I am asking whether or not you could access, for example, Lemmy through the Tor browser. This is not what I meant. What I was more alluding to was if it were possible to create a sort of "hidden fediverse" that was separate from the fediverse over the clearnet. There exitsts, already, Dark Web forums, like Dread, and I wonder if those would benefit more from being federated -- Lemmy seems like a good candidate for this.

Title changes: Added "More specifically, could one make a sort of "Hidden Fediverse"?"

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

It seems that self hosting, for oneself, a federated service, like Lemmy, would only serve to increase the traffic in the network, and not actually serve the purpose of load balancing between servers.

As far as I understand it, the way federation is supposed to work is that the servers cache all the content locally to then serve to the people that are registered to that server. In doing so, the servers only have to transmit a minimal amount of data between themselves which lowers the overhead for small servers -- this then means that a small server doesn't get overwhelmed by a ton of people requesting from it. Now, if, instead, you have everyone self hosting their own server, you go right back to having everyone sending a ton of requests to small servers, thereby overwhelming them. It seems that it's really only beneficial to the network if you have, say, hundreds of medium sized servers instead of, say, thousands, of very small servers. While there is the resilience factor, the overhead of the network would be rather overwhelming.

Perhaps one possibility of fixing this is to use some form of load balancer like IPFS to distribute the requests more evenly, but I am no where even remotely close to being knowledgeable enough in that to say anything definitively.

It seems that self hosting, for oneself, a federated service, like Lemmy, would only serve to increase the traffic in the network, and not actually serve the purpose of load balancing between servers.

As far as I understand it, the way federation is supposed to work is that the servers cache all the content locally to then serve to the people that are registered to that server. In doing so, the servers only have to transmit a minimal amount of data between themselves which lowers the overhead for small servers -- this then means that a small server doesn't get overwhelmed by a ton of people requesting from it. Now, if, instead, you have everyone self hosting their own server, you go right back to having everyone sending a ton of requests to small servers, thereby overwhelming them. It seems that it's really only beneficial to the network if you have, say, hundreds of medium sized servers instead of, say, thousands, of very small servers. While there is the resilience factor, the overhead of the network would be rather overwhelming.

Perhaps one possibility of fixing this is to use some form of load balancer like IPFS to distribute the requests more evenly, but I am no where even remotely close to being knowledgeable enough in that to say anything definitively.

I can't really find any information on where one would submit a feature request for KDE products -- it seems wrong, to me, to submit them to the bugtracker.

I found this Reddit thread that seems to say that there isn't one, but that post is, as of writing this, 6 years old, so I'm wondering if anything has changed since then?

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?

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 have Nextcloud installed as a snap. I would like to back it up to a folder on a separate drive within the server. Nextcloud appears to have an official backup app, which I have installed on the Nextcloud instance.

Is it possible to connect a folder on a separate drive to Nextcloud running as a snap? What permissions should such a folder have?

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