forestG

So many memories... Thanks !

Ah, the duck alarm and human to the rescue XD

This post made my day, thanks!

Wikipedia defines snack as a small portion of food that is eaten between meals. The way I think about it, that is the only distinction between a meal and a snack. That "in between meals".

This, as far as weight goes, carries with it an inherent quality that makes regulating weight harder. If not impossible, depending on your sleep patterns (the etymology of the term breakfast indicates exactly how this is relevant to what I am saying here). It's nearly impossible to find snacks that have zero insulin response in your body. Insulin not only promotes energy storage, but it also prevents the body from using energy already stored. Making a habit of doing that, even when you don't face weight problems (which are related to health issues), is essentially making a habit of preventing your metabolism of using energy already stored from previous meals.

This is also probably the most important reason why people speak highly of intermittent fasting or low carb diets. Most of them, through these two approaches, regardless of the other positive/negative aspects, completely eliminate the habit of constantly spiking their insulin levels, effectively allowing the body to regulate energy levels through both the energy still available from a meal and the energy stored from previous meals.

Imo, there’s no shame in getting orthodontia just because you prefer that aesthetic or really don’t like the way your teeth currently are, either. None whatsoever.

Even though I agree with what you say, I think the article was not an attempt to shame people who get their teeth fixed for whatever reason, cosmetic or functional. I perceived it more like an attempt to explore the extend of the unrealistic standards propagated through media, cinematic or web based.

I mean, what about body dysmorphia? It's not the people who fall into this trap that are the issue. They are not vain, and they probably actually suffer in more ways than one. They are actually the victims of unrealistic standards propagated by media. I believe that attacking those standards is not the same as attacking the people that identify themselves in them.

And it doesn't really stop at the teeth. It's everywhere. Bodybuilders struggling for years to achieve physiques that are not only impossible to achieve without PED's but actually also harmful to their health (especially if they start using drugs). Men injuring their bodies in countless ways to match false standards of what strength is supposed to look like. Women performing dangerous and sometimes clearly unhealthy plastic surgeries to match false standards of what attractive female figures are supposed to look like. Young people getting their faces changed permanently before they actually get a chance to experience the world fully.

This is not a new thing either. If you start looking into our past, there have been countless types of clothes that fit like a fingerless glove which people used to wear in order to conform to whatever social standards were at the time.

What is new though, is the extend to which these standards spread through modern media.. Comparing the current situation to the one before the web, like for example the extend to which magazines or tv shows could influence people's standards, looks scary to me. Oppressive to say the least.

Sunflower plant here.

I feel like a cannibal munching on sunflower seeds while reading the description of my type of plant XD

I don't think there is a way to have both the option to host images and have zero risk of getting such image uploads. You either completely disable image hosting, or you mitigate the risk by the way image uploads are handled. Even if you completely disable the image uploads, someone might still link to such content. The way I see this there are two different aspects. One is the legal danger you place yourself when you open your instance to host images uploaded by users. The other is the obvious (and not so obvious) and undeniable harmful effects contact with such material has for most of us. The second, is pretty impossible to guarantee 100% on the internet. The first you can achieve by simply not allowing image uploads (and I guess de-federating with other instances to avoid content replication).

The thing is, when you host an instance of a technology that allows for better moderation (i.e. allowing certain kinds of content, such as images, only after a user reaches a certain threshold of activity), actually helps in a less obvious manner. CSAM is not only illegal to exist on the server-side. It's also illegal and has serious consequences for the people who actually upload it. The more activity history you have on a potential uploader, the easier it becomes to actually track him. Requiring more time for an account before allowing it to post images, makes concealing the identity harder and raises the potential risk for the uploader to the extend that it will be very difficult to go through the process only to cause problems to the community.

Let me also state this clearly: I don't have an issue with disabling image uploads here, or changing the default setting of instance federation to a more limiting one. Or both. I don't mind linked images to external sites.

I am sorry you had to see such content. No, it doesn't seem to go away. At least it hasn't for me, after almost 2 decades :-/

Even though the data loss is a little sad (much time went into thoughtful comments now lost), it's on version 0.18.4... Bugs are to be expected.

I don't know whether this was caused by the timestamp issue mentioned by Penguin in the other thread about delays, but yeah, it's obvious that the technology is not yet mature enough. Let alone it being suitable (alyaza mentioned the growth of storage space, which doesn't even make sense when there is no data mining in place, since actual people pretty much never return to older posts)...

On topic, from the outside, the data loss, looks like a database rollback to a previous snapshot.

Anyway, I hope this doesn't make you feel bad, you 've got a good thing going here, regardless of the technical issues, lemmy, or the fediverse as a whole.

As someone who grew up with a (quite) younger sibling in the most disabling end of the spectrum, witnessing all the development from infancy to adulthood, I am very reluctant to recommend for/against any specific approach, because I think that what matters most is the people who actually practice it. So, I absolutely agree with the last sentence of your comment.

The negative aspects of ABA are not entirely in the past. I am not in a position to verify the information I will quote, but this is mentioned in the third of the linked articles:

Mandell says ABA needs to renounce that history — especially the early reliance on punishments like yelling, hitting, and most controversially electroshocks, which are still used in a notorious residential school in Massachusetts called the Judge Rotenberg Educational Center.

To be clear: I am not arguing with your experience here. Rather, I am pointing out how important is the kind of practice of whatever theory and what the focus of the practice actually is. It's really very difficult to find professionals who are actually both able and willing to care properly for autistic people. At least in the place I live.

Beyond that, I have to say that there are many things that now have positive effects on people's lives that weren't exactly positive in their original forms.

At least, not at first. As the scandal heated up, EFF took an impassive stance. In a blog post, an EFF staffer named Donna Wentworth acknowledged that a contentious debate was brewing around Google’s new email service. But Wentworth took an optimistic wait-and-see attitude—and counseled EFF’s supporters to go and do likewise. “We’re still figuring that out,” she wrote of the privacy question, conceding that Google’s plans are “raising concerns about privacy” in some quarters. But mostly, she downplayed the issue, offering a “reassuring quote” from a Google executive about how the company wouldn’t keep record of keywords that appeared in emails. Keywords? That seemed very much like a moot point, given that the company had the entire emails in their possession and, according to the contract required to sign up, could do whatever it wanted with the information those emails contained. EFF continued to talk down the scandal and praised Google for being responsive to its critics, but the issue continued to snowball. A few weeks after Gmail’s official launch, California State Senator Liz Figueroa, whose district spanned a chunk of Silicon Valley, drafted a law aimed directly at Google’s emerging surveillance-based advertising business. Figueroa’s bill would have prohibited email providers like Google from reading or otherwise analyzing people’s emails for targeted ads unless they received affirmative opt-in consent from all parties involved in the conversation—a difficult-to-impossible requirement that would have effectively nipped Gmail’s business model in the bud. “Telling people that their most intimate and private email thoughts to doctors, friends, lovers, and family members are just another direct marketing commodity isn’t the way to promote e-commerce,” Figueroa explained. “At minimum, before someone’s most intimate and private thoughts are converted into a direct marketing opportunity for Google, Google should get everyone’s informed consent.”

Google saw Figueroa’s bill as a direct threat. If it passed, it would set a precedent and perhaps launch a nationwide trend to regulate other parts of the company’s growing for-profit surveillance business model. So Google did what any other huge company caught in the crosshairs of a prospective regulatory crusade does in our political system: it mounted a furious and sleazy public relations counteroffensive.

Google’s senior executives may have been fond of repeating the company’s now quaint-sounding “Don’t Be Evil” slogan, but in legislative terms, they were making evil a cottage industry. First, they assembled a team of lobbyists to influence the media and put pressure on Figueroa. Sergey Brin paid her a personal visit. Google even called in the nation’s uber-wonk, Al Gore, who had signed on as one of the company’s shadow advisers. Like some kind of cyber-age mafia don, Gore called Figueroa in for a private meeting in his suite at the San Francisco Ritz Carlton to talk some sense into her.

And here’s where EFF showed its true colors. The group published a string of blog posts and communiqués that attacked Figueroa and her bill, painting her staff as ignorant and out of their depth. Leading the publicity charge was Wentworth, who, as it turned out, would jump ship the following year for a “strategic communications” position at Google. She called the proposed legislation “poorly conceived” and “anti-Gmail” (apparently already a self-evident epithet in EFF circles). She also trotted out an influential roster of EFF experts who argued that regulating Google wouldn’t remedy privacy issues online. What was really needed, these tech savants insisted, was a renewed initiative to strengthen and pass laws that restricted the government from spying on us. In other words, EFF had no problem with corporate surveillance: companies like Google were our friends and protectors. The government—that was the bad hombre here. Focus on it.

I don't know whether it is illegal for someone to open a letter addressed to you or not, in the country you live, but this is pretty important. If the information presented here is accurate, this is not simply EFF focusing on the government, its EFF actively resisting similar rules to be applied on e-mail as those applied on regular mail. Would anyone use any of the non-electronic mail service providers or courier services if it was a given that for each piece of mail sent, there would be exactly one open and read, shared with multiple other parties besides the sender and receiver?

It seems to me that this is the whole point of this (quite long, but interesting) article and this instance probably illustrates it better than any other chosen to discuss in the article.

Ah, fellow runner..

Less dirty search (doesn't even classify as quick), more recent, better documented, with some testing, without the console logs (lol what). Take a look.. There are actually quite few attempts, depending on what stack you are searching for and how you search.

Well, that's just my experience with building software. Not sure if it has any educational value as such..

It's pretty common for people who are not part of the design/implementation to underestimate the difficulty and the complexity, to mistake reluctance or delays as incompetence or indifference. It's also quite common even for people who are part of the design/implementation to underestimate the complexity or already implemented assumptions that have to be adjusted, which almost always leads to defective software. Add to that the fact that it is an open source project currently at 0.18.4 version and you can explain all of the issues without attributing ill intend to anyone.

Getting nasty comments when you repeatedly point out that you are not familiar with the process would just be unfair. Besides, it's the user experience (moderators/admins/hosts are users too) you are commenting on, making a completely valid point about the importance of moderation in building a community.

I really wish it wasn't built on rust so I could actually be helpful :-/

A database that’s crummy (but functional) is an important issue, but one that seems like it can wait.

That's often the problem with how software is perceived by a user. Simple functionality might introduce complexity in already existing functionality effectively breaking it at the scale it is supposed to support. The technical aspect of a piece of software will always seem secondary for the end user, regardless of the functionality it appears to be second to. That's only logical. You don't care about a certain metal's properties when you buy a knife, you care about the kind of cuts it can perform.

My issue with the project is that it's mostly written in a language that I am not familiar with, and much of the scale it's built to support is over a protocol that is also new to me. I can't really judge whether the issues (especially content removal and how actions are synchronized between separate federated instances) are a database issue, a protocol issue, a sub optimal approach to the complexity or even just doable in the current context.

Designing and implementing properly and fully working transparent software is always hard. And in new protocols and contexts is even more so.

You are correct though, these things are not important for the people who use it. What is important for the users is how the piece of software can, and if it can, allow for the use they want to make of it.