Bummer - doesn't work for kbin... might be something as simple as the change from /c/ in community urls on lemmy to the /m/ magazine urls on kbin. Any chance they have a github or a contributor page to report a bug? Not seeing any on the initial interface.
Lmao - you're the first person I've ever told this story to who considered it a loss. I figure that there are some things you hold on to in this world, but sometimes you just have to let your therapist fly free...
My last therapist disappeared into the redwoods after doing a hit of acid laced with DMT. Seeing as he'd been growling like a tiger all night as part of some Hindu shaman thing he'd picked up on the streets of New Delhi, it was kind of a relief. All that was left behind was his kilt. Sometimes I wonder where he is and whether or not the Hell's Angels were really hunting him.
True story. Oregon can get wild in the backwoods.
That being said, you probably could do without my advice on finding therapists.
I just did via http://chat.petals.ml/ - was interesting enough to transcribe and post the results, although it did crash once I got deeper into the analysis due to rate limiting. It definitely has potential.
Because they're not tracking user behavior, they're actively stealing copyrighted content from web pages through the use of an automated crawler. It's actually not so much privacy abuse (bad, but legal in the US to an extent) as it's a violation of copyright law (really bad for the content creators and pretty much illegal everywhere).
If I were in this position, I'd refuse to give any money to the uncle, but my cousins would have the most awesome birthday presents and lots of fun trips with me to help them deal with having a deadbeat dad.
Also, while it's clear you're not in the US, so your laws may differ, there are trust funds you can set up for the kids that the uncle can't touch - and if they're young, it could be a lot of money for them when it matures at a minimal cost to you. Grandparents who want to support their grandchildren often do this when the parents can't be trusted with money due to addiction or criminal behavior. Another option to support the kids would be to take out a life insurance policy on the uncle in the kids name - there are a couple of variations that allow the kids to borrow against the value of the policy before he dies once they come of age.
There are good comments here already, but I thought I'd provide a practical breakdown of my experience using both in web development.
Open source software is generally better overall from a programming perspective. The "many eyes" dynamic can be extremely positive if the project has a strong developer community. Even smaller communities make great software.
On a security level, I'd say they're about on par - I've had about as many security issues with open source as I have with closed. It was what to do when that security problem arose that the real difference came into play. In open source, you either have to figure it out yourself, or wait for the community to fix it. In closed source, you're paying someone to fix it for you. On the balance, closed source security issues get fixed faster than open source in my experience, but it really depends on the strength of the community behind the open source project, versus the size of the closed source company - bigger companies move a lot slower than many of the smaller services I've used.
On a software evolution level, open source wipes the floor with closed source. There's simply no competing with the amount of creative minds behind open source development. Most closed source successes in the online world are built on the backs of open source developers - if not directly, than on the ideas that had their genesis in the open source space.
When it comes to consistency and stability, they're about neck and neck, with a slight advantage to closed source. Again, it's the difference between volunteers maintaining the code and someone you're paying.
On a personal level, how much do you want to be involved with running the software? If you want to have a greater level of control, build new features, and have the time to maintain it, go open source. If you just want it to work and you're willing to pay someone else to maintain it, go closed source.
Note in a corporate setting, it's often better to go with closed source, as then you have more plausible deniability and someone else to blame when it fails.
Neither am I! Totally! Not one bit... after all, far be it from me, a humble peon, to pull traffic away from the content Spez has claimed as his personal fiefdom.
You either have to start one yourself, or have a friend do it. I think you have your work cut out for you - honestly, being mod of a cross-dressing community sounds like herding cats in hell. Fabulous cats.
Damn - the mental gymnastics that account performs to try and justify systematic oppression is worthy of Olympic Gold. 90% of their arguments are "China's not bad because the US is worse", followed by a full frontal attack on democracy and "wokeness" while claiming to be a leftist. A very shrill shill.
Bummer - doesn't work for kbin... might be something as simple as the change from /c/ in community urls on lemmy to the /m/ magazine urls on kbin. Any chance they have a github or a contributor page to report a bug? Not seeing any on the initial interface.