#ChatControl (the proposed EU regulation which would require backdoors to encryption if it can send a video, picture or link) is set to be voted on June 19th.
They've been trying to pass this for the last two years and it looks like it might happen this month.
If passed, it will affect people around the world.
More info and suggested actions for how to resist available here: https://blog.cryptpad.org/2022/05/19/against-chatcontrol/
The only good news I have for you here is that the law currently targets "service providers", not "software developers" or "end users" (directly). Developers who also run a service, or get income from service providers will be affected indirectly.
The tactic being used here by the lawmakers is to starve developers of funds so they have to stop working on open source projects and get a so-called "real job". There are not many options for directly stopping developers from writing and sharing code, but this is a pretty effective way to slow down development and try to burn out open source developers.
Source: https://social.cryptography.dog/@ansuz/112630461011248734
And the reason they're not targetting end users is because it'd turn publuc support against them (more so than it already is).
People are a lot more okay with lawmakers regulating [big] businesses than they are with being told "we are banning that app you like". It's a lot more pallatable when the proposed law seems to only affects a few dozen companies and not the entire population.
I'm afraid not. The issue is service providers can not operate in their jurisdiction if they do not comply with the law. It doesn't make any difference if it's a paid service or not.
The law can be circumvented by operating the server out of another jurisdiction, but this also means that the operators themselves also need to be outside the EU. For example, if the sysadmin is in the EU and the server is not, they're still coming for that sysadmin, at least as I understand it.
Now tipping could solve the development problem where people have rent to pay, food to buy and so forth. The law doesn't currently prevent them from developing the software or getting paid to develop the software.
Although I'd suggest talking to a lawyer to anyone in this situation! Taking legal advice from someone who is neither a lawyer nor even in the EU would be riskier than is warranted.
Remember Jason Lowery? He's apparrently flying small planes now and pretending that whole "softwar" thing never happened.
https://bird.makeup/users/jasonplowery/statuses/1684637080029196288
What a strange world.
#ChatControl (the proposed EU regulation which would require backdoors to encryption if it can send a video, picture or link) is set to be voted on June 19th.
They've been trying to pass this for the last two years and it looks like it might happen this month.
If passed, it will affect people around the world.
More info and suggested actions for how to resist available here: https://blog.cryptpad.org/2022/05/19/against-chatcontrol/
The only good news I have for you here is that the law currently targets "service providers", not "software developers" or "end users" (directly). Developers who also run a service, or get income from service providers will be affected indirectly.
The tactic being used here by the lawmakers is to starve developers of funds so they have to stop working on open source projects and get a so-called "real job". There are not many options for directly stopping developers from writing and sharing code, but this is a pretty effective way to slow down development and try to burn out open source developers.
Source: https://social.cryptography.dog/@ansuz/112630461011248734
Got the #Signet Windows and MacOS builds done, signed and uploaded.
Linux and Windows releases are well tested.
I did some testing on my development machine for the Mac version, but still need to go test it on a separate Mac to be sure. I've seen problems in the past where it worked on the build box but not on another Mac.
Once testing is complete, I'll update all the links on the website. If you want it now, just change the 0.9.19 to 0.9.20 in the download URLs.
It is better to share your key fingerpint, and nostr:npub1ajdaw3j4g6aqv86alhn3df8jpulj0mxz3jjgwpm4uh598hc348gqthdt20 is spot on about having to publish your public key.
Message + public key = cipertext
Ciphertext + private key = message
So we need the public key to encrypt (and you need the private key to decrypt).
Sharing your fingerprint is how we search for your public key on PGP key servers.
We can also search for keys by email address, but since anyone can upload any key and claim that it belongs to your email address, we want to get the fingerprint directly from you to make sure we have the correct one.
Handing over your fingerprint used to be done in person, but I guess those days are largely behind us now. 🫤
Got the Linux binaries and packages released for #Signet v0.9.20
I have to go to a Mac to compile the Mac build and a Windows box to do the Windows build. But it is late here so I'll try to get those done tomorrow along with updating the links on the website.
Just fixed opening a #backup file in the #Signet client without any #hardware connected (e.g. if your device is lost/destroyed and you need your #passwords so you can order a replacement).
That, plus:
- #accessibility improvements to be compatible with a screen reader
- fixed device detection without having to restart the client on #Debian 12 (the only place it broke)
- #developer #documentation
- and some odds & ends
Version 0.9.20 release in progress now! 🤓
#FOSS #OpenSource #OpenHardware #value4value
We were late with everything except tomstoes, peppers and eggplants. But we've got it sown now. Radishes, spinach, carrots, beats, kale, and a few other odds and ends.
Store fruits and vegetables that you dehydrste. Either things you grow or are on a deep sale at your local farmers' market or grocery store.
Store bulk goods like coffee beans, sugar, flour, and so forth. We have a 2-jar system where when one gets emptied, we send it to the store to get refilled. That way we always have some of each ingredient in stock.
If you've ever been to #Berlin and not had Döner kebab, you are missing out, my friend. It's the best street food in town.
At some point my '96 Legacy is going to die and my plan is to go without a car for a while and just rock the bicycle.
If that doesn't pan out my backup plan is to find the local group of peope who took an old clunker and put an electric drive train in it. I'll understand how everything works, no privacy policy, no phoning home, no nonsense.
The #Meshtastic #documentation for #RaspberryPi Pico based nodes is 💩. From #development environment setup to #compiling to #flashing to using it with the Android app.
I'm going to figure out the process and then fix that.
Maybe they'll accept my changes upstream, maybe not, but either way, I can say for certain that **I** will have proper documentation.
As someone who grew up when only doctors and drug dealers had pagers (and later, cellular telephones), some things still strike me as being bizarre.
For example, buying things from someone used to be that you gave the person money (which we now call "cash") and they're give you the object.
Now, people need a big tech/finance company who decide whether these people can do business, or even make a donation! Sexy photos? PayPal says no. A hunting rife for your daughter? Nope. Wikileaks. LOL, no.
For legal purchases, it seems very strange that a private company would decide what is allowed. It's stranger yet that most people think this is just normal and acceptable.
I've been enjoying buying things from local establishments whenever I can and paying in cash. It's not that I'm trying to hide the quantity of shredded cheese I buy from the grocery store, which local artists I support, or how much I donate to non-profits. It's just a return to a simpler time and a way to stick it to big corporations and data collectors.
I have used both #OpenSCAD and #FreeCAD and I use FreeCAD for things I design from scratch. I can brush up on my OpenSCSD skills to modify an existing part though.
They are very different programs and they have distinct learning curves!
Different workbenches in FreeCAD will be better or worse depending on what you are modeling. Generally speaking, I'd suggest starting with the Part Design workbench. Once you get the hang of the basics with one workbench, it's easier to make sense of the other workbenches as you branch out.
I'm glad to see othe #CAD modelers on here. Giving you both a follow now. 🙂
I take it that it is the set screw whose hex derive that is stripped?
I'd suggest screw extractors.
https://www.mcmaster.com/products/easy-out-extractors/
In case you are not familiar with them, they are reverse threaded and tapered. As you push in and turn them with a hand tap wrench the threads dig into the inside of the hole that you drilled into the head (or in this case, possibly directly into the hex hole). Once it grips, it'll be easier for the threads to move than for the screw extractor to dig in further.
Might want to hit it with some lubricant (deep creep, WD-40, etc.) before you start.
Will the revolution be televised?
That depends. Will we have water? Electricity? Who will revolt and over what?
https://geoffreydeihl.substack.com/p/will-the-revolution-be-televised
It's grim, but he makes a strong case. Seeing the mass surveillance intensify, attacks on encryption, increased police funding and other things make it seem like maybe some others believe this to be the case too.
I made a bunch of small improvements in the #Signet client today:
- Detect when devices are plugged in on Debian 12 (they changed something in version 12 and I had to make changes in the Signet client as a result)
- Search looks in group names in addition to account names
- When selecting the firmware file, only show files with a valid firmware extension
- Fixed the default filename when making a backup
This was a great decision. I feel refreshed, both mentally and physically.
I hope I remember this in the future and actually make this a habit.
I'm glad I follow you and see these reminders from time to time. 🫂