remotelove

joined 2 years ago
MODERATOR OF
196
[–] remotelove@lemmy.ca 1 points 1 hour ago

(For others reading this, this is a perfect followup to my comment here explaining the "why", while this is an excellent view into the "how" and picks up the bits I dropped about Ohms Law.)

[–] remotelove@lemmy.ca 9 points 2 hours ago* (last edited 2 hours ago)

Pin pitch is pin size and/or spacing. With physical plugs, you start to hit limitations with how small the wires can get while still being durable enough to withstand plugging/unplugging hundreds of times.

Drop losses. (I am keeping this at an ELI5 [more like ELI15, TBH] level and ignore some important stuff) Every electronic component generates heat from the power it uses. More power used usually means more heat. Heat requires physical space and lots of material to dissipate correctly. Depending on the materials used to "sink" (move; direct; channel) heat, you may need a significant amount of material to dissipate the heat correctly. So, you can use more efficient materials to reduce the amount of power that is converted to heat or improve how heat is transferred away from the component. (If you are starting to sense that there is a heat/power feedback loop here, it's because there can be.) Since a bit of power is converted to heat, you can increase the power to your device to compensate but this, in turn, generates more heat that must be dissipated.

In short, if your device runs on 9v and draws a ton of power, you need to calculate how much of that power is going to be wasted as heat. You can Google Ohms Law if you would like, but you can usually measure a "voltage drop" across any component. A resistor, which resists electrical current, will "drop" voltage in a circuit because some of the current (measured in amperage) is converted to heat.

I kinda smashed a few things together related to efficiency and thermodynamics in a couple of paragraphs, but I think I coved the basics. (I cropped a ton of stuff about ohms law and why that is important, as well as how/where heat is important enough to worry about. Long story short: heat bad)

[–] remotelove@lemmy.ca 1 points 17 hours ago
[–] remotelove@lemmy.ca 5 points 20 hours ago (1 children)

You don't go for your weekly dopamine sprays? It's totally the new thing.

[–] remotelove@lemmy.ca 23 points 1 day ago

Oh rock on. I misread the URL, so thanks!

[–] remotelove@lemmy.ca 93 points 1 day ago* (last edited 1 day ago) (3 children)

I love me some good old fashioned verification, so thanks for falling on that sword for us. (No way in hell am I clicking through to that shit hole though.)

Edit: I misread the URL and it's an archive site, not TS.

[–] remotelove@lemmy.ca 1 points 1 day ago

Any experienced mixing engineer should be able to tell. Here is your flea whisperer.

[–] remotelove@lemmy.ca 28 points 1 day ago (4 children)

If the shoe fits... turn everyone in a 500ft radius into Hulk.

[–] remotelove@lemmy.ca 11 points 1 day ago (3 children)
[–] remotelove@lemmy.ca 58 points 3 days ago (1 children)

So one arm of Google is making the slop and the other is trying to avoid it? Neat.

[–] remotelove@lemmy.ca 11 points 4 days ago (1 children)

My general attitude is similar to yours. Let OP figure out that the reporting and blocking is basically just creating more noise that has to gets filtered out and bot supply is basically infinite.

"It's a learning experience."

 

I have no plans to move from Lemmy any time soon, but I am curious if PieFed integration was being considered.

It would probably make more sense to fork Connect but a "multi-client" would be neat.

247
face. (lemmy.ca)
 
 

There seems to be a correlation between how long a feed hasn't been interacted with and this behavior. (Scroll up and down a feed; Wait a random amount of time; pre-fetching seems to halt.)

There are times when pre-fetching the feed can be slow and briefly pause while loading. Sometimes, this is when the feed will lock up.)

 

... this happens more often on cursed memes. /s

I can still slide to open the menu, but cannot take action on the feed. (The + button opens in the fore-foreground, so it works as well as 'back to exit' Connect.)

I was playing with the thumbnail preview in fairly rapid succession when one just "stuck".

 

Seemingly random. Error may only happen on the first post a new thread. Could be a server-side issue, but not sure.

 

Menu -> Refresh does not cause this issue.

 

I just realized that I have never used an oscilloscope on anything over 50V DC. (There has never been a need, actually.)

The goal is to trace how noise generated by my PC GPU is propagating through the power circuit. As I don't want to start tossing in power filters at random spots, it would be nice to actually understand what is going on first.

TBH, measuring mains AC doesn't seem any different than any other measurement I would take, other than using a 1:100 scope probe. Are there any "gotchas" I should be aware of that would put my scope at risk?

 
 

OMG. This recipe is one of the best I have tried.

 

Our dev does good things. Please help keep the world economy intact by buying him a coffee.

Connect -> Settings -> Scroll to bottom -> Support your dev link.

Nelson demands it.

Edit: A few coffees later and the DOW is up 2k. Coincidence? I think not.

 

Originally, I just wanted to request tagging specific instances as NSFW. This would be helpful for posters on specific instances that do not always tag posts as NSFW but still should get caught by our NSFW preferences.

NSFW isn't always porn so the NSFW filter catches a bit much, sometimes. Excluding specific communities from the NSFW filter is an option, but that gave me yet another idea.

Expanding on this idea, it would be cool to start categorizing communities with tags, like "sports" or "news", "world news" or something arbitrary like "neat".

This would allow filtering by what kinds of content I want to view at any given time, in theory. Hell, we could even start building a master list to share for community categories in GitHub or something like that.

42
Corm (lemmy.ca)
 
view more: next ›