

You already lost the data at that point and you really don’t want to play roulette with data that has the potential of killing your users. Just imagine what could happen if a gay man from Saudi Arabia joined your instance and that data leaks.
You already lost the data at that point and you really don’t want to play roulette with data that has the potential of killing your users. Just imagine what could happen if a gay man from Saudi Arabia joined your instance and that data leaks.
No, data must be shared between instances for federation to make any sense and the operators of other instances don’t necessarily share your views about privacy and security. Lets take for example a matching algorithm like the one OkCupid used to use. You answer some questions and based upon those people are recommended to you. If you want to see people from other instances as well, the answers to the questions must be shared between all federated instances; but at the same time these answers contain private details about you. I don’t think a workable solution to this problem exists, even if you come up with an algorithm that allows you to make decisions on anonymized data. The danger of deanonymization due to a bug is too high.
I would have serious concerns regarding data privacy. You share intimate and very private details about yourself on these apps that could be used for blackmail. I wouldn’t feel comfortable sharing that on a federated network. For example, how would you ensure data isn’t logged by a hostile server operator. A company is at least forced to play lip service to privacy laws. The theoretical operator of fedi-date.ru
can do what they want.
Obsidian stores the notes in a well known plaintext format on your computer. They can’t easily hold you hostage like with other closed source apps.
It has only three letters and its on the .com top-level domain. That’s it.
So this is a man-in-the-middle attack waiting to happen isn’t it? Buy the domain, setup a reverse proxy that points to the original hexbear server IP and start logging all requests.
I worked on a couple commercial C++ applications that used vcpkg. It’s not as convenient as nuget, cargo or npm but it think it is a massive improvement over manually hunting for dependencies.
Here are a couple of reasons:
I unsubscribed and deleted my Kagi account mainly because of their attitude to data privacy but also because of their nutjob CEO. When I subscribed I was excited because I thought they wanted to build a proper competitor to other search engine operators, but they are actually just another company that tries to shove AI into absolutely everything. So, after realising that they are an untrustworthy company full of tech maximalists trying to build the torment nexus, I immediately canceled my subscription and moved back to duckduckgo and marginalia. Maybe I give SearXNG another go, it’s just that selfhosting is a bit of a bother.
I don’t think control features help much when one of the most basic question that you can ask is “What is your gender and who would you like to date?”. As I have already outlined in another comment in this thread, this information has to be shared with the federated network and is already enough to get people into serious trouble should it get into the wrong hands.
Alternatively think about it this way. Would you hand over this kind of information to a total stranger? Would you take on the responsibility of handling data that could literally kill someone if you make a mistake?