11·
18 hours agoNot just an engineer thing though. Everyone finds it obnoxious.
- 0 Posts
- 7 Comments
Joined 2 months ago
Cake day: August 28th, 2024
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
0·18 hours agoEnceladus, a moon of Saturn is actually mostly water, but salt has been found in volcanic emissions ejected into space.
That said it’s not impossible that conditions exist somewhere in the universe where you have H2O and no NaCl since that is the salt we usually mean when we talk about salt water. Unfortunately it is not the only thing found to be mixing with water as on Jupiter, liquid water does exist but it mixes with amonia.
that would be because electric eels are fish, not eels.
On my phone but see phylogeny https://en.wikipedia.org/wiki/Electric_eel
3·12 days agoYeah. Komga + Komf seems like overkill for your use case too. Komf would definitely get around the limitation of english editions only.
Readarr can track comics/manga too but unless you’re interested in only indexing by author I have found it less than ideal.
Tachidesk or sorayomi or whatever they are calling it now may be an option? Like the other tools I have mentioned it’s primary function is for piracy but I don’t see why you couldn’t just add sources and add series to library without downloading. Again would need dummy files to track owned vs unowned.
I use Komga + Komf for digitals but seems like you could do simply with mylar without a download agent. Might need to create a dummy file for each issue you own to change status to owned. Been ages since I have used so not sure.
12·1 month agoWow is right. That man probably voided his warranty if he blended her feet.
reason for that is isolation and reduncancy though. Most incidents/outages are the result of a change and in the cases you mentioned they are mitigated by the fact that not all instances receive updates at the same time. Presumably, the error is noticed in one place and traffic is then served by healthy instances.
By all accounts these are practices that significant service providers follow. In fact AWS typically rolls out updates to us-east-1 before updating other regions to use it as a canary to warn against issues.
With federated services, this is less of a conscious decision and tends to happen only because instance maintainers update on different schedules.
Blue-green deployments and failover are common mitigation strategies and mature organizations actively employ these. Conversely, these patterns are integral to the decentralized nature of the fediverse and other distributed solutions such as cdn.