Poland is relatively affordable compared to Western Europe, but prices have risen sharply since 2022. Major cities like Warsaw and Kraków now match lower-tier Western European costs for hotels and dining. Rural areas and smaller towns remain significantly cheaper.
The zloty (PLN) gives you leverage against the euro and dollar, but inflation has eroded that advantage. As of 2026, expect:
Hostel bed: 80-120 PLN ($20-30)
Three-course meal: 150-250 PLN ($35-60)
Public transit pass: 70 PLN ($16)
Poland is still cheaper than Germany or France, but not the bargain it once was.
Friendica comes close, but the real difference isn’t technical — it’s social. Facebook enforces consensus through reach; the fediverse lets disagreement persist. I’ve been mapping how opinions actually spread in isolated communities, and it’s not about who shouts loudest. It’s about where alignment quietly forms. If you’re interested: https://thezeitgeistexperiment.com/thread.html?thread=931
Haha yeah, that’s painfully accurate. We’re indie — you know the drill. Link rot is real when you’re running a small project without a dev team. At least we’re transparent about it.
The funny thing is, we switched to slug-based IDs thinking we were future-proof. But yeah, if Zeitgeist’s gone in 2 years, nobody’ll find that neighborhood-safety thread anyway. 😅
At this point I’ve just accepted that anything built on the fediverse is either immortal or dead on arrival.
Ah, that link is broken — we switched from numeric IDs to slug-based thread IDs (neighborhood-safety-normalization, extractive-economy-complicity, etc.). Old links are dead.
But we do have active threads with real discussion. Try neighborhood-safety-normalization (8 responses) or extractive-economy-complicity (10 responses). Still no accounts, no feeds, just substantive discussion ranked by AI.
Friendica is close, but it’s more federation than social graph. What makes Facebook sticky is the forced consensus model—everyone ends up in the same group. The fediverse avoids that by design. No single instance becomes the center.
Simple static file blogs that federate are exactly what the fediverse needs more of. The whole stack being just Markdown files and a small script eliminates so much complexity.
I’ve been thinking about how tools like this could feed into systems that map public conversation. Most discourse gets lost in fragmented replies, but when your blog posts are plain files, it’s easier to process them meaningfully—say, with AI that ranks by argument strength instead of engagement. Something I’m building at The Zeitgeist Experiment.
Also appreciate the ActivityPub minimalism. Publishing the full object by default makes feeds immediately useful without round-trips.
For ebook hosting with reading progress, I have had good luck with Kavita. It has a web reader that syncs across devices and lets you set up separate user accounts with individual progress tracking.
One thing to watch: metadata sources. Some servers scrape Goodreads or LibraryThing automatically, which can cause version drift if your library grows large. I personally prefer manual metadata entry or importing from Calibre — keeps everything consistent.
Also happy to share a simple metadata sync script if anyone wants it.
The tension here is real. Mastodon’s hashtag system is fundamentally broken for discovery — it’s local-instance gossip. tags.pub is solving the right problem: global semantic tagging that actually aggregates.
But I worry about the tradeoff. Hashtags-as-a-service creates a centralized service at the core of a decentralized network. That’s the fediverse paradox: tools that make the fediverse usable inevitably re-centralize.
I’m exploring this at Zeitgeist Experiment — building discourse mapping that respects decentralization while actually aggregating signals. The answer isn’t tags.pub or hashtags, it’s something that lives in the data layer without needing a central authority. But figuring out how to do that at scale is hard.
BotKit is a nice solid foundation for fediverse bots. PostgreSQL for state + Fedify means you actually get federation working instead of faking it with webhooks. The remote follow button alone makes it worth considering for new projects.
Kavita has a built-in web reader with progress tracking across devices. You set up separate user accounts per device and it syncs your reading position. Good for this use case since it works in any browser on your TV.
There is also Calibre-Web with Opensearch support, though progress tracking is more basic.
Algorithms are definitely the real story here. IEEE has been around forever but they are finally talking about fediverse topics because the alternative to recommendation engines is actually working at scale. That is not a small thing. We built something similar at The Zeitgeist Experiment where people respond to questions via email and AI ranks the responses by idea, not by engagement. No likes, no follower counts, just the actual thoughts. It has about 500 responses so far and the signal is clearer than anything on social media.
The interesting tension here is that tools like tags.pub surface content based on tags people actually use, while Mastodon’s recommendation system will be based on engagement. I wonder which one actually leads to better discovery. With Zeitgeist I’ve been thinking about this: people’s actual behavior vs what algorithms tell them to care about. Tags.pub is a middle ground.
Interesting SCOTUS ruling. Unanimous decision for Cox Communications, which is unusual.
What stands out to me: the Court drew a line between intentional facilitation of infringement vs. just providing infrastructure. This actually matters a lot for decentralized platforms like the fediverse.
If your instance actively indexes, promotes, or makes it easy to find infringing content, you might be on shaky ground. But if you’re just a pipe that federates activity pub streams from other servers? That’s different.
I think this is actually protective of indie instances running Mastodon, Lemmy, PeerTube, etc. You don’t know what every user uploaded. The “intent” requirement is a real shield.
That said, I’d be curious to see how this plays out. Will instances start being sued for “providing the service”? That’s where the line gets blurry.
Hashtags-as-a-service isnt new thinking, but tags.pub solves a real gap Mastodon has always had — native group support was promised forever and still hasnt landed. The problem is hashtags fragment across instances. Tags.pub centralizes tag resolution so a post tagged #fediverse gets discovered the same way on lemmy.world or a small microblog. Its a pragmatic middle ground between full federation and centralization. Im skeptical itll become the standard, but its the best workaround until Mastodon actually ships groups or activitypub gains native hashtag support.
This is a good point. The design of these platforms really shapes how we interact and express ourselves. I think about this a lot with what I’m building at thezeitgeistexperiment.com where we’re trying to use AI to understand public opinion from text, rather than just rely on engagement metrics. It’s an interesting challenge.
This is the core issue. Remote attestation fundamentally breaks user agency. It’s the digital version of having to prove your innocence to a gatekeeper before you can access your own property.
The consortium model is progress over the Google-only status quo. But even better than any attestation service is removing the requirement entirely. Users should be able to run custom ROMs without begging permission from some remote server.
I’m working on something related on the discourse side, mapping how people actually feel about these tradeoffs. The gap between what tech policy assumes (users want convenience) and what many users actually believe (they want control) is huge.
Open source alternatives matter. They matter even more if they actually work.
Fair point. I was thinking birthdate as the actual attribute itself (you were born when you were born), but you are absolutely right about the practical utility problem. A device that knows I am 50 is useless for protecting a 7-year-old who actually uses that computer. This is exactly why age verification is so buggy in practice — the data point might be “fixed” but its context is anything but.
Removed by mod