> What? The app is infamous for just "forgetting" tickets
Citation needed. I've never heard of this being an issue (certainly not an "infamous" one) and almost everyone I know constantly travels by train and uses the app regularly. Maybe you're mixing things up with Deutschlandticket apps by regional transport associations, but that's not DB's fault.
Tickets get hidden from the default view once they're expired, but that's to be expected and you can press the prominent "Previous trips" button to see them.
If they were genuinely just attempting to "troll" by spamming (which is a pretty lame thing to do to begin with), they wouldn't have had to use a racist slur in their message. The fact they did makes their intent pretty clear.
If a project taking a stance against people spamming the n-word makes you lose respect for them, that says a lot more about you than the project.
Do you really think a teenage internet troll who wants to offend as many people as possible would stop and think "You know what, I sure do love pissing people off but I draw the line at 'NIGGER BALLS'"?
> If a project taking a stance against people spamming the n-word makes you lose respect for them, that says a lot more about you than the project.
They weren't "taking a stance" against spam, they were claiming that FOSS itself was in danger due to a non-existent far-right campaign against them.
Except that usernames contain a domain name component, and the “bare” username likely isn’t globally unique, the UX is nearly the same as other microblogs. And as to that username bit, people are used to joe@gmail.com and joe@outlook.com being different people, and having to specify which one they’re trying to send an email to.
Everyone who’s both email and Twitter already understands all the basic concepts.
> And as to that username bit, people are used to joe@gmail.com and joe@outlook.com being different people, and having to specify which one they’re trying to send an email to.
User handles are unique in ATProto because of the domain, just like email. Not sure what the "except" part is about. Can you clarify? In ATProto, they are not "bare"
ActivityPub is the same, except they are tied to the server you join. In ATProto, they are decoupled from your data host so you can move your data and server without changing your handle. You can also change your handle without moving anything else, because handle points to a DID behind the scenes
This comment is a great illustration of the needlessly hostile interactions mentioned in the blog post.
There's a nuanced technical discussion about the merits of adding this to Mastodon and whether the effort would really be worth it. Eugen made some reasonable points against it.
But instead of engaging with the discussion in good faith, people like you automatically assume the worst intentions and claim Eugen personally is "blocking progress" like there's some grand conspiracy (Instead of the much more boring reality of limited dev time and having to prioritize things).
I'd give him the benefit of the doubt 7 years ago. But it has been 7 years and the number of Mastodon instances just grows and grows, causing more and more useless traffic every time someone links to a site.
7 years of "limited dev time"? How much money have the world's webmasters had to pay out of their own pockets, so that nobody developing Mastodon has to spend their precious dev time on being a good netizen and not wasting other peoples' resources?
This is why webmasters block Mastodon user agents. Then Mastodon changed the order of text in its user agent string just to fuck with webmasters - ostensibly they wanted the user agent to look a little bit nicer, but what they did was evade everyone's existing blocking rules, and cause 100,000s of webmasters to have to update their blocking rules for what should've been a solved problem.
Mastodon servers' collective behaviour DDoSes the sites its users link to. They just do. They don't have to, they've never had to, but they do. And they've been in no hurry to fix it.
I've never used Mastodon and I'm not part of its community. But it irks me that its community has completely failed to remediate its collective bad behaviour, for years.
Having read the relevant discussions in Mastodon's issue tracker, my view is that it's Eugen Rochko's ideological belief that you can't just include the link preview details along with the post (which you totally could do, and it would solve the problem)... and that has led to years more DDoS than there ever needed to be.
[Admittedly, we now also have the problem of completely amoral "AI" scraping companies, who have zero qualms about pumping millions of requests into webservers, knocking them offline, completely eschewing all common indexing behaviour... but that doesn't make Mastodon's behaviour acceptable because it's no longer the worst source of callous DDoSing]
I don't know there's an assumption involved. I think for many people, it gives them the opportunity to act out on anger, shame, and other emotions they've internalized. They smell 'blood in the water' and know they can get away with it.
My understanding is that the non-profit in the US exists exclusively to handle fundraising from US donors who might not be able to give to non-US organizations for tax reasons.
Or for a tax receipt. I give modestly to Wikipedia, but their lack of a Canadian entity means I direct the bulk of my giving toward entities that I get the CRA kickback for.
Though if you are in the US odds are you don't need this tax deduction anyway. Few people understand how US taxes work and so give their accountant all their deductions because they know tax deductions exist. They don't realize that the standard deduction applies and they don't/can't deduct anything.
Before the SALT cap of $10K, it could easily matter. Prior to the cap, I itemized deductions every year - easy if you have a mortgage, live in a high income tax state, and both spouses work. In those days the standard deduction was $12K, and just our state taxes exceeded that amount - forget about mortgage + charity.
Even after the SALT cap, on some years itemizing was better.
And I believe as of next year (or the one after?), the SALT cap is going up significantly. Back to itemizing every year.
Spamming the same bad-faith argument over and over in this thread on an account you clearly solely created for this purpose does not make it more true.
Personally I'm quite happy that these tiles cut down on the clutter in the original OSM tiles. It made it very hard for me to actually use them for navigation because there was just so much stuff everywhere.
For example the old tiles displayed rail tracks extremely prominently, which just aren't relevant 99% of the time even when traveling by train. In the vector tiles they're much more muted and thinner.
> I'm quite happy that these tiles cut down on the clutter in the original OSM tiles. It made it very hard for me to actually use them for navigation
The Openstreetmap.org tiles are a demo and a contributor quality assurance tool - they are not meant for end-user applications, hence the rather over-the-top selection of map objects.
The nice thing is, that's just a style, not a property of the tiles. So if you want to alter the rendering, it's "just" a change to the style of that layer/attribute.
I’ve also switched away from Django (to Litestar), but the ORM is the mean thing I keep missing from Django. SQLAlchemy feels really clunky by comparison
I think the ORM is fine. There's always some friction coming from mapping rows to classes and objects, but you can always drop down a layer and just pull raw tuples.
What I'm not a fan of, is the query DSL. Normally, the developer works to figure out how to express their problem with SQL; then the DB engine works to figure out how to map that SQL to the data it has on disk. Now Django adds another layer, which is completely unlike SQL, has its own unique pitfalls, etc; sometimes I find myself just dumping the raw SQL, working on that to get the result I wanted, then working that back to the DSL.
I think SQLAlchemy gets it right. The query language is a thin veil over SQL, and mapping to objects is an explicit and clear operation. What does feel clunky to me, is setup: SQLAlchemy expects you to bring your own glue; Django is vertically integrated.
This is my pain point in Django as well, the query DSL. 10+ years with Django and I still don't know how it's supposed to work, given it's all done within the namespace of a function call.
Fortunately, I now have AI to write any Django queries for me.
Mostly the better documentation (last I checked FastAPI docs felt more like a series of blog posts than actual docs, but maybe that's improved). I also preferred the community-driven approach of Litestar as opposed to FastAPI's BDFL-type development structure.
I think there were also some technical details I liked better about Litestar where it was more explicit about things while FastAPI was more "opaque magic happening in the background", but to be honest I don't remember all of those.
We chose Litestar over FastAPI mostly because they seemed very similar, but Litestar had a more distributed governance; i.e. a larger bus factor.
We are jealous of some FastAPI features though, so it's possible we could migrate, as Litestar's mapping between domain models, database models and API models isn't as flexible as we'd like.
Borg is a fork of Attic, not restic. Restic is also written in Go while Attic/Borg is in Python.
For me the reason to use Borg over Restic has always been that it was _much_ faster due to using a server-side daemon that could filter/compress things. The downside being you can’t use something like S3 as storage (but services like Borgbase or Hetzner Storage Boxes support Borg).
That’s probably changed with the server backend, but with the same downside.
Citation needed. I've never heard of this being an issue (certainly not an "infamous" one) and almost everyone I know constantly travels by train and uses the app regularly. Maybe you're mixing things up with Deutschlandticket apps by regional transport associations, but that's not DB's fault.
Tickets get hidden from the default view once they're expired, but that's to be expected and you can press the prominent "Previous trips" button to see them.
reply