home.social

Search

1000 results for “not_gagarin”

  1. the #ecb while residing in #germany does not have to follow #brd #law

    is it true the ECB does not have to follow German law?
    Duck.ai said

    Not exactly. The ECB is an EU institution, so when it carries out EU-assigned tasks, it is governed primarily by EU treaties and EU law—not simply by German law....

    but EU law is above German BRD law?
    Duck.ai said

    Generally, yes: where #EU law applies and conflicts with #German federal law, EU law takes precedence. #wtf

  2. ☁️🌈☁️🪽😇🪽🕊️✝️👑💦🌊🤽🏿‍♀️💒🛐🫂👐🫶🏩🌪️🍥🌀🥴🫧🆘😵🌊🫍🐳🐋🪼🦑🐟🤔🌊🌪️🌀👇🌏🌐🩵💁🏼*[FRIENDS 😨*”YET GOD DID NOT ANSWER ME!”🥴🤔❓🙇🏿*SO THE NEXT THING I SAID TO GOD IS “OK!*IF THIS IS WHERE YOU WANT ME TO STAY THAN I SURRENDER TO YOUR WILL!*& ACCEPT IT LORD!”*& BEFORE I HAD COULD HAVE ANOTHER THOUGHT GOD SPIT ME OUT OF THE WATER ONTO THE LAVA ROCKS!🏖️👉

    Hebrews 11
    #Christ #Jesus #Holy #Spirit #Pray #Heaven #Truth #Personal #Relationship #With #God #Faith #Means #being #sure #of #what #we #hope #for #convinced #of #things #we #do #not #see

  3. The Internet That Remembers You're Not a Product

    A system built so your identity, posts, and followers travel with you across apps, sovereign, portable, and finally yours.

    Watch: youtube.com/shorts/bU7JLxSnW9U
    #Nostr #DigitalIdentity #Decentralization #Web3

  4. buying concert tickets and then ending up not going to the show is kind of becoming my new normal. why can't bands just come play at my house, it's too much effort these days to drag myself across town.

  5. Upgrading FastMCP to 4.1.2 does not close its OAuth credential leak. You also have to pass issuer=.

    In 4.0.0 to 4.1.1, the client-credentials and private-key-JWT providers used whatever authorization server an MCP server advertised, so a hostile server could receive your client secret. In 4.1.2, omitting issuer still works, with only a deprecation warning. Set it, then rotate the secret.

    github.com/advisories/GHSA-vqq

    #MCP #AIAgents #Cybersecurity #Python

  6. 87-year-old customer says she's not eaten all day because she's so stressed trying to .

    In a 90-minute phone call – and with English not her first language – she followed diligently step-by-step as I guided her to restart the iPad, try the iPhone instead, restart the , restart the router, rejoin the printer to Wi-Fi, factory reset the printer, check for printer firmware updates, and factory reset the router. All to no avail.

    Now I'm off to find her a new printer, and she's promised she'll have dinner.

    Dear tech bros: we don't want AI, we don't want smart everything, we don't want a new version every year. We want stuff that works.

  7. The phonograph produces a primal sound not by notation but as a metaphor, an absolute transfer of anatomical traces.

  8. #SixYearsAgoToday #AreWeGreatYet

    Try replacing “We’re not going to control the pandemic” with “We don’t care about your lives.”

    October 25, 2020 – “We’re not going to control the pandemic,” Trump’s chief of staff Mark Meadows told CNN — suggesting that the Trump administration had given up on any attempt to stem the spread of the virus.

    politico.com/news/2020/10/25/w

    #TrumpMustGo #SaddamInsane #RepublicansOwnThis #NoRepublicansEverAgain #USPol

  9. Taxpayers Alliance Against Genocide (TAAG): “We Will Not be Intimidated!”

    Article republished by Jerry Alatalo | October 25, 2026

    [Editor’s note: The non-responses of U.S. President Donald Trump and Israel Prime Minister Benjamin Netanyahu to this significant international law development have been widely described by veteran world affairs observers as being akin to deer-in-headlights. Please share the article far and wide. Please feel free to respond in the comments. Thank you very much. Peace.]

    ***

    We Beat The Trump Administration In Court

    October 24, 2026

    Tariq Ra’ouf, Mondoweiss.

    Now we’re going to the ICC to hold the U.S. accountable for the Gaza genocide.

    A recent lawsuit successfully challenged the Trump administration’s assault on the International Criminal Court. Now, families like mine, whose relatives have been killed with U.S.-supplied weapons in Gaza, might finally have a chance at justice.

    Over the course of the last three years, my family has lost 49 family members in Gaza. Their bodies were torn apart by shrapnel, crushed by falling buildings, and mutilated by bullets and munitions made and provided by the United States of America. Now, the U.S. is trying to dismantle the International Criminal Court, the only international court that can criminally prosecute U.S. officials for aiding and enabling genocide, by sanctioning the Court and attempting to intimidate anyone, including U.S. citizens, from working with them. So, in response, I joined others to sue this administration in order to take them to the very court they’re trying to destroy.

    I’m a Palestinian-American organizer, and I helped establish Taxpayers Alliance Against Genocide (TAAG), which recently partnered with Democracy for the Arab World Now (DAWN) to sue the Trump administration so we can continue much-needed legal and advocacy work. Over the course of over a year, TAAG worked with an international legal team to prepare evidence against top U.S. officials for aiding and enabling the genocide of my people, but up until now, we haven’t been able to submit our evidence to the ICC because of this administration’s attacks and sanctions on the court and its judges.

    Thankfully, that will now change after we successfully challenged the Trump administration in court. On October 13 we won a preliminary injunction that blocks this administration from being able to target our groups for working with sanctioned parties, clearing the way for us to proceed to the ICC. For the first time since the genocide started, I am beginning to see a glimmer of hope that justice will be found for the dozens of family members I have lost in Gaza.

    The Trump administration’s war on the ICC

    Long before the Trump administration sanctioned the entirety of the International Criminal Court (ICC) on October 9, it first enacted Executive Order 14203 in February of 2025. This executive order granted administration officials the ability to sanction foreign nationals for supporting the ICC’s investigations into U.S. and Israeli parties guilty of committing war crimes and their complicity in genocide. Under this Executive Order (EO) , the Trump administration also sanctioned leading Palestinian human rights groups al-Haq, al-Mezan, and the Palestinian Center for Human Rights (PCHR), as well as the UN Special Rapporteur for the Human Rights Situation on the Occupied Palestinian Territory, Francesca Albanese, along with other ICC officials.

    What many people don’t know is that the EO that allowed the administration to sanction these parties doesn’t only go after foreign nationals, it also makes it a federal offense — punishable by a $1 million dollar fine and/or 20 years in prison — for anyone, including American citizens, who provides or receives a “service” to or from a sanctioned party. This provision of the EO is exactly why TAAG and DAWN took this administration to court: Our lawsuit argued that the EO violates our First Amendment rights as American citizens to speak, associate, and engage in Palestine-related human rights advocacy with these parties. As a founding member of TAAG, I can tell you firsthand how these sanctions have prevented us and organizations like DAWN from being able to continue our work sharing evidence and advocacy ideas with people like Albanese and ICC officials, because the definition of “service” is so broad and undefined — the US can interpret it as being anything that confers a benefit to the recipient.

    In an October 9 video of Marco Rubio announcing the actions against the ICC, he tries defending the administration’s actions by calling the ICC a “rogue court,” which the U.S. is “not subject to the jurisdiction of.” But Rubio leaves out a fundamental principle of international law: A country does not have to join the ICC for its nationals to fall within the Court’s jurisdiction.

    If a country that is not a State Party to the Rome Statute commits a war crime on the lands of a country that is a state party, the perpetrator of that crime can be investigated. Given that Palestine is a State Party to the Rome Statute, and that Gaza (and the West Bank) are classified as Occupied Palestinian Territories by the United Nations, the ICC has every right to investigate and prosecute the United States and Israel for the insurmountable war crimes committed against my family members and thousands of other innocent civilians.

    It is clear that the only “protections” this administration are seeking are for the citizens responsible for aiding and abetting war crimes, which after three years, we have plenty of evidence of. Anthony Aguilar, a retired US special forces officer and whistleblower who resigned from his work with the Gaza Humanitarian Foundation (GHF) aid distribution centers in Gaza, has gone on record saying he saw the Israeli Defense Forces (IDF) shooting at crowds of Palestinians, and in an interview with the BBC says he saw Israeli and American military forces of the GHF using an “indiscriminate and unnecessary force against a civilian population, an unarmed, starving population.”

    Rubio consistently mentions the idea of “protecting American citizens” from investigations by the ICC, but the citizens he is referring to are the ones committing the war crimes he doesn’t want investigated. What about American citizens whose families have been killed with U.S.-supplied weapons? Who protects our right to seek justice?

    In sanctioning the entirety of the ICC, the Trump administration is not only trying to cripple any attempt to hold them accountable for their war crimes, but they’re also telling American citizens like myself that if you dare to seek justice for the family members you’ve lost, we’ll imprison you.

    The struggle for accountability moves forward

    Now that the courts sided with us in our lawsuit, we are finally able to prepare for the next steps ahead.

    With the injunction in place, TAAG is now moving forward to finalize its evidence submission and plans to imminently send this to the ICC. We are also rallying support, within the US and beyond, for human rights organizations and advocates for the ICC to act responsibly upon this massive collection of evidence, in hopes that more parties take appropriate legal actions where possible. We fundamentally believe that grassroots movements like ours, and so many throughout the world, are the ones who must step up where our leadership has failed, and build the democratic, popular power capable of ensuring that legal action against genocide is taken and enforced.

    We also hope that our actions inspire more American citizens to speak up against this administration and the priorities of our government. I helped found Taxpayers Alliance Against Genocide because I’m sick of our tax dollars being used against my own family in Gaza, while our communities here in the U.S. suffer from a lack of housing, education and healthcare. Those of us within TAAG recognize that we have a duty as American citizens to hold our nation accountable for the war crimes they commit, not just in Gaza but all over the world.  We will not rest until we’ve exhausted every avenue to seek justice and accountability for these war crimes. We will continue collecting evidence, and pursuing every available legal avenue, moving forward with our crucial evidence work for a prospective submission to the ICC and advance our efforts to hold U.S. officials accountable for crimes against humanity.

    We will not be intimidated into abandoning our work, our families, or the principle that no one is above the law.

    ***

    (Source/credit: ScheerPost.com)

    #DonaldTrump #GenocideProsecution #InternationalCriminalCourt #InternationalLaw #PoliticalScience #TAAG #WhatIsTheInternationalCriminalCourt
  10. Even with the squad depth it's not great losing Kadioglu from the defence and Andres from midfield to injuries, with a double-header looming away to Manchester City, 2-0 (56). #BHAFC #LIVBHA

  11. Really it should be Arkansas man not Florida man, IQ of 56 they are basically brain dead lol

  12. CW: very lewd at viewer

    should be in you but you're not here

    #nsfw #boobs #cock #cum

  13. A dropped interception and 3 fumbles not recovered. Man Steelers D cannot catch a break really

    #nfl #herewego

  14. "AG Todd Blanche suggests Corey Lewandowski may not be under investigation after all"

    Evidently Corey Lewandowski has something on Trump.

  15. Another way Mastodon > Bluesky: It's not stuffed with genocide-supporting Zionists and their hand-wringing liberal enablers.

  16. ⚡️Any so-called Russian oppositionist who does not call for Russia's withdrawal from 100 per cent of Ukraine is addicted to the Historical Russia. Podcast: open.spotify.com/show/033ZXAMD

  17. So I was wondering why it is not working. The implementation should be easy and straight forward. Just put in the read and write functions...

    🤦🤦🤦

    Do you spot it? I put the write function in the read callback and the read function in the write callback.

  18. Abbas Araghchi says resumption of war would not change Iran’s policies

    Iranian Foreign Minister Abbas Araghchi. (Image for representational purpose only) | Photo Credit: AP Iran’s Foreign Minister Abbas…
    #EuropeSays #Headlines #News #Europe #Europa #EU #Iran #AbbasAraghchionIranwar #iranuswar #IsraelUSwaronIran #StraitofHormuzblockade #usiranceasefire
    europesays.com/iran/340875/

  19. Half the power of a nightmare is not knowing, it's from a film but I'm not going to say which. You can just fear that it might come visit you at some point* 😈

    I've used a sensitive as when I'd done the final correction to the eyes at the end it creeped me out 😅

    Alt text 47 words

    *If you know, please don't say, as it'll spoil it for others if they watch the film in the future 🙏

    #Cosmictober #KittyDraws #Mastoart #KleineKunstKlasse

  20. The first week after launch is not about ranking. It is about confirming three things: crawlers can reach the site, they are actually fetching it, and the contact path works end to end. Everything else can wait until there is data.

    Day 0, before you tell anyone: four things that block indexing silently


    1. A coming-soon or maintenance mode that is still switched on.
    2. A noindex left over from staging. There are two places: a meta tag in the head, and an X-Robots-Tag response header. Check both. Open the page source and search for noindex, then request the page headers with curl -I. The header is the one people forget.
    3. HTTP auth or a site-wide password still enabled.
    4. The same page reachable on more than one hostname (with and without www, or both protocols) with no redirect between them. Pick one, 301 the other.

    One more, before launch rather than after: put the measurement tag on the site. Analytics installed on day 3 means day 1 and 2 have no data at all.

    Test all of this from a phone on mobile data, not from the office wifi, and not while logged in as an administrator. Logged-in views hide caching and coming-soon behaviour.

    Day 1: verification and submission


    • Add a domain property, verified by a DNS TXT record. It covers every subdomain and both protocols in one property, which matters when you are not yet sure whether the canonical host is www or not.
    • Add a URL-prefix property as well if you want per-protocol reporting. It is a second view of the same data, verified separately.
    • Submit the sitemap once.

    Before submitting, open the sitemap in a browser. It has to load, return 200, be valid XML, and contain only canonical URLs that themselves return 200. No redirects, no 404s, no noindexed pages inside it. A sitemap full of redirects teaches the crawler to distrust the whole file.

    Then URL inspection on a handful of pages, not hundreds: home page, one category or service page, one product page, the contact page. "Request indexing" is a queue entry, not a switch. There is a daily quota and no way to buy more.

    Bing: import from Search Console or verify directly, then submit the sitemap there too. Ten minutes, and it feeds the results that are not Google.

    What not to do in week one: resubmitting the sitemap every morning, requesting indexing for every URL, or deleting and recreating the property because nothing shows on day 2.

    Day 2-4: crawl your own site before the crawlers do


    Check that every key URL returns the status you expect. One line per URL, status code first:

    while read -r u; do
    printf '%s %s\n' "$(curl -s -o /dev/null -w '%{http_code}' -L "$u")" "$u"
    done < urls.txt

    urls.txt is one URL per line in a plain text file: home, top landing pages, contact, the sitemap, robots.txt.

    Then check, on each page:

    • the canonical tag points at that page itself, not at the home page and not at the other hostname
    • internal links use the canonical hostname; one mixed link is enough to create a duplicate
    • the main text is in the HTML source, not injected by JavaScript. View source, not the rendered DOM.

    Fix these now. Crawlers come back, but they come back on their own schedule, not yours.

    Day 3-7: read the access log


    This is the step people skip, and it is the place that shows what actually happened rather than what you submitted.

    Where the file is. On a managed host, the control panel, usually under access logs or raw logs, rotated daily. On your own server, /var/log/nginx/access.log or /var/log/apache2/access.log. Behind a CDN, the origin log shows the CDN's IP addresses, so you need the CDN's own log or an origin header that carries the real client IP.

    Download a couple of days and work on the copy.

    # Who is hitting the site at all
    awk '{print $1}' access.log | sort | uniq -c | sort -rn | head -20

    # How many requests claim to be a crawler
    grep -Eic 'googlebot|bingbot' access.log

    # Which paths the crawler actually fetched, busiest first
    grep -Ei 'googlebot' access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

    # What we served it
    grep -Ei 'googlebot' access.log | awk '{print $9}' | sort | uniq -c | sort -rn

    The field numbers ($1, $7, $9) assume the combined log format: client IP, identity, user, timestamp, request, status, bytes, referrer, user agent. Check the first line of the file and the server config before trusting them.

    A user agent proves nothing. Anyone can send the word Googlebot. Verify the IP by reverse lookup, then forward-resolve the name it returns and confirm it comes back to the same IP:

    host 66.249.66.1
    # the returned name should sit under googlebot.com or google.com
    host <the-name-it-returned>

    If either lookup fails, or the forward lookup does not return the original IP, that hit was somebody else. Usually a scraper or a monitoring service.

    What real crawling looks like: more than one hit, spread over several days; requests for HTML pages rather than only images and CSS; 200 responses; and a spread of URLs that includes internal pages, not just the home page.

    What it does not look like: a single hit on the home page, a run of hits on the login path, or hits only on assets. Those are fetchers and scanners, not indexing.

    The self-inflicted block. If you switched on a firewall bot rule, a rate limit, or a security feature that blocks suspicious traffic during launch week, check it before concluding anything about the index. The log will show 403s or 429s served to a crawler. That is your own rule, not a search engine decision.

    Inquiries: prove the path works end to end


    Submit the form yourself on launch day, from a network that is not yours, using a mailbox you control. Confirm four separate things:

    1. the thank-you message appears
    2. the notification email arrives
    3. the entry is stored somewhere you can query
    4. the sender address passes SPF, DKIM and DMARC for your domain

    The email is the fragile part. It can fail while the form still looks fine to the visitor. Check the spam folder, then check the host's mail log for the message ID. If the mail path turns out to be unreliable, at least store every submission so nothing is lost.

    Server-side proof that a submission reached you, even when the email did not:

    grep 'POST ' access.log | awk '{print $7, $9}' | sort | uniq -c | sort -rn | head

    A 200 on the form handler means the data arrived somewhere. A 500 means the handler is failing and the visitor saw an error or a blank page. A 429 means your own rate limit ate a real inquiry.

    Separating noise from a real inquiry. Noise usually looks like this: the same IP hitting the handler several times in a few minutes, fields that are empty or obviously generated, a message body that is only a link, a referrer from a directory site. A real one usually has a company name you can look up, a reply-to address that matches the domain in the message, and a specific question about a specific thing.

    That is a set of heuristics, not a rule. Read the message.

    The week-one sheet


    One place, filled in daily. Five minutes a day.

    WhatWhereNormal in week onePages known / indexedSearch Console pages reporta small number, growing slowlyCrawl requestsaccess log, filtered by verified crawler IPsa handful per day, spread across URLs4xx / 5xx on canonical URLsaccess logclose to zeroForm POSTsaccess logequals the number of inquiries you receivedInquiriesinbox or a shared sheetany number, including zeroTop referrersanalyticsmostly direct and your own links early on


    The form POST count and the inquiry count should match. If they do not, you have a delivery problem, not a traffic problem.

    What not to conclude in week one


    • Zero indexed pages on day 3 is not a penalty.
    • Zero inquiries from fifteen visitors is not a conversion problem. It is a traffic problem, and it is too early to see either.
    • Do not rewrite the site on five days of data.
    • Do not resubmit anything twice. Once is the instruction; the second time is noise in your own process.

    The whole first week is a verification exercise: is the door open, is anyone walking through it, and does the contact path actually deliver. Everything after that is content, which runs on a much slower clock.#seo #startup #webdev #software #coding #development #engineering #inclusive #community
    Launch week: what to submit, what the logs should show, and how to tell a real inquiry from noise

  21. it feels like I did not sleep at all tonight, thanks to the storm. :blobcatsnapped:

Share on Mastodon

Enter the server where you have an account.