I imagine, sometimes, its the only way to cope with them. some people get paranoid, some do not. setting and grounding play important roles in this.
if you really want a deep dive (cuz your post suggests that), fire up wireshark on a speed test PC and capture the traffic while you test. look for out-of-order, missing and corrupted packets. you will also get awesome stats on the traffic - wireshark is your best friend. be warned, this is the entrance to the rabbit hole.
edit: because at some point you are going to want to slide wireshark between the cable modem and your router - for general troubleshooting (and funsies!) then things get interesting as you figure out how to do that properly.
test it early morning when your neighbor peeps are sleeping (or bulk traffic torrenting - QoS usually knocks them back down pretty quickly). at the least you are looking for rock solid ping times. if pings are wild your link or the community bandwidth is possibility saturated.
is something already pushing 300Mbps worth of traffic across the router? speed tests that are good at power cycle, but quickly deteriorate after, can sometimes indicate that you have unaccounted for traffic crossing a bandwidth limited i/f (your ISPs service).
check your router stats for the missing traffic.
edit: also, almost all ISPs have a "burst bucket" for quick but intensive bursts of traffic. you get super speed for a few seconds while your bucket fills up. once full/overcommitted, your ISP starts rate limiting your service again. that may be why you get nice initial speeds, but they drop off quickly. does your ISP give burst speeds and sustained speeds in its terms of service contract on your kids?
CIA: "sounds like socialism, boys. you know what to do."
israeli drone strike on dearborn, MI in 3, 2, 1...
with us made weapons, of course! ’cuz ’murica!
at which point you turn on all symbols/debugging, bloat your binary 10x and submit it ...cuz it seems to work sometimes then.
...and the beatings will continue apace!
yup. absolutely zero lessons learned. FML.
or, if you are really lucky, you can poke the right locations and release the magic blue smoke from the chips. super fun and all the cool kids are doing it.
unsurprisingly, I think bernie does not care and would only consider the safety of others involved.
to my thinking, anyone involved should be willing to commit to the idea that this revolution wont come through evolution and wont be televised.
Crowd sourced, open access FLOS(Data) is almost always good. will check it out. thanks!
and, hopefully, we can finally let the man rest a bit.
excellent article. thank you.
I torture it by pointing its webcam at the wall outlet and forcing it to watch its own pull-the-plug execution.
I will be among the first against the wall when the AI revolution comes.
They are doing everything possible to bait Harris into a mistake
super walz to the rescue. seems like he has played the VP attack dog role pretty smartly. loud enough to make headlines with reasonably pointed attacks, while being "clean" enough to deflect incoming.
that snark just snapped my head back.
mirror, mirror on the wall...
app crashes after v0.0.35 update
just updated to the v0.0.35 f-droid build and jerboa started to consistently crash at seemingly random times. likewise, I would get web UI error notifications while using the web frontend.
did a little testing and noticed that it may be related to the "show avatars" setting being enabled.
turning "show avatars" off and saving the settings seems to have eliminated the issues on both web and app.
will continue to test and update the post if needed. any others able to confirm or refute this particular issue might be helpful.
edit: there are still crashes related to editing a post, but crashes while scrolling through posts and comments seem to be much reduced. any feedback is welcome.
edit2: further poking suggests the underlying cause may be jerboa not handling server response timeouts well. turning off avatars may reduce the number of API calls and therefore the number of potentially mishandled timeouts. crash frequency is likely variable as a result of variable server load. if others also experience reduced crash frequency with avatars turned off then I can either create a github issue or add info to an existing one.
Jeep gets us
sorry about the quality - was stopped (safety first) but dealing with poor picture taking conditions.
The network IS us
I know that many of us already know this, but it should repeated as often as needed.
we are the network -- the network is us.
social is nothing without the interactions that we create. reddit was just a place; a place that, because of a centralized power dynamic, abused us all.
we have are now at a cultural juncture, an opportunity to bring back what each of us knows to be true. our interactions do not need to capitalized, marketed and sold.
we are not products. we are the network.
please, find communities that even mildly interest you or catch you eye, join them and comment on posts.
just had this conversatin with the wife and she is joining Lemmy to start her own federated social journey.
/end_rant
share the load
pretty please... we need a samwise "share the load" meme for Lemmy instances, and it should be pinned far and wide.
mememasters... do your thing.