We’re not looking to be tied to a grid outside the community. Do you have any links to recommended resources to learn more about microgrids and/or community grids?
If it were me and I understand correctly I would probably not tie the systems together.
Well, the loads of the buildings are different, so tieing them together would be very beneficial. For example, one building is a workshop with lots of power tools and heavy machinery and some other buildings (with equal sq meter rooftops) are residential (with less energy requirements)
Hi, Michael Altfield here. I was the sysadmin for OSE from 2017-2020.
Everything OSE does is transparent, so you can just check the OSE websites to see what everyone is currently working-on. OSE contributors log their hours in a worklog called “OSE Dev”. There you can quickly see who is working on what.
The above graphs show 4 contributors in the past ~10 weeks (one is me; we had some issues with the apache config recently). There’s no direct link, but you can then check the wiki to see people’s work logs (just search for the person’s name and Log):
I told Marcin about Lemmy back in June 2023. Another OSE contributor even created an OSE community on the slrpnk.net instance, but it appears to have been abandoned. I’ll email him about this thread to see if he’ll bite and publish updates in this community since there’s clearly interest :)
Also, shameless plug: I started an org that’s very similar in spirit to OSE called Eco-Libre, with a focus on projects to sustainably enfranchise human rights in smaller communities. We’re currently accepting volunteers ;)
That would be true if their instance wasn’t federating. If the instance is federating, then it’s downloading content from other users, even if the user isn’t registered on the instance. And that content is publicly available.
So if someone discovers their content on their instance and sends them a GDPR request (eg Erasure), then they are legally required to process it.
Did you read the article and the feedback that you’ve received from your other users?
Any FOSS platform has capacity issues. I run my own FOSS projects with zero grant funds and where I’m the only developer. I understand this issue.
What we’re talking about here is prioritization. My point is that you should not prioritize “new features” when existing features are a legal, moral, and grave financial risk to your community. And this isn’t just “my priority” – it’s clearly been shown that this is the desired priority of your community.
Unfortunately, the Lemmy devs literally said it would take to fix this issue. If you think this should be a priority for them, please advocate for them to prioritize it on GitHub:
file (aka the "alias") is the server filename of the uploaded image
delete_token is the token needed to delete the image
Of course, if you didn't capture this image's delete_token at upload-time, then you must fetch it from the postgres DB.
First, open a shell on your running postgres container. If you installed Lemmy with docker compose, use docker compose ps to get the "SERVICE" name of your postgres host, and then enter it with docker exec
ⓘ Note: If you get an incorrect_login error, then try [a] logging into the instance in your web browser and then [b] pasting the "https://<instance_domain>/pictrs/image/delete/<pictrs_delete_token>/<image_filename>" URL into your web browser.
The image should be deleted.
Method Two: /internal/purge?alias={alias}
Alternatively, you could execute the deletion directly inside the pictrs container. This eliminates the need to fetch the delete_token.
First, open a shell on your running pictrs container. If you installed Lemmy with docker compose, use docker compose ps to get the "SERVICE" name of your postgres host, and then enter it with docker exec
<span style="color:#323232;">~ $ wget --server-response --post-data "" --header "X-Api-Token: ${PICTRS__SERVER__API_KEY}" "http://127.0.0.1:8080/internal/purge?alias=001665df-3b25-415f-8a59-3d836bb68dd1.webp"
</span><span style="color:#323232;">Connecting to 127.0.0.1:8080 (127.0.0.1:8080)
</span><span style="color:#323232;">HTTP/1.1 200 OK
</span><span style="color:#323232;">content-length: 67
</span><span style="color:#323232;">connection: close
</span><span style="color:#323232;">content-type: application/json
</span><span style="color:#323232;">date: Wed, 14 Feb 2024 12:56:24 GMT
</span><span style="color:#323232;">
</span><span style="color:#323232;">saving to 'purge?alias=001665df-3b25-415f-8a59-3d836bb68dd1.webp'
</span><span style="color:#323232;">purge?alias=001665df 100% |*****************************************************************************************************************************************************************************************************************************| 67 0:00:00 ETA
</span><span style="color:#323232;">'purge?alias=001665df-3b25-415f-8a59-3d836bb68dd1.webp' saved
</span><span style="color:#323232;">
</span><span style="color:#323232;">~ $
</span>
ⓘ Note: There's an error in the pict-rs reference documentation. It says you can POST to /internal/delete, but that just returns 404 Not Found.
The image should be deleted
Further Reading
Unfortunately, it seems that the Lemmy develoeprs are not taking these moral and legal (GDPR) risks seriously (they saidit may take years before they address them), and they threatened to ban me for trying to highlight the severity of this risk, get them to tag GDPR-related bugs, and to prioritize them.
lemmy #4433: Deleted Account should delete uploaded media (pictures) too
lemmy #4441: Users unable to delete their images (pictrs API)
lemmy #4434: Unapproved users cannot delete their accounts/data
lemmy #3973: Banned users cannot delete their accounts/data
lemmy #4445: Create an interface for local users to view and remove images
lemmy-ui #2359: Allow users to delete images they uploaded
lemmy-ui #2360: Allow admins to view & delete uploaded images
lemmy-ui #2361: private_message_disclaimer to include user's matrix handle
No, please do not deactivate downvote functionality.
(I say this as someone who has received a lot of downvotes; they’re useful feedback that I appreciate)
Also, monero.town is currently a recommended instance on awesome-lemmy-instances (at the time there’s only 7 recommended instances, and monero.town is one). If this instance deactivates downvote functionality, it will no longer be recommended as downvote functionality is one of the requirements for recommendation.
You definitely can do that, but if you’re afraid that you might stand-up and forget you’re using it, then you probably shouldn’t.
It’s probably enough to just use the default trigger that locks your screen. Or, once you get comfortable with it, set it to shut down your computer. Most people don’t need to shred their FDE keys, unless they’re facing torture.
In fact, we make it difficult to use “destructive” triggers (like the LUKS Header Shredder that wipes the FDE header) and intentionally do not include the ability to switch to it in the app. To use it, you have to do a lot of extra work. So most users don’t have this issue.