voytec

Polish army, border guards and police are stationing on Poland-Belarus border since 2021 as there's a constant conflict.

Putin's goons are driving middle-eastern refugees to the border and are trying to forcibly push these people to Polish side. Last year, Belarusan Mi-8 military helicopters flew at low altitude some 2km into Poland's territory. In June, Polish soldier was stabbed to death.

> I think this might be a cultural thing.

It's just German bureaucracy. When I wanted to register domains with Hetzner few years back, they asked me to print multiple pages of forms and contract, fill out, sign and... fax it back.

Is ERR_SSL_VERSION_OR_CIPHER_MISMATCH the effect of this cap? If so - that's a really weird approach at blocking a website.

    > openssl version
    OpenSSL 3.4.0 22 Oct 2024 (Library: OpenSSL 3.4.0 22 Oct 2024)
    > openssl s_client -connect www.lukasmoro.com:443
    Connecting to 2a06:98c1:3120::b
    CONNECTED(00000005)
    00E167F201000000:error:0A000410:SSL routines:ssl3_read_bytes:ssl/tls alert handshake failure:ssl/record/rec_layer_s3.c:908:SSL alert number 40

Yup. IANA dind't have ccTLD retiring procedures yet, when Soviet Union collapsed in 1990. But would they want to, they could delist it at any point. IANA holds the registry for all TLDs and - that's extreme and unlikely - could delist .ru, .ir or .kp at any moment.

I'd guess that it's actually a requirement. Domains registered under ccTLDs (country-code top level domains) are managed by regional bodies[0]. In case of .su, it's either RIPN or ROSNIIROS[1] which manages the registry and registrations.

But again - IANA is universally queried about given TLD and redirects the query to regional body. In case of .su:

    > whois yandex.su
    
    % IANA WHOIS server
    % for more information on IANA, visit http://www.iana.org
    % This query returned 1 object
    
    refer:        whois.tcinet.ru
    domain:       SU
    organisation: Russian Institute for Development of Public Networks
    organisation: (ROSNIIROS)
    
    (...)
    
    # whois.tcinet.ru
    % TCI Whois Service. Terms of use:
    % https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian)
    % https://tcinet.ru/documents/whois_su.pdf (in Russian)
    
    domain:        YANDEX.SU
    nserver:       ns1.snparking.ru.
    (...)
    state:         REGISTERED, DELEGATED

[0] USUALLY; .tk, .ga, .cf, .gq were managed by by infamous Freenom due to incapability of owners to do it themselves

[1] https://www.iana.org/domains/root/db/su.html

> it's pretty explicitly set up as an extortion racket

Or rather for squatting. google.sucks is registered by Google LLC, microsoft.sucks by Microsoft Corporation, meta.sucks by Meta Platforms, Inc., and so on...

Two-char TLDs are a special case and are bound to a country. And this rule works both ways - Soviet Union wanted .ussr and was given .su

ICANN and IANA could effectively delist .su despite Russian Federation's "decline".

How much silly and outdated the WHOIS protocol is, the client queries IANA and only then is forwarded to RIPN (Russian Institute for Public Networks).

Theoretically .io should cease to exist as well but apparently TLDs can be "too big to fail"[0], too. But officially, there's a 5 years-long grace period after which .io is deemed to be sunshined[1].

> In essence, a five-year time window will commence during which time usage of the domain will need to be phased out.

Related: "Ask HN: What happens to ".io" TLD after UK gives back the Chagos Islands?"[2] (2024-10-03), 250p 210c

[0] https://www.theregister.com/2024/10/10/io_domain_uk_mauritiu...

[1] https://domainnamewire.com/2024/10/09/io-domain-names-arent-...

[2] https://news.ycombinator.com/item?id=41729526

We seem to have a weird drive towards testing one sci-fi dystopia after another as a potential way to go. This is Max Headroom.

I like your thought pattern.

My route from Poland to dedi box leased from Hetzner in Finland currently goes through AS1299 / twelve99.net (Warsaw->Talinn->Helsinki) peering, and there's a slight increase in latency since the cable cut. On a normal day, it's Poland -> Hetzner in Germany -> Hetzner in Finland. I'm guessing that the situation hurts companies like Hetzner financially.

> the "battery" in the old ones is nuclear and it's going to be difficult to beat that

Newer atomic batteries can theoretically last centuries instead of decades.

V'ger 1 atomic battery is based on Plutonium-238 which has a halflife of ~88 years. It's down to ~210W output from initial 470W at launch time.

Americium-241 has a half-life of over 400 years.

Poland joining NATO was "an existential threat" to Soviet Russia, too. It's bullshit. The CCCP pretty much collapsed on its own.

There's no "threat" now. Putin is just desperately trying to rebuild what Gorbachev already lost.

I'm not interacting with companies seeking cheap labor in Poland - like Intel. Despite their quite active recruiters, all conversations with whom end up at "company policy doesn't allow me to discuss salary range".

I've set up a small business with EU tax id over a decade ago and I'm issuing invoices to European countries (EU and Schengen) and North America.

It's a trade-off of giving up European employment safety, pension, some quality of life when working in different timezone, benefits and job security, to work for higher salary.

But it only makes sense until some business decides that they would like a contractor from Poland with a Polish salary.

I've talked to several recruiters and HR people who were prepared for quite a different answer than I gave to this question.

I got the feeling that several interviews were carried out afterwards out of politeness or because the recruiter "had to" do it, but the interview ended before it began. Than, there's either ghosting or almost immediate (like up to an hour past the interview) copy-paste email along the lines of "we decided to go with another candidate".

A few recruiters however were open that they've checked the salary for similar position in my country's capital city (Warsaw) and it's much lower than what I'm asking. Pointing out 20+ years of experience and listing accomplishments seems less important for a lot of businesses, than paying as little as possible.

I got a few links to these "check salary for [level] [position] in [city]" websites from recruiters. All these seem to be crafted in a way that undervalues employees by artificially lowering country-wide salaries to ridiculous levels.

Poland's right-wing is pushing nationalism and anti-EU propaganda under the guise of patriotism. The word lost its original meaning since pre-1991 communist era.

> Contributing factors to the mishap included an electrical event during flight, which induced failures of both primary radios, the transponder, the tactical air navigation system, and the instrument landing system

Are F-35 Lightnings already permitted to fly to operate within 25 miles from thunderstorm or other atmospheric electrical activity?

I need to dry my hands before clicking "no longer exercising" on my Apple Watch after swimming. It adds my steps through the beach to the towel as the distance swum but allows using the physical crown/button to eject water...

> Poland is pretty strict. They will fine you if you cross the street

It's varies in different parts of Poland.

Lublin - double fine for crossing a street with an "island" between the lanes on red light

Warsaw - single fine, but ~99% chance of getting fined even if you don't see any cops around

Gdańsk - you can jaywalk in front of a precinct and unless you force drivers to honk, or act stupid in other way - no cop gives a flying fuck. Cities with tourism have cops acting on different rules.

You're focusing on an app, instead of ringing person's UX and _the_ doorbell itself.

My suggestion: find a niche, like a doorbell for hearing impaired home owners. Otherwise you'll be recreating Nest. Google won't buy identical product twice, to kill it. A generic Nest-like product has little chances to take over the market.

A button feels more natural and is much more approachable over an QR code. QR may be a nice fail-over for when no one is opening the door in reaction to knocking or pushing a button. But QR as the main method? Maybe for evolving markets or harsh neighborhoods where wireless doorbells get stolen - if that's even a thing.

You're looking into providing value to home-owners, by making it easier for someone outside their homes. In most cases this dumb button that makes some sound inside the house just works. Little area for improvement here, for most people.

Your potential market for people willing to stick a QR code on their door are:

> "I'm hearing-impaired. Please use below QR code if I don't hear you knock"

> "I'm not opening? chat with me here [QR code]"

↑ this is your potential target. You already see that most comments in this thread tell you that people don't want QR codes on their doors. You have an idea for a solution still looking for a problem. Accessibility around hearing loss may be one.

You can help people. And from a business perspective, you may be able to get government grants for such project, which may be better for you than crowd-sourcing. And, you may get customers who get their purchases partially covered by gov health programs, if you properly interact with related accessibility-related gov bodies (YMMV around the world of course), apply for getting your stuff assessed for free advertisements inside hearing loss-related clinics etc. And again - you can make a product that makes impaired folks' lives better. Win-win.

There are multiple ESP32-based doorbell projects (I like this one[0]) that can be expanded easily with code changes. I can't really see how a QR code is better. Make your product either equally interesting to public or covering some niche use-case. And again: Nest...

[0] https://tristam.ie/2023/758/

I can see some potential for people with hearing loss. I've seen apartments and houses of such folks, with some small dedicated bulbs or even normal ceiling lights flashing furiously on all over the house upon someone ringing the doorbell. A doorbell signaling smartphones, making smart wrist watches vibrate etc, could be reasonable in such cases. But it could be still a plain uncomplicated button next to the door.

> As I said, laws that prohibit companies like Apple from disclosing something are very different from laws that force them to affirmatively make false statements.

1. Apple tells users that they don't snoop on iCloud data, and sprinkles this marketing statement by assuring users that they are literally incapable of doing so.

2. US government lawfully forces Apple to gather and share intelligence, with an adjacent gag order. Apple changes a few settings on their backed and issues updates to to iPhones, along with publicly disclosed changes. Apple - as any business wishing to still exist in a year (or the management wishing to keep their seats) - complies with government's demands to the letter.

3. Gag order literally renders Apple and any person aware, [edit: s/incapable/disallowed/] of stating "we started logging this data" or "we have not been logging this data in the past, but..."

4. Apple logs and shares data, has to lie to customers to abide the law.

> This kind of stuff is an existential threat to ad-based business models and upselling.

Sounds great. But corporations will find a way to fuck over their users for inverstors' gains in no time.

Prohibition of Certain Disclosure under 18 U.S.C. § 2709(c) AKA "gag order".

So Apple sucking the data from user's device to their cloud without permission is not data collection because Apple says it can't access iCloud data? Come on. It's a US-based corporation owning the keys to systems on both ends. They are obligated to release the data when requested. And they may be obligated to lie about it, also by law.

> allow users to resell/inherit/gift digital goods such as apps.

Users can't gift/resell what they don't own ;-)

What about Health.app? It collects data, and likely sends it to Apple, without user's permission. The permission to allow Apple / the app to collect data actually only allows _the_user_ to see the data collected earlier.

Get an iPhone, only after few months enable Health permissions and one will see all the data collected before one allowed data collection. Oh, and Apple absolutely knows which country the device is used in - they base sound level warning levels on specific country's laws.

A very tamed - yet on point - comment on Mullenweg's recent behavior.

Kudos to the author for using RFC5737[0] TEST-NET-2 address for:

> An example of an IPv4 IP address is 198.51.100.1.

[0] https://www.rfc-editor.org/rfc/rfc5737