home.social

Search

28 results for “Wijfi”

  1. Comparativa del ESP32-C6 y el ESP32-C3: Wi-Fi 6, Thread y Zigbee, memoria, pines, consumo, precio y soporte en Arduino. Cuándo elegir cada uno.#spanish #esp32c6 #esp32c3 #wifi6 #software #coding #development #engineering #inclusive #community
    ESP32-C6 vs ESP32-C3: Wi-Fi 6 y Thread, ¿vale la pena el cambio?
  2. Ukraine bolted wifi extenders onto bomber drones because real aircraft can't survive the sky anymore. Range solved. Now Russia hunts the repeater instead of the pilot. Entropy relocated one hop.
    businessinsider.com/ukraine-si

  3. I thought about going around offering free wifi or an ISP service maubahahaha

  4. XD I think the idea of recording all wifi near me fun, everything them trying to map moving. You can't hide from me I see 🙈

  5. Der beste Weg um zu sparen, ist nur noch zu nutzen.

  6. TIL only 12 of the largest stations in Belgium actually have wifi... that's wild.. I somehow assumed majority atleast had it. #nmbs

  7. It's definitely safe to update my proxmox server from 8 to 9 over an ssh connection on conference wifi, right?

  8. Minor updates here; got uboot -> limine going, working wifi, working drm with brightness and display off, working on touch panel atm. Not sure wtf to do with A13 GPU :'(

  9. Interesting how tech companies have fnally figured out you csn use any wavelength as radar/xrays

    #tech #surveillance #router #wifi

  10. It will be called the

    WHY THE FUCK DID NO ONE FUND THIS FUND

    WFNOFTF pronounced wiffinofftiff

  11. Heute ganz frühes #Homeoffice gemacht. Wenn dann der #ICE107 vernünftiges WiFi hat, geht's später mit #mobilerArbeit weiter.

  12. NetWizard (2.0.0) for esp32/rp2040 by Ayush Sharma

    ➡️ github.com/ayushsharma82/NetWi

    An easy-to-use yet powerful WiFi manager and captive portal library for wireless microcontrollers.

  13. Your home automation and network setup is a mess, and a significant security risk. Camera system and IoT on your flat, default subnet? With the default Netgear wifi password? 🫣 When was the last time you rolled your passwords or WiFi authentication passwords? When was the last time your router firmware was updated? 😩

  14. 🔄 SteamOS - 3.9 Update

    SteamOS 3.9.5 updates Arch base and Plasma 6.7.3, fixes WiFi and VRR issues, adds kernel 7.2 and default wpa_supplicant, plus early hibernation work

    1/2

    #Linux #LinuxGaming #PCGaming #Steam #ValveSoftware #LegionGo2 #LegionGoS #SteamDeck #SteamFrame #SteamMachine #SteamOS

  15. esp_abus (0.0.7) for esp8266/esp32 by Daniel Gangl

    ➡️ github.com/killer0071234/esp_a

    ABUS Socket Communication library for PLCs (Cybro-2 and Cybro-3) from Cybrotech and ESP32 / ESP8266 over WiFi

  16. In addition, there is an app if you need to print from your phone... And the printer is 100% wifi compatible.
    The ONLY complaint I have is that it doesn't come with a dedicated printer cable. And I have learned over the last decade that printer Wi-Fi has 4 prospective problems.
    1. If wifi isn't strong enough, connections are iffy. And many printers are truly only designed for Wi-Fi. The fact that they no longer include a printer cable is their way of pushing you to Wi-Fi printing.
    2. Wi-Fi traffic seems to heavily affect Wi-Fi signal strength, which makes #1 significantly more problematic.
    3. Ink subscriptions (especially after cancellation) will negatively influence ease of use. The manufacturer swears that subscriptions are not mandatory, but they do everything in their power to make the non-subsciption experience so unpleasant that most people will just keep the subscription to avoid the hoop-jumping requirements, to exit the subscription.
    But I happened to have the 10ft one I bought for the prior printer, because, after living in a lot of places where the WiFi is iffy, I prefer old school.
    4. Wi-Fi is hackable, most printer Wi-Fi is unsecured, and all printers keep a log. If I wanted the world to know what I am printing, I would post it on FB.

  17. JMBase (1.8.4) for esp8266/esp32 by Juanjo Martín

    ➡️ github.com/juanjomartinf/JMBase

    Librería modular con funciones comunes, WiFi y MQTT para ESP32/ESP8266.

  18. 5MP cameras, 8CH NVR, 1TB hard drive included. Complete home surveillance for under $180.

    5MP WiFi Home Security Camera System Outdoor

    🔭 https://www.amazon.com/dp/B0GJ5KWVR3?tag=jwebb004-20 #ad #paidlink #AmazonAffiliate #SmartHome #HomeSecurity

    5MP WiFi Home Security Camera ...

  19. I'm going to get some speakers and a little sound war fare lol like they want. I hope you like my little ponies techno I love mlp. Soon I will be all your fucking ISP lol. Just need me equipment then I r become everyone's wifi whether you like it or not I will ensure you never play cod your iot don't work xD.

    Get helicopters though do better with ai

  20. Yes, this is a hill I will die on (and die mad about, because there's nothing that's gonna change it now)...

    Internet != internet.

    There's a generational breakpoint where the only meaning of "internet" is "wifi access", and in fact "wifi" means access to the Internet. Whereas the geeks and the older folks think of "wifi" as the last-feet layer-two transport / auth / etc only.

    Put another way, analogy from electricity:

    "internet" = "is the power on in my home"

    "Internet" = "is the overall electrical grid OK"

    ... and The Youts make no distinction between the two.

    So when 404 Media's headline says "is the internet cooked?", they really should say the Internet, not the internet.

  21. 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

  22. So, I don't do a lot of printer reviews. Primarily because, "in my day" there wasn't a freaking subscription on everything. And now, most printers offer (who are we kidding, it's a requirement that requires a lot more technical savvy than I have, to bypass effectively)
    My last printer had a subscription. But, due to my friend's accident, I had to move to someplace where I almost never used the printer, so I cancelled the cartridge subscription. That alone was a MASSIVE pain in the ass. Then, because I didn't use it very often, I had to have it cleaned ($20). Unfortunately, I had to have it cleaned every time I needed it because it would sit for weeks.
    I had hardwired it, because when I tried to use it through WiFi, it kept trying to reinstate the subscription, EVERY FUCKING TIME.
    I used to love HP. No more.

    I wanted something that wasn't a subscription, didn't have expensive cartridges and could sit for a month without the necessity of cleaning.
    And I found one.
    Yes, it was $300. But I am so glad that I spent the $.
    I got an Epson Eco printer and I ABSOFUCKINGLUTELY LOVE it.
    No cartridges, you fill reservoirs from a bottle.
    No subscription.
    I filled it up, printed the test page and a couple things I needed, and then it sat for over a month. Then I needed something printed, I was worried because, in my experience, after sitting for a month, it should require cleaning before operating.
    The pages printed perfectly, no cleaning.
    If you want an environmentally better printer, hate ink subscriptions and it doesn't matter if your usage is daily or less than monthly, I HIGHLY recommend the Epson Eco printer.

  23. 📻 Top 10 @acarsdrama posts (past 24h):
    📊 Total Engagement: ❤️ 6 | 🔄 10 | 📈 16 | 📊 Avg: 1.6

    1. ⏰ 01:40 UTC | ❤️ 3 | 🔄 0 | 📊 3
      📝 Air to Ground Message: LMAO THATS WHAT WE WERE SAYING Area: Liberal, KS, USA Type: Bombardier CRJ200A: F:
      🔗 live.acarsdrama.com/@acarsdram

    2. ⏰ 22:43 UTC | ❤️ 0 | 🔄 2 | 📊 2
      📝 Air to Ground Message: TUG FAILED. NEW TUG Area: Ingolstadt, Germany Type: Boeing 787-9A: F:
      🔗 live.acarsdrama.com/@acarsdram

    3. ⏰ 19:13 UTC | ❤️ 0 | 🔄 2 | 📊 2
      📝 Air to Ground Message: GOOD AFTERNOON RDU, STAY SAFE THIS SPOOKY SEASON....,THE MOONS HAUNTED Area: Orlando, FL, USA Type: Airbus A321neoA: ...
      🔗 live.acarsdrama.com/@acarsdram

    4. ⏰ 18:21 UTC | ❤️ 1 | 🔄 1 | 📊 2
      📝 Air to Ground Message: NO POLICE. HES NOT ESCALATING. WE JUST WANT IT DOCUMENTED IN CASE HE DOES IT AGAIN IN FUTURE. HES A PLATINUM GUEST. Area: Phila...
      🔗 live.acarsdrama.com/@acarsdram

    5. ⏰ 03:38 UTC | ❤️ 1 | 🔄 1 | 📊 2
      📝 Air to Ground Message: PASSENGER IS CONSCIOUS Area: Orlando, FL, USA Type: Airbus A319A: F:
      🔗 live.acarsdrama.com/@acarsdram

    6. ⏰ 20:58 UTC | ❤️ 0 | 🔄 1 | 📊 1
      📝 Air to Ground Message: JUST HEARD AF1 TAKEOFF Area: Tampa, FL, USA Type: Airbus A321A: F:
      🔗 live.acarsdrama.com/@acarsdram

    7. ⏰ 20:08 UTC | ❤️ 0 | 🔄 1 | 📊 1
      📝 Air to Ground Message: WE HAVE UNRULY PAX RETURNING TO GATE Area: Philadelphia, PA, USA Type: Airbus A320neoA: F: ...
      🔗 live.acarsdrama.com/@acarsdram

    8. ⏰ 19:00 UTC | ❤️ 0 | 🔄 1 | 📊 1
      📝 📡 ACARS Drama — 24 Hour Summary📝 Messages• Drama Candidates: 6392• Posted: 322✈️ Aircraft• Seen: 3293• Posted: 260🛫 Flights• Seen: 2729• Posted: 269🛩️...
      🔗 live.acarsdrama.com/@acarsdram

    9. ⏰ 16:38 UTC | ❤️ 1 | 🔄 0 | 📊 1
      📝 Air to Ground Message: WOOT WOOT... COFFEE LEVELS TO THE TOP Area: Philadelphia, PA, USA Type: Boeing 737-900A: F: ...
      🔗 live.acarsdrama.com/@acarsdram

    10. ⏰ 16:29 UTC | ❤️ 0 | 🔄 1 | 📊 1
      📝 Air to Ground Message: FYI POWER DROPPED OFF AT THE GATE PRIOR TO AP U START AND AS A RESULT THE ENTERTAINMENT SYSTEM IS NOT WORKING WIFI IS GOOD NO M...
      🔗 live.acarsdrama.com/@acarsdram

Share on Mastodon

Enter the server where you have an account.