nowadays there is also malware that actually infect the firmware. Meaning just wiping the content isn’t good enough anymore. Same is true for BIOS worms/infections.
Software Engineer & DevOps Architect. Mbin contributor (and creator of the fork).
He/him 🇳🇱
nowadays there is also malware that actually infect the firmware. Meaning just wiping the content isn’t good enough anymore. Same is true for BIOS worms/infections.
(what did you say? I can’t read or ty.e mani 93
yea microwave all your sticks in your house at full power for 15 minutes.
My bad. I was almost injecting another worm.
Do you want to see something cool? See: https://www.youtube.com/watch?v=Uf4Ux4SlyT4
Try C-band UV Lamp instead.
Try to clean your USB stick. Remove the worm and maybe use a cloth to remove the dirt.
it is without obligation ;)
@Aatube It seems that Mbin isn’t handle those changes correctly and change the thread/post type after such a change.
I hate smoke alarms, especially since I have Tinnitus. So indeed I throw those away.
Understood. I’m also maintainer of several AUR packages.
I asked Ernest 1 year ago about delegating and empower the software developers, but that didn’t happen and will never happen. That was the reason to create Mbin.
Mbin was created to get kbin to the next level.
I will continue to use telegram
No not really. The problem is that Ernest wants to be a final person that does all the checks/reviews/etc. Creating a bottleneck in the process. Hence Mbin was created to give much more developers and contributors the rights to review each other code and merge code (also known as pull requests). And using the C4 specification. See: https://github.com/MbinOrg/mbin/blob/main/C4.md and: https://github.com/MbinOrg/mbin/blob/main/CONTRIBUTING.md.
Mbin is a fork, Kbin is currently not in active development. See also: https://github.com/MbinOrg/mbin
It really whips the llama’s ass. It’s back from the death!!