kjo

joined 2 years ago
 

Rescuing vintage microcontrollers from their decades-long purgatory in a drawer.

PS: not my blog.

 

DIY rebuild project for the Tektronix PS503A dual tracking power supply.

The constructed power supply: https://www.paulvdiyblogs.net/2026/03/diy-ps503a-construction.html

PS: not my blog.

[โ€“] kjo@discuss.tchncs.de 3 points 2 months ago (1 children)

Hey, thanks for the write up. Not everything in there is understandable to me, but I appreciate it.

[โ€“] kjo@discuss.tchncs.de 19 points 3 months ago

Nay, Lilly is cute ๐Ÿ˜บ

[โ€“] kjo@discuss.tchncs.de 1 points 4 months ago (1 children)

I am making an argument that copyleft licenses such as GPL are better than permissive ones because of the extra guarantees, primarily to the benefit to communities instead of corporations.

You on the other hand are making a false equivalence.

This is what i wrote:

If corporations want to release a software based on modified version of my code, I want a guarantee that the modified code to be available to the community too.

This is what you wrote:

What you are saying is, if they extend the Open Source software, you do not want the Open Source version anymore. You only want theirs.

The false equivalence is that because i desire communities to be the primary beneficiary of my code and its modifications, then i must also "... you do not want the Open Source version anymore. You only want theirs."

These are not equivalent. You have begun using a logical fallacy. More elaboration of my arguments will be fruitless. Good bye.

[โ€“] kjo@discuss.tchncs.de 2 points 4 months ago (3 children)

I welcome collaboration from everyone (including corporations).

With permissive license, corporations are allowed publish a modified version of the software while restricting their code modifications from release to the community. That is not collaboration. Permissive license benefits corporations more than the community.

corporations are a major (majority) source of Open Source

Which is why they choose permissive licenses for their projects. They receive code contributions from the community and then suddenly: rugpull! Starting from next version the software will be proprietary. The community contributors are of course having pikachu face when they realize the corporations are legally permitted to take the fruit of their labor from them because their contributions are under permissive license.

Nothing have been lost.

My time and effort has been lost. The fruit of my labor has been lost. When i contribute or make to a Free Software project, i wish for it to benefit the community the most. If corporations want to release a software based on modified version of my code, I want a guarantee that the modified code to be available to the community too. The corporations benefit from my labor, but the community receives the company's modified code too. That's collaboration. Copyleft licenses such as GPL guarantees this.

Of course, such guarantee is considered "restriction" if one never intends the community to be the primary beneficiary in the first place.

When I release code as Open Source, I am providing unpaid labour to everyone.

With permissive license your free labor benefits corporations the most. Corporations that take things and enshittify them and do not give back to the community, all the while they get rich. Your choice your prerogative.

[โ€“] kjo@discuss.tchncs.de 5 points 4 months ago (5 children)

Permissive license means that whoever (say a corporation) modifies some code and release a software from it, they are not obligated to release the modified code under the same license. Which means they can use Open Source software to make proprietary software, make money off it, and the community receives nothing back for their labor.

GPL forbids this. With GPL anyone can still modifes the code and release a software from it. But it obligates that the modified code must be released as GPL too. So GPL guarantees that the community benefits.

The act of choosing a license political one. Are you willing to provide unpaid labor for corporations? Or do you want your code to benefit communities?

[โ€“] kjo@discuss.tchncs.de 6 points 5 months ago

Cannot unsee ๐Ÿ˜Œ

[โ€“] kjo@discuss.tchncs.de 1 points 6 months ago

Indeed. Very well done. ๐Ÿ–ผ๏ธ

[โ€“] kjo@discuss.tchncs.de 3 points 6 months ago* (last edited 6 months ago) (1 children)

Bear with me for a bit, because i don't understand these schemes.

If the sellers instead just closed up shop, they would get maybe a fraction of the money they would from selling it, mainly in selling off assetsโ€ฆ It would be a pittance compared to this scheme.

How would the sellers get more money from this scheme? Isn't liquidating company assets are basically what the buyers (the private equity firms) did anyway?

collect whatever they can from insurance

How does the insurance companies keep falling for these? This has happened several times, and insurance companies aren't known for being charitable.

[โ€“] kjo@discuss.tchncs.de 17 points 6 months ago (1 children)

Phone needs to be connected to the internet for about a week (6 days for me) to get the OEM Unlocking

Ahhh, that's good to know now that i'm actually considering buying this device. That sucks. Still better than Xiaomi though.

[โ€“] kjo@discuss.tchncs.de 2 points 6 months ago* (last edited 6 months ago)

~~This is the same as moto g45 5G i think.~~ Apparently moto g 5G โ‰  moto g45 5G.

I am considering moto g45 5G at the moment.

I will probably keep my current device for shit apps necessary for banking etc.
I will install LineageOS on moto g45, and it will be for programs that will not have google's approval / F-Droid stuff.

[โ€“] kjo@discuss.tchncs.de 28 points 6 months ago (22 children)

Looks like I'm searching for a device that can run LineageOS, then.

๐Ÿค—

 

My goals for this firewall were mostly to provide better robot blocking and perhaps some more powerful DDoS protection than my Raspberry Pi 3 web server is capable of delivering. I still have to do some testing before I will know if my new firewall actually provides either of those, but at least I now have the additional ability to run multiple physical web servers on my LAN. Exploring that should be fun, and fun is a very important component of running a home web server.

Not my article. Just sharing.

1
Help Identify This Connector (discuss.tchncs.de)
submitted 1 year ago* (last edited 1 year ago) by kjo@discuss.tchncs.de to c/askelectronics@discuss.tchncs.de
 

Hello Ask Electronics community, please help me identify the name of this connector.

For context, this is from a motor scooter: Yamaha Mio M3 125. This socket connects the ECU to the wiring harness.

I wish to know how to open this socket to access the rubber/silicone seal inside, and to know that first I need to identify the name of this connector.

So anyone know what is the name of this connector?

Something like "Superseal 24-pin" or so. Also, to clarify: I am not searching for replacement part for this connector. I only need to know the name.

Here are some more pictures of the connector (hover above the picture to see alt-text).

(None of the pictures are mine, I just copied them from the internet).

 

Testing if Lemmy supports hashtags. #Monday #Test

 

My brand spanking new Casio F-105. It is only less than a day, but I like it so far. ๐Ÿ˜˜

Last time I wore a digital watch was decades ago.

Here's the electro-luminescent backlight. Can you tell I'm not used to take photo in the dark? ๐Ÿ˜…

 

A shortwave radio receiver from scratch using only cheap and easily available components, i.e. standard transistors, op-amps and 74xx logic chips. No typical radio parts โ€“ no coils, no variable capacitors, no exotic diodes.

 

Not my post/video. Link to mastodon.social post which then links to YouTube video.

Poster bought an old firewall hardware:

  1. saw unpopulated footprints on the circuit board,
  2. analyzed the chips,
  3. found the serial comm to access BIOS (blocked by password),
  4. dumped the SPI flash memory,
  5. obtained supervisor password,
  6. accessed the BIOS from serial comm,
  7. enabled the video display in BIOS,
  8. soldered the HDMI port,
  9. soldered the SATA power and data ports and the associated components,
  10. connected a SATA SSD,
  11. checked that the SSD is being recognized in BIOS,
  12. made modifications to firewall circuit board to mechanically secure the SSD, and to face plate to facilitate the HDMI port,
  13. installed FreeDOS and used it as a retro gaming PC.
view more: next โ€บ