u/Dustersvk

Bratislava is stuck in the far southwestern corner of Slovakia, pressed directly against Austria and Hungary. The city can only grow in one direction inside its own country. Its functional urban area does not respect that, so a large part of its suburban growth has simply landed in municipalities that belong to other states.

The clearest case is Kittsee, a Burgenland municipality sitting right on the border. Population was 3,803 at the start of 2025 and has close to doubled over ten years. The growth is overwhelmingly younger Slovak families. The number that made me want to write this: of about 260 children in the local school, roughly 200 speak Slovak at home.

The drivers are unremarkable individually. Land is cheaper than in Bratislava, the commute is very short because the city edge is right there, Austrian housing credit support is available, and by several accounts the permitting process is more predictable than on the Slovak side. Stack them and you get a village turning into a suburb of a foreign capital.

The part I find genuinely hard, and where I would like to hear how other regions handle it:

The costs and the revenues end up in different countries. The Austrian municipality carries the service load, school places, kindergarten capacity, roads, water, waste, for a population that largely works in Slovakia and pays income tax there. That is an ordinary fiscal externality of suburbanisation, except the usual remedies are unavailable. You cannot do metropolitan tax sharing across a national border, you cannot fold these municipalities into a Bratislava planning authority, and neither national government has much incentive to fix a problem that is invisible in its own aggregate statistics.

What is left is blunt. Reporting from the area suggests some border municipalities slow down permitting once the incoming share climbs, which manages the rate of change but does nothing about the underlying mismatch, and it pushes the pressure one village further out. The same pattern is reported on the Hungarian side of the border, where land is cheaper again.

Two questions:

Are there other capitals where suburbanisation has crossed an international border at this share? I can think of cross-border metro regions like Geneva or Basel or Luxembourg, but those are usually framed around labour commuting into the core rather than the core exporting its housing demand outward into another jurisdiction.

Has any cross-border metropolitan region actually solved the fiscal side, meaning real compensation flows between the municipalities on either side, rather than setting up a coordination body that produces strategies and no money?

My city is finally replacing a tram stop this summer, and the thing being torn out went in as a provisional platform in 2016. Ten years of provisional.

It was one of the worst stops in Bratislava. There was no real platform, so you boarded practically off the road surface with a big step up into the tram. Fine if you are able bodied and in a hurry, genuinely awful if you have a pushchair, a walking frame, or luggage. The replacement is a proper island platform, 66 metres long and just under 4 metres wide, built during a line closure that runs from the start of July to mid August.

What strikes me is how ordinary this is. Provisional infrastructure has nobody lobbying to finish it. It works badly, but it works, so it never quite reaches the top of anyone's budget, and the temporary label quietly turns into the permanent state. Meanwhile everyone using it just adapts and stops noticing.

So what is yours? A bridge, a stop, a container building, a level crossing, a road layout, a "temporary" ferry replacing a bridge that never got built.

Bonus points if you know what year it was originally supposed to be removed.

I live in Bratislava and have been following the Danube situation closely this summer. What interests me is less the drought itself and more what it reveals about a river that has been engineered in a very uneven way along its length.

The current state, for context. The gauge in Bratislava fell to roughly 214 cm at the end of July, the lowest in about 30 years. It has recovered a little since, it was 243 cm last Thursday morning. Downstream the picture is worse. Romania is at its lowest since 1996, with flow near the mouth around 1,700 cubic metres per second against a July average of roughly 4,700.

The consequences have been concrete rather than scenic. Hungary shut down the Paks nuclear plant on 1 August because the Danube no longer supplied enough cooling water. That was the first full shutdown in the plant's 44 year history, and Paks produces close to half of Hungary's electricity. It had already been running at 965 MW instead of its usual 2,000. On the Slovak side the Gabčíkovo hydro plant is producing around 12 percent less. On the navigation side there are stretches where vessels are banned from passing or overtaking each other, the worst being a 142 km reach below Gabčíkovo down to the confluence with the Ipeľ.

Here is the part I find geographically interesting.

Almost none of this reach behaves as a natural river anymore, so a "record low" reading is a measurement against a heavily modified baseline rather than against nature. The Gabčíkovo scheme diverts most of the flow into an artificial bypass canal, and when that diversion began the water level in the original riverbed dropped by three to four metres. So the number a gauge reports depends on which channel it sits on and how the system is being operated that week, not only on how much water the catchment is delivering.

The asymmetry comes from the fact that the scheme was never finished. Gabčíkovo–Nagymaros was a joint Czechoslovak–Hungarian project. Hungary abandoned the Nagymaros half, and the dispute went to the International Court of Justice in 1997. The result is that the upper reach has regulation and the lower reach does not. Under drought the burden therefore lands unevenly along the river rather than in proportion to where the rainfall deficit actually is, which is roughly the opposite of how you would design it if you started today.

Two things I would like input on from people who work with this:

First, how should a record low be communicated on a regulated river? Saying "lowest in 30 years" is technically true at that gauge but it arguably understates the hydrological anomaly, because part of the level is being held up by infrastructure. Is there a standard way of expressing this, some naturalised or reconstructed baseline?

Second, a local told me that Gabčíkovo raises the level at Bratislava by roughly a metre, so that without it the city would currently be sitting near 1 m. I could not verify that figure anywhere and I am not going to repeat it as fact, but if anyone knows the actual backwater effect at that distance upstream I would like to know, because it changes how the headline number should be read.

We run a voice and chat agent in production that takes real bookings. It has to answer in Slovak or English depending on the customer. For about three weeks we had a bug I think is worth describing, because the symptom pointed straight at the model and the cause was entirely ours.

The report was "the agent sometimes slips back into Slovak when the customer is writing in English". Classic LLM nondeterminism, or so it looked. We had a language detection function running server side, and when it detected English it injected a hard directive into the system prompt twice, once as a final overriding instruction and once as a separate system message right before the question. Belt and braces. And it still leaked Slovak.

So we spent real time on the model side. Reordering the directive, strengthening the wording, moving it later, giving it its own turn. Marginal changes, nothing that actually fixed it.

The real cause: the regex inside the detector contained a literal backspace character, 0x08, in the position where a word boundary was supposed to be.

The patch that introduced that detector had been applied by a Python script. The regex lived inside a Python string, Python interpreted the backslash-b as its backspace escape, and wrote the raw control byte into the JavaScript file. The file looked completely normal in an editor and in review, because that byte renders as nothing at all. The regex compiled without complaint. It simply never matched, so the English branch never ran, and the directive was never injected. Every single time it "slipped into Slovak", it had never been told not to.

Two things I took away.

First, when a guardrail works "most of the time", verify it is executing before you tune the prompt. We had logging on the final output but nothing on whether the detection branch fired. A single line logging "directive injected: true/false" would have found this on day one instead of week three. This is the trap: a model behaving nondeterministically and a deterministic check that never fires are indistinguishable from the outside. Both look like "usually fine, sometimes wrong".

Second, do not let one language's escaping rules write another language's source. If you patch or generate code with a script, verify the resulting bytes rather than how they render. Running od -c over the changed lines would have shown it immediately. We rewrote that detector to avoid escape sequences entirely, it is now a plain set of stopwords split on non-letter characters, partly for readability and partly because it cannot be silently corrupted the same way again.

The broader point, and the reason I keep coming back to this in this sub: a lot of what gets blamed on model nondeterminism is deterministic code quietly not running. Prompt level guardrails and server level guardrails fail in completely different ways. Prompt rules fail loudly and randomly. Server rules fail silently and totally, and you will not notice unless you instrument the decision itself.

Curious whether others have been bitten by a guardrail that was never actually running, and how you log it. We now record every injection decision, which works but gets noisy fast, and I have not found a good middle ground yet.

I'm in Slovakia, Central Europe. Historically this is roughly zone 6 to 7 country. You grow apples, plums and cabbage here, and anything Mediterranean lived in a pot and came inside in October.

This summer our all-time national temperature record fell. The old one was 40.3 C from 2007. We went past 41 C in the south, and we had two separate 40 C episodes about a month apart in a single summer, which has not happened here before in the modern record.

So I went digging into what our Academy of Sciences says about the plant side of this, and it is stranger than I expected. In the southwest of the country these now overwinter outdoors, in the ground, with no winter protection at all:

• loquat (Eriobotrya japonica)
• pomegranate (Punica granatum)
• passionflower, both Passiflora incarnata and P. caerulea
• olive, which takes about -15 C and tops out around 2.5 to 3 m here

The part I liked most is that pomegranate is not actually new here. There is a roughly 35 year old clone growing in a village called Bernolakovo that has its own name, "Bernolakovo early". It flowers and ripens earlier than southern cultivars, and some pomegranate cultivars handle -17 C. So while everyone assumed this was impossible at our latitude, one tree had quietly been doing it for three decades.

Olives also behave differently here than in the Mediterranean, which I did not expect. Down there summer heat actually slows them down. Our summers are more humid, so growth is more or less continuous. They flower two to three weeks later, but the fruit ripens earlier.

The honest other half of this, because it isn't really a feel good story: the same institute points out that wheat, potatoes and cabbage stop performing above 30 C, our summers have stretched by up to two months, invasive species are pushing natives out, and alpine species have nowhere left to retreat to. Their director's line is that by the end of the century this could be climatically similar to North Macedonia. So we get figs and olives, and in exchange the mountains lose part of their flora and farmers lose yield.

What I'm actually curious about: what are you growing successfully now that would have been a joke in your area twenty years ago? And specifically, is it ripening for you, or just surviving? Those feel like very different claims and I keep seeing them treated as the same thing.

Po tom, ako tento rok padol absolútny teplotný rekord SR (Hurbanovo držalo 40,3 °C z júla 2007, teraz sa na juhu prekročilo 41 °C), ma napadlo, či to celé má aj nejakú použiteľnú stránku. Tak som sa prehrabal tým, čo k tomu píše SAV, a dosť ma to prekvapilo.

Na juhozápade Slovenska už vraj prezimujú vonku, zasadené priamo v pôde a bez akejkoľvek zimnej ochrany:

• mišpuľa japonská
• granátovník obyčajný
• mučenky (Passiflora incarnata, caerulea)
• olivovník, ten znesie asi do -15 °C a narastie u nás na 2,5 až 3 metre

Najviac ma dostalo, že granátovník tu nie je žiadna novinka. V Bernolákove rastie asi 35-ročný klon, ktorý dostal aj meno, "Bernolákovo skorý". Kvitne a dozrieva skôr ako južné odrody a niektoré odrody granátovníka vydržia až -17 °C. Čiže kým sme všetci žili v tom, že toto u nás nemá šancu, niekomu tam tri desaťročia v tichosti rástlo granátové jablko.

Zaujímavý detail k olivovníkom, ktorý by som nečakal: v Stredomorí im letná horúčava rast skôr brzdí. U nás sú letá vlhkejšie, takže rastú prakticky nepretržite. Kvitnú o dva až tri týždne neskôr, ale plody dozrievajú skôr.

Aby to nevyznelo ako reklama na klimatickú zmenu, druhá strana veci. Tá istá SAV upozorňuje, že tie isté podmienky likvidujú to, čo tu bolo doteraz. Obilie, zemiaky a kapusta nad 30 °C prestávajú fungovať, letá sa predĺžili aj o dva mesiace, invázne druhy vytláčajú pôvodné a druhy viazané na vyššie polohy nemajú kam ustúpiť. Riaditeľ centra Jaromír Kučera hovorí, že do konca storočia to tu môže klimaticky vyzerať ako Severné Macedónsko.

Takže áno, môžeme mať vlastné olivy a granátové jablká. Výmenou za to, že hory prídu o časť flóry a poľnohospodári o úrodu. Neviem, či sa to dá brať ako dobrá správa.

Pestuje tu niekto niečo, čo by pred dvadsiatimi rokmi u nás vonku neprežilo? Zaujímalo by ma hlavne, či to niekomu reálne aj dozrelo, alebo to len prežíva. Podľa mňa je to dosť veľký rozdiel a väčšinou sa to hádže do jedného vreca.

Zdroj, keby to niekoho zaujalo, je cbrb.sav.sk, majú k tomu viac článkov.

Context: a voice and text agent for a small cleaning company. It quotes prices, checks a calendar, books the job, emails the customer and the owner, and can cancel or move a booking. Real customers, real money, a real van driving to a real address. That last part is why the failures below were expensive rather than funny.

The pattern is the same in all of them, so here it is up front: a rule in a system prompt is a suggestion the model will route around under pressure. A rule on the server is a refusal it has to explain to the customer. Everything we moved from one to the other stopped failing.

The actual failures, roughly in order of what they cost us.

1. It booked jobs with no name and no phone number. Both fields were required. The model filled them with the literal string "not provided". if (!name) is perfectly happy with a non-empty string, so the check passed and the owner got a job with an address he couldn't find and a customer he couldn't call. Fix: a placeholder blocklist on the server, plus a completeness gate that refuses to book unless name, phone, street, town, service and quoted price are all present and the phone actually parses.

2. That fix silently did nothing for weeks. The blocklist regex used \w. The language is Slovak, the placeholder word has accented characters, and \w does not match them. So the exact string we were filtering sailed straight through the filter written to catch it. It normalises to NFD and strips diacritics before matching now. The lesson we keep relearning: after deploying a guardrail, try to break it with the exact input from the incident, not a similar one.

3. It told a customer it already had their phone number. It did not. The only phone number anywhere in that conversation was our own company number, which the model had written out itself two messages earlier while giving contact details. It read its own output back as customer data. Server fix: if the submitted phone normalises to the company's own number, refuse before booking and before sending anything.

4. It invented a name from an email address. Customer gives john@example.com, model records the name as John. Nobody asked it to do that. It now has to come from something the customer actually said.

5. It quoted below our minimum callout price. The rule covered every price-list item cheaper than the minimum. It did not cover sums the model calculates itself from square metres, so a small carpet came out at a price we cannot physically do the job for. The rule now applies to every number before it is spoken, computed or listed, and the server refuses to record a quote below the minimum.

6. It said "I've noted that down" when no tool had been called. Pure narration. Nothing is confirmed to the customer now until the tool returns success, and the tools that matter return an explicit reason string when they refuse, so the model has something true to say instead.

7. It read numbers out as words in the text chat. The prompt spells numbers phonetically because that is what makes text-to-speech pronounce a phone number correctly. In the chat widget that produced "zero nine zero two six three eight" written out in words. Two channels, one prompt, and the instruction was right for exactly one of them.

8. The model was chosen with a harness that never touched the production path. We A/B'd two models on a text simulation. One scored 8 out of 8 and shipped. In actual voice runtime it called tools once out of three attempts. The other times it narrated the tool call out loud, invented an appointment slot, and told the customer the booking was confirmed. Nothing booked, nobody emailed, customer happy. The simulation was text-in/text-out and the voice pipeline had a different tool-calling path, so the harness was green on code that production never ran.

9. Language selection broke in a way that looked like a model problem. English-speaking customers were getting Slovak sentences mixed in. We added server-side language detection to inject a directive when the incoming message is English. It never fired once. The regex contained a literal backspace character (0x08) instead of \b, because the patch went through a script and the escape got eaten on the way. From the outside this was indistinguishable from an unreliable model. The detection is written without any escape sequences at all now.

What was never a problem: the model choosing what to say, conversation quality, or latency once we dropped reasoning effort. Every real failure lived in the seam between the model and a system. Fields, encodings, channels, transports, escaping.

The architecture is boring on purpose now. Dates and availability are computed by the server and never by the model, so it cannot offer a slot that does not exist or double-book one. The booking tool validates completeness and refuses with a reason. The model's job is to hold a good conversation and call tools. Anything that costs money when it is wrong lives in code.

Happy to go into detail on any of these.

Small local service site, Slovak language, launched a few months ago with no backlinks, no reviews and no Google Business Profile. It gets tracked daily across ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews. Posting the actual numbers because most GEO writeups are either pure theory or a screenshot of a dashboard, and the per-engine split turned out to be the genuinely useful finding.

Starting point. First radar run: 17 questions a real customer would actually ask. Site cited in 0 of them. Competitors cited in most. Normal for a new domain, but useful as a zero line.

What changed, none of it clever:

• Sorted the 17 questions into winnable and not. Everything containing best / recommended / reviews went into the not pile and I stopped writing for those. They get answered from directories and review aggregators, and your own pages are simply not eligible to answer them. No amount of content fixes that.
• Wrote answer-first content for the process questions instead: how long does X take, what is the difference between X and Y, what does the price actually depend on.
• Rewrote every quotable fact to carry its own subject and unit. "Dries in 2 to 4 hours" became "A carpet cleaned by hot water extraction dries in 2 to 4 hours." Engines lift fragments without the heading above them, so a fact that needs its H2 for context is a fact that gets quoted wrong or not at all.
• Added the company registration number to the Organization schema as identifier, plus knowsAbout. Specific reason for this further down.

First proper run after that: 10 real URL citations. The split is the part worth stealing:

• Gemini: 7, almost all the homepage
• Perplexity: 3, all deep article pages, never the homepage
• ChatGPT: 0
• Claude: 0
• Google AI Overviews: 0

If you only check ChatGPT, which is what most people do because it is the one they have open, you would conclude the work failed. Gemini and Perplexity moved first and they wanted different things: Gemini wanted the entity, Perplexity wanted the specific answer. That alone changes what you write next.

The trap that nearly fooled me. The nearest competitor owns a domain that is the same words in a different order, roughly two characters apart. Early counts looked much better than reality, because the matching was substring-based and every competitor citation scored as ours. The real number at that point was zero. If you build or buy tracking, verify it does exact hostname matching plus subdomains and nothing looser. Same reason the schema identifier went in: when two entities look this similar to a model, a registration number is the only hard disambiguator you can hand it.

Separate your metrics. URL citations and plain text mentions are not the same event. One means the engine actually fetched your page, the other means it recalled a string from somewhere. Most dashboards blend them into a single visibility score. This site came back 10 URL citations and 0 text mentions, which tells a very different story than "10 points of visibility".

What has not moved: the head term, in any engine. The long tail moved first by a wide margin, so judging this at week three would have been wrong. And the best/reviews question class is still flat at zero, exactly as predicted, because that needs other people talking about you. That is not a content problem and I have stopped pretending it is.

Disclosure, since both are mine: the tracker is optimalizaciapreai.sk, built because the English-language tools do not handle Slovak. The site being tracked is tepovanievbratislave.sk, a carpet and upholstery cleaning business in Bratislava. The method above is tool-agnostic, the numbers are what they are. Happy to answer specifics.

Robím tepovanie v Bratislave a časom mi došlo, že väčšina toho, čo sa o čistení čalúnenia hovorí, je buď mýtus, alebo marketing. Hádžem to sem, lebo je škoda, koľko ľudí zbytočne zničí gauč alebo zaplatí za niečo, čo si vedeli spraviť sami.

1. Schnutie nie je jedno číslo. Koberec po extrakcii schne zhruba 2 až 4 hodiny. Sedačka alebo matrac do 24 hodín, lebo penová výplň drží vlhkosť oveľa dlhšie ako podklad koberca. Keď niekto sľubuje sedačku suchú za dve hodiny, buď ju len povrchovo prešiel, alebo klame. Po čistení sa oplatí otvoriť okno a na ten povrch si jednoducho nesadať, kým nie je suchý úplne.

2. Shaggy a dlhý vlas sa poriadne vytepovať nedá. Roztok sa do dlhého vlasu dostane, ale odsať sa z neho spoľahlivo nedá ani voda, ani nečistota. Výsledok je koberec, ktorý vyzerá čisto na povrchu, schne dva dni a v spodku má vlhko. Toto odmietam robiť, lebo sa pri tom nedá sľúbiť ani výsledok, ani čas schnutia. Ak máte shaggy, skôr ho perte v práčke, keď to výrobca dovolí.

3. Vlna, juta, sisal a viskóza nie sú bežný koberec. Vlna je bielkovinové vlákno, zle znáša alkalické pH, teplotu aj premočenie a po nesprávnom čistení vie zožltnúť, zraziť sa alebo splstnatieť. Bežná tepovacia chémia má pH okolo 8, čo syntetike nevadí, vlne áno. Ak máte doma vlnený alebo prírodný koberec, pýtajte sa konkrétne, čím sa bude čistiť. Ja si na ne pýtam najprv fotku a riešim ich kus po kuse.

4. Škvrna a zápach sa nedajú garantovať. Tepovanie vie zápach znížiť alebo odstrániť a škvrnu spraviť menej viditeľnou. Nevie sľúbiť, že mačací moč zmizne úplne, lebo ten nesedí v textílii, ale v pene pod ňou. Keď vám niekto garantuje sto percent, opýtajte sa, čo sa stane, ak to nevyjde.

5. Bežné tepovanie nie je dezinfekcia. Odsaje prach a časť usadených nečistôt. Nie je to sterilizácia a nezabíja to spoľahlivo baktérie ani vírusy, aj keď to tak v reklamách vyzerá. To sú dve rôzne služby.

6. Koľko to reálne trvá. Aby ste mali predstavu pri plánovaní: jeden koberec cez celú izbu je otázka 20 až 30 minút, bežné kobercové plochy v trojizbovom byte zhruba hodina, sedačka podľa veľkosti a materiálu 60 až 120 minút. Nie je to celodenná akcia, ako si ľudia často myslia.

7. Čo sa dá spraviť doma. Čerstvú škvrnu vysajte a potom ju len tupujte bielou handrou od kraja do stredu, nie krúživo. Krúživým drhnutím sa nečistota roztlačí do vlákna a okraj sa rozšíri. A hlavne to nezalievajte vodou, lebo bez odsávania sa vlhkosť dostane do podkladu a keď vyschne, škvrna sa vráti.

Pre poriadok, aby to nevyzeralo, že sa niekam pretláčam: živnosť mi beží pod menom Tepovanie v Bratislave. Nedávam sem odkaz ani cenník, nič nepredávam. Ak sa chcete na niečo konkrétne spýtať, kľudne do komentárov, odpoviem aj keď z toho nič nemám.

Zaujímalo by ma aj opačná strana: strhol tu niekomu prenajímateľ pri odovzdávaní bytu časť depozitu za koberec? Narážam na to dosť často a som zvedavý, ako to ľudia riešia.

Fico zatiaľ nepredáva slovenskú vodu šejkovi. Jeho vláda však rokuje o zapojení investora zo Spojených arabských emirátov do slovenských závlah. Keďže podmienky projektu nie sú verejné, obavy z drahej a dlhodobej závislosti slovenských farmárov sú úplne legitímne.

Kým vláda nezverejní zmluvu, dĺžku koncesie, spôsob určovania cien a práva investora, verejnosť vlastne nevie, čo sa pripravuje.

A pri vode a potravinovej bezpečnosti by sme to vedieť mali.

Vzdy som povazoval pracu z domu za benefit. Myslel som si, ze by to malo byt zakladnym benefitom kazdeho zamestnavatela, ktoreho zamestnanci nemusia sediet v kancelarii, lebo pracu zvladnu odkialkolvek. Pri dvoch detoch doma mam pocit, ze benefit je prave priestor u zamestnavatela. Praca z domu pri detoch mi pride ako peklo na zemi. Ma niekto podobny nazor / skusenost?

Hello i have my own n8n flow with chatbots but i think RAG is completelly useless. I started to use normal database and i got 100% precised answers. Have anybody same experience?

Chcel by som vedieť, ako si môžem vylepšiť svoju webovú stránku, aby mi ju citovali AI vyhľadávače, ako je napr. GPT alebo Gemini a pod.