Yes, that will happen when the “problem” lives solely between your ears.
Yes, that will happen when the “problem” lives solely between your ears.
You are more than welcome to block any and all content from that instance. You can do this by going under your user settings and clicking on the “Blocks” tab and searching for lemmy.ml in the Block Instance section. That’s the thing about Federated content. You have the power to selectively engage with the content of your choosing. You don’t get to quarantine others because there is no centralized authority that gets to say “your instance gets stuck in an internet ghetto where it isn’t allowed to interact with other users.” You have to quarantine yourself by excluding content. If that doesn’t work for you, then maybe it’s less that you dislike their authoritarian ideology and more that it isn’t the same flavor as your own.
It’s the Vampire Castle phenomenon of online leftist spaces. One dev and instance admin of Lemmy has problematic personal beliefs, so now we aren’t allowed to be on Lemmy anymore because it’s failed an ideological purity test that OP decided for the rest of us. In other news, Jimmy Wales, the founder of Wikipedia, is a hardcore Ayn Rand style freemarket libertarian, so I guess we should all ditch wikipedia and each buy a 400 pound Encyclopedia Britannica set. Because that’ll show him to believe things I think are terrible.
So your assertions here are the following:
So, point by point:
If you want to hate religion because you’re bitter, that’s fine. You can feel about religion any way that you want. But don’t be offended when you bring it up out of nowhere and someone tells you that your comments are irrelevant to the current discussion.
The world doesn’t revolve around your personal bitterness.
A lot of it probably comes from deeply negative personal experiences, combined with a general propensity for people to apply a categorical belief to particular experiences. People who were treated badly by a particular group of Christians, or people who see and hear about certain Christians advocating for some terrible politician or political goal, are applying a generalized belief to how all Christians act, and potentially to all religion in general. It’s much harder to accept that the world is a deeply complicated and messy place and that religion and religious belief is a much more complex element of human civilization, culture, and personal identity than what many people would care to acknowledge.
I already mentioned that shoehorning criticism of religion into conversations that were unrelated came across as bitter and myopic. Your point was, essentially, that a lot of people are bitter towards Christianity, which is implied by my own observation. If you have nothing to add beyond restating what was already said by the person to whom you are replying, then I would suggest saving yourself the time in the future and just clicking the up arrow. Or doing literally nothing. Either of those are fine options.
Sure, and that’s terrible, but from a different perspective, most of these beliefs and behaviors you’ve identified would persist without religious institutions and their proponents formalizing them as policy. Religion can give people a way to justify a lot of the terrible beliefs that they had internalized anyway, because it’s part of the dominant culture. But misogyny, racism, homophobia, transphobia, classism, xenophobia, and moral hypocrisy aren’t caused by religion or religious beliefs, any more so than atheism or agnosticism causes people to be tolerant or accepting of others in spite of their differences. And that’s a foundational premise to many of the criticisms of religion I see on Lemmy. But it’s just objectively wrong. If you want to look at a historical example of the productive power of religion, look no further than the SCLC (Southern Christian Leadership Conference), which was one of, if not the most significant, political and religious organizations of the Civil Rights movement. It helped to organize people into a fighting force for real progressive change and it did so by way of lines of communication between black congregations across the country. For even more examples of religion as a tool of social progress, I recommend the wikipedia page on Liberation Theology.
You don’t even need to involve churches.
There are plenty of valid complaints about (many) American religious institutions, but the constant shoe-horning in of complaints about religion in unrelated posts that I see on Lemmy comes across as bitter and myopic.
This is a good question. The answer is probably “a few years old” at the least. I went hunting for the UPC code on the back label and found this website, which indicates its last recorded scan was some time in 2021. It’s likely this product is simply no longer manufactured and sold by them. Probably by virtue of a lack of demand or other considerations.
Yeah, I didn’t know that until very recently, and that was because of an anime I was watching.
Oh boy a semantic argument
It turns out the language you use can be semantically ambiguous or misleading if you phrase it incorrectly. Today you learned.
And any web dev who remotely understands the point of CSP and why it was created, should instantly have alarm bells going off at the concept of triggering arbitrary ajax via html attributes.
Oh, did you finally manage to fucking Google how HTMX works so you could fish for more reasons to say it’s unsafe? What you’re describing is not a particular concern to HTMX. If an attacker can inject HTML into your page (for example, through an XSS vulnerability), they could potentially set up HTMX attributes to make requests to any endpoint, including endpoints designed to collect sensitive information. But, and this is very important, this is not a unique issue to HTMX; it’s a general security concern related to XSS vulnerabilities and improper CSP configurations.
Do you know what the correct cure for that is?
PROPER CSP CONFIGURATION.
“HTMX doesn’t bypass CSP! It just (proceeds to describe the exact mechanism by which it bypasses CSP)”
Do you genuinely not understand that CSP works on the browser API level? It doesn’t check to see if your JavaScript contains reference to disallowed endpoints and then prevents it from running. I don’t know how you “think” CSP operates, but what happens is this: The browser exposes an API to allow JavaScript to make HTTP requests - specifically XMLHttpRequest and fetch(). What CSP does is tell the browser “Hey, if you get an API request via XMLHttpRequest or fetch to a disallowed endpoint, don’t fucking issue it.” That’s it. HTMX does not magically bypass the underlying CSP mechanism, because those directives operate on a level beyond HTMX’s (or any JS library’s) influence BY DESIGN. You cannot bypass if it if’s properly configured. Two very serious questions: what part of this is confusing to you? And, have you ever tested this yourself in any capacity to even see if what you’re claiming is even true? Because I have tested it and CSP will block ANY HTMX issued request that is not allowed by CSP’s connect-src directive, assuming that’s set.
CSP works on the browser API level - all HTMX does is what you could do yourself with any AJAX: send an HTTP request to an endpoint. If the CSP disallows that endpoint, it will fail.
removed by mod
Just to be clear, are you talking about some kind of templating library that literally transpiles all the htmx logic and instead packs it into individual ajax logic in js files “per element”, such that you don’t need to serve htmx client side and instead you pre-transpile all the ajax logic out to separate files?
My brother in Christ, what the fuck are you talking about “transpiling HTMX” and “serving HTMX client side?” You don’t “serve” HTMX and there’s nothing to “transpile into JavaScript.” It is JavaScript. That’s like saying you “serve React client side” and “transpile JavaScript into more JavaScript.” Jesus, I feel like I’m taking crazy pills.
Cause the very start of my statements was that if we had something like that then HTMX would be fine, as a templating lib that transpiled out to html+js.
Oh, okay, so you don’t actually know what HTMX is or how it works, then? Because HTMX (https://htmx.org/) is a JavaScript library. Like, literally just a JavaScript library. It’s like…4000 lines of JavaScript. In fact you can read the source code for it here: https://github.com/bigskysoftware/htmx/blob/master/src/htmx.js. For some…insane reason you seem to think HTMX is its own language. It’s not. It’s…just a JavaScript library. There is no other language called HTMX. There is no other mechanism or tool called HTMX. No implementation or protocol or ANYTHING else. It’s just a small JavaScript library.
invoke arbitrary logic with html attributes
Once again, HTMX enhances HTML with various attributes declaratively. It utilizes custom data attributes in HTML (like hx-get, hx-post) to specify how elements on the page should behave - essentially, how and where to fetch data or submit forms without a full page reload. This is a form of declarative programming that tells the htmx.js library (which is just doing fucking AJAX) what to do when certain events occur (e.g., a click or a form submission). The actions (like the actual requesting of data from an endpoint) are performed by the code in htmx.js.
This is a fancy way of saying “if you stick an hx-get attribute on a button, then you can just say where you want a GET request to go to and what element you want updated with the HTML returned from it and htmx.js will parse that out on page load and set an event listener for the button click to know when to initiate an AJAX request to the defined endpoint.” If you had an hx-get attribute in an element in a page and that page didn’t have the htmx.js library loaded it would do literally nothing.
And, once again, HTMX, being a JavaScript library, operates under the same security constraints as any JavaScript executed in the browser. This means that:
HTMX enables arbitrary invocation of ANY api endpoint with cookies included, through html attributes, which inherently can’t be covered by Content Security Policy
I want you to please explain how HTMX bypasses the Content Security Policy connect-src directive, or any -src directive, for that matter, assuming it is specified (which it should be). Because I’m genuinely curious why the HTMX dev team would include a section on CSP in their docs if it did literally nothing, as you say.
Actually, as an even more basic question…you do know that HTMX is literally just an AJAX library, right? It doesn’t actually “do” anything via HTML attributes. The additional HTMX attributes, like hx-get, hx-post, etc. just tells HTMX where and how to make the API requests. These requests are executed by the browser’s native fetch or XMLHttpRequest APIs, depending on compatibility and implementation. Therefore, HTMX is subject to the same security constraints and policies as any other JavaScript-based operation that makes HTTP requests. Which also, by definition, means that it adheres to the Content Security Policy directives configured for that website.
In other words, an HTML button element with hx-get=“https://www.some-endpoint.com/” on it would eventually translate into
const xhr = new XMLHttpRequest();
xhr.open("GET", "https://www.some-endpoint.com/");
xhr.send();
on click.
You do understand that, right?
“Billionaire has shitty beliefs. In other news, the weather in London is still complete ass.”
The preferred term is NaMP - Not a Magical Person/Non-Magical Person. You could also say “Person of Non-Magic,” but it’s hard to pronounce “ponm.”
number puzzles that need to be solved.
In JK Rowling’s mind the number puzzles are things like “How many genders are there?”
The correct answer, of course, is “Fuck you, JK Rowling, that’s how many.”
Remember when shootings were so rare that a shooting happening one time at one place was enough to spawn a lasting phrase in American English? Simply fascinating how the times have changed.
As a note, the Israelites would in later generations go on to kill a shitload of people. It’s one of those things where it seems like the Bible only really considers it murder if God doesn’t sanction it. It’s honestly one of the many sticking points that makes Abrahamic religions a hard sell for modern individuals. That said, if you look at it from a historical perspective, it really comes across more like a religious version of the Code of Hammurabi. It’s less “don’t kill” as a philosophical or religious position and more about sanctions against killing in a practical legal sense. A functioning society has laws that formally govern behavior and the Israelites were essentially an ecclesiarchy, with Moses being both head of state and high priest. The same laws that governed social life were always going to intersect with laws that governed spiritual life.