133arc585 @ 133arc585 @lemmy.ml

Posts

4

Comments

368

Joined

2 yr. ago

It's in the blocked word list because it's misogynist. The fact that it's used so commonly with no second thought is disturbing.

I don't know if I agree with the blocked word list being enforced, but I definitely have a problem with rampant misogynist, ableist, and otherwise discriminatory language used with no thought.

Was that supposed to be some sort of joke or do you actually not know Orwell himself was: a rapist, a snitch, a plagiarist, and a racist? One man, four horrible qualities.

I see what you're saying but I still disagree. If you are making that much money and living paycheck to paycheck, it's your own fault and is a lack of self control or money management knowledge. If you're making $7.25 an hour and living paycheck to paycheck, no amount of self control and money management knowledge will mean you aren't living paycheck to paycheck. Living paycheck to paycheck is a personal failing when you're in the top 1% of earners in the country.

I meant not popular as in they don't have as much foot traffic as they did a few decades ago. Many exist, but the number of malls that don't feel "dead" is pretty low in my experience.

Mullvad does not allow port forwarding.

They announced on May 29th that they would not allow new port forwarding. On July 1st, all existing port forwarding was disabled. Since then, Mullvad no longer allows port forwarding.

No. You are building a massive strawman. I never even said a word about medics.

I guess you don't understand how this works. I'm not building a strawman, as I'm literally describing the Geneva Convention's justification for why your opinion is nonsensical to hold. I'm simply asking you to extend your "logic" to an identical situation that, in my opinion, is more enlightening as to why your argument is faulty. They are both non-combat roles, and the justification for protecting them in a war setting is identical.

You conveniently ignore everything Russia has done. Tell me, is Russia following Geneva conventions and Nuremberg principles?

I see that you don't actually care to have an honest discussion. I haven't mentioned anything Russia has done; I haven't justified anything Russia has done. You think me pointing out that Ukraine has done something wrong, and that your defense of that is bad, is somehow equivalent to defending Russia.

It seems, unless you want to try to actually respond to the points I've raised, that you're content in your disagreement with the Geneva Convention. As such, your faked concern about Russia's supposed violation of the Geneva Convention is just that: faked.

I think there are many other versions of the same story that aren't plagiarized, aren't written by horrible humans, and are also better written.

Personally, I'm fond of Aldous Huxley's Brave New World. I haven't read it, but you can skip Orwell's plagiarizing and go to the source and read Yevgeny Zamyatin's We.

You can thank Meta for that. They sued the registrar managing several ccTLDs, including .ml, .ga, .gq, .cf, and .tk. Meta even goes so far to fabricate a conspiracy theory about the registrar being part of a cybercriminal ring; they feign concern and wreak havoc.

So you ignore the actual argument I made, how your logic, evenly applied, would apply to killing medics as well. And you ignore the fact that your opinion here is against the Geneva Convention. You conveniently ignore the part where you don't have to target them to have killing them be a problem; killing them is the problem. And your only retort is whataboutism: "yeah but Russia does bad".

Take a look back at my comment. Apply the reasoning, and tell me: do you think we should allow killing enemy medics? If not, explain to me your contradictory stance.

If they are fabricating propaganda, why would they go to the front line? Why risk their life when, according to you, they're just going to make everything up and say what they want anyway? Seems like the easier, safer, and more effective propaganda would simply not involve going to the front line and instead sitting in a news room, with some CGI if they're feeling fancy, or using old footage if they're not, and propagating that?

Moreover, just because you don't like what a journalist is reporting, you can't condone killing journalists.

Are you also saying it'd be ok to kill Russian medics, since after all, they're just saving the lives of "Russian war criminals"? Should we suddenly open up the rules of war to allow killing medics on the side we're fighting? The logic you're using to defend the killing of journalists, when applied evenly, would say yes, we should allow killing of enemy medics.

Fortunately though, the Geneva Convention disagrees with your faulty logic and recognizes that non-combat roles including medics and journalists can not be targeted and indeed care should be taken to not inadvertently kill them.

Most countries except for the US

They still exist in the USA as well. They just aren't popular.

No, as I realized and clarified in a comment of mine down this thread a bit,

Climate records tumble,

Here, "climate records" is the object of the verb "tumble". That is, the thing that is "tumbling" are "climate records".

I agree it's a poor choice of wording for a headline but it is clear what is doing the tumbling on subsequent reads.

Ah I see you mentioned the cuts are only a few seconds long. This wouldn't catch that very well.

If you have a server outside of your network you could simply hold open a TCP connection and report when it breaks, but I'll admit at that point it's outside of what I've had to deal with.

Depends on how much you want to set up. For my purposes, I just check for connectivity every minute, and record true or false as a new row in a sqlite database if there is connectivity.

This is what I use on my raspberry pi,

 py

    
#!/usr/bin/env python3
from datetime import datetime
import sqlite3
import socket
from pathlib import Path

try:
    host = socket.gethostbyname("one.one.one.one")
    s = socket.create_connection((host, 80), 2)
    s.close()
    connected = True
except:
    connected = False
timestamp = datetime.now().isoformat()

db_file = Path(__file__).resolve().parent / 'Database.sqlite3'
conn = sqlite3.connect(db_file)
curs = conn.cursor()
curs.execute('''CREATE TABLE IF NOT EXISTS checks (id INTEGER PRIMARY KEY AUTOINCREMENT, timestamp TEXT, connected INTEGER)>
curs.execute('''INSERT INTO checks (timestamp, connected) VALUES (?, ?);''', (timestamp, 1 if connected else 0))
conn.commit()
conn.close()

  

and I just have a crontab entry * * * * * ~/connectivity_check/check.py >/dev/null 2>&1 to run it every minute.

Then I just check for recent disconnects via:

 sh

    
$ sqlite3 ./connectivity_check/Database.sqlite3 'select count(*) from checks where connected = 0 order by timestamp desc;'

  

Obviously, it's not as full-featured as something with configurable options or a web UI etc, but for my purposes, it does exactly what I need with absolutely zero overhead.

What a weird take. You're allowed to pay for whatever you'd like. Personally, I can't afford to pay for any JetBrains product, even if I wanted to.

Not only are there alternatives which may be better overall or better suited to someone's needs, that wasn't even my point. My point was more that it is only temporarily free, and so the parent commenter's comment of "it's free" should be taken with a grain of salt if you're considering the product.

Moreover, we're in the Open Source community: Fleet is neither free nor open source, and pointing that out here is relevant.

Quoting JetBrains,

Fleet is free to use during the public preview

(emphasis mine)

So it is only temporarily free. Once it's polished it will no longer be free. Better to not get tied in to something that will be taken away from you before long.

But nothing is falling, all of the temperature records are rising.

I see what you're saying. I had taken the use to mean the situation is tumbling, not the temperatures. But upon a closer reading (of the title specifically) it seems a more reasonable interpretation of the word tumble is:

Climate records tumble,

The object of the verb 'tumble' is "climate records". That is, the climate records are tumbling. A tumbling record is one which has fallen over and been surpassed. So what they're saying by using the word "tumble" is: previous climate records have fallen over and been surpassed.

I do agree it's a weird word choice, but I don't think it's wrong or even playing on a potential uncommon secondary definition. It's not saying temperatures have tumbled, but rather records have tumbled.

Reading your comment history, it seems it would benefit you greatly to read history. The simple reaction you just had to the parent comment was born out of historical ignorance: you don't know the history of the region, so when you see a claim that you don't like the sound of (despite it being true), your reaction is to assume the other person is divorced from reality. In actuality, by nature of not knowing history, you are detached from reality.

In hindsight, yes. But there was no indiciation ahead of time that this situation would happen or was likely to happen. In fact, there was no more reason to believe a free ccTLD was any more likely than a paid ccTLD to cause a problem. The problem arises because a ccTLD's host country can choose to remove any domain it wants, paid or not. One could argue that using a ccTLD at all was a mistake, but you'd have to look at precedent for ccTLD's country's doing this and see if it happens often or not.

If a condition is worsening (a "fall") "tumble" applies just fine. Indeed, "tumble" is just a way to say "falling rapidly" in this context.

The reason "tumble" (and its notion of "fall") is applicable is because the situation is worsening. If it was rapidly improving, nobody would say "tumble"; it's not simply that it is occurring rapidly.