I've found that the only way to dual boot reliably is to have windows installed on a separate, dedicated drive, and to keep all drives used by Linux air-gapped from the windows drive. Fast start and hibernate must also be disabled within windows to prevent it from putting hardware in an undefined state.
That being said, I haven't actually found any regular use for the windows install in years. mostly just keep it around as a sort of backup failsafe, or just in case there is a game that refuses to work in Linux. 99 times out of 100 it simply just collects dust.
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.
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 don't really have an exact answer to your question, as I don't write Rust, and I've never used a Raspberry Pi for electronics, but I have some educated input:
There is a max7219-crate that used. But i am unsure about how to prepare the pins want to use.
Presumably, the crate just exposes pre-defined config objects that you call in your code.
Can Use any of the pins?
From what I recall, no, you can't use any of the pins on the Raspberry Pi as generic IO (all this information that you are looking for is in the datasheets of the devices that you are using) -- some pins are dedicated for power, etc.
Do have to set them to push-pull-output?
Generally speaking, yes, if you want to use a generic I/O as an output, then you must configure it as such.
I'm not sure that there is much for actual server side support for cross posting just yet, but there is a way, at least on the web UI: if you click the two overlapping squares under you post title, it'll open a new post with a link to the previous post and its content quoted underneath. It feels more like a work around for cross posting, but it does work.
TL;DR: There is no singular answer to your question, imo. Essentially just run the instance transparently, reliably, and actively, and it will be attractive to people.
I'm not sure that there is one "best way" to grow an instance. An instance is essentially the fundamental governing framework for how the users interract with each other. You structure the rules around how you believe the users on your instance should interact, and those who agree with those rules will be drawn to them. Ideally, for sustainable growth in an instance, you also need reliable server infrastructure -- the instance should be responsive, and have a reliable uptime. An instance's admins must also actively moderate content. An instance with inactive moderators is not sustainable, and will quickly delve into hosting unwanted content on the instance which is undesirable for users.
I did try that. Nothing appeared to happen, or change on my end; however, I now realize what the issue was. The first thought that I had, when I first noticed that Icon, was actually the exact same as that which you said; it just never occured to me that I could be on the same instance as the comments in question. So, when I tried clicking that icon, I was clicking it on a post that was from Lemmy.world -- the same instance that I am on. As such, I noticed no change in the displayed content -- the page would appear to load, but nothing would actually change. This is, of course, to be expected -- I just didn't put 2 and 2 together. I apologize if my inquiry seemed lazy, or thoughtless.
As an aside, In my defence, the UI also doesn't necessarily tell you what the icon does. If you hover your mouse over it, you will see the following:
Imo "link" isn't exactly descriptive, as to the button's purpose.
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.
Can you see if a moderator has removed comments from a thread? Can you see the content of the removed comments? Are moderators able to specify motive for the specific removal?
I just recently noticed the following button in the comment section:
Clicking it appears to make the comments look somewhat like what you see on Mastodon, but I'm a little unsure about it's exact format. Is it only showing parent comments? Is it showing parent and child comments all mixed together? If so, in what order? Is it in order of when the comment was added? If it does show child comments, is it possible to see that child's context?
I'm aware of Signal's "no log policy", but I'm wondering if such information is visible to the servers at all. I'm assuming "Sealed sender" is what is supposed to protect this information? If so, how effective is it?
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"?"
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 sm
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 overh
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.
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?
I can't seem to find any setting to enable automatic updates in Discover. Currently, I get a ping for available updates, nearly every day, and I then have to manually click "Update". I would much prefer for Flatpaks to automatically update themselves in the same way that Gnome Software does it.
I understand the negative sentiment that many have towards automatic updates, but, for Flatpaks, it's a risk that I am completely willing to take.
Update #1:
There appears to be a setting for toggling automatic updates in System Settings>Software Update>Update software>Automatically; however, it appears to be a known bug that this is currently broken with flatpak.