Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I'd probably just spin up a calendar such as one on Nextcloud but also change the name of the event to another plausible name such as:
Pay day.
Grandma coming to town.
Grandma leaving town.
Walk the cat.
Pick up groceries.
Collect mail.
Drop off mail.
As someone who uses Nextcloud, why do you suggest obfuscating the name of the calendar event? My nextcloud instance is only accessible from outside my LAN via HTTPS, so no concern about someone using a packet sniffer on public WiFi or something of that sort. The server is located on my property, so physical security isn't a real concern unless someone breaks in with a USB drive or physically removes the server from the rack and steals it. If someone was to gain access to my network remotely, they'd still need login credentials for Nextcloud or for Proxmox in order to clone the VM drive.
To be clear, I'm not disagreeing with you; I'm wondering if I may be over-estimating data security on my home network. Considering you're posting from infosec.pub, I'm assuming you know more about this than I do.
Also, I feel like I need to say that the fact that OP even needs to consider data security for something like really makes me wonder how parts of our society have gone so wrong.
If your concern for wanting to self host is that you're concerned your government might attempt to access that data, then you should also assume they could get a warrant for that data and force you to decrypt it if it were encrypted at rest on a machine in your home.
That's a very valid point, and certainly a reason to obfuscate the calendar event. I would argue that in general, if the concern is the government forcing you to decrypt the data, there's really no good solution. If they have a warrant, they will get the encrypted data; the only barrier is how willing you are to refuse to give the encryption key. I think some jurisdictions prevent this on 5th amendment grounds, but I'm not not a lawyer.
Right, this is exactly what I was saying. Plausible deniability because you know you're not going to be able to fight to protect the data when they come knocking.
They can't force you to decrypt it in the US due to the 5th amendment
The police can confiscate your servers. Considering some states are treating abortion as murder, I don't think it's unrealistic to say the police could raid your home and confiscate your devices just on suspicion.
The only thing safe against that is an encrypted device locked with a password, no biometrics like fingerprints or face ID. As far as I know, you can refuse to give a password under the 5th amendment, but you can't refuse to unlock a device with a fingerprint reader or face ID.
But how would that work? I wouldn't know when my next cycle begins before the current one ends so I'd have to adjust all future entries myself all the time? Or would you not add future periods but then what is the point if you'd just get surprised anyways? And also adding in PMS and evaluation, would you do them as 3 separate calendars? If it's in the same one doesn't it get visually confusing?
To tell you the truth - I don't bleed from my genitals so I don't have the solution for you.
Time between periods should be 24-38 days. If you can't manage that in a calendar, how can an app know?
But it's a different length every time. Like one cycle might be 26 days, the next one 24 and so on. Unless you use a hormonal contraceptive I suppose, but who would want to risk the long term damages that causes.
The app I currently use can calculate it using the body temperature I enter and adjust the planned dates based on that. I'm pretty lucky to live in a first world country I guess because having to calculate this every day on my own sounds like a pain.
Damage? What damage?
Also if you're not on one you should be. Don't want to be forced to have some bastard rapists kid.
Blood clots and cancer, suicidal thoughts and many more. Also I don't live in a third world country so I would not have to carry that to term anyways.