I forgot to link to this one on cohost: https://hikari.noyu.me/blog/2023-02-06-touchhle-anouncement-thread-tech-games-me-and-passion-projects.html
I'm curious to see what kinds of comments I'll get here.
magical girl on the internet?
You must log in to comment.
in reply to @hikari-no-yume's post:
planning on a technical write up? iβd be super interested to read one
Oh, I'd love to write one, but there's just so many moving parts that it'd be hard to actually cover the whole thing. I actually wanted to write a proper blog post about it for the release, but I realised that my high standards for blog posts meant I'd never get it done. In the end I wrote a twitter thread which actually worked pretty well when turned into blog form, but the way I thought about it was pretty differentβ¦
I can see myself eventually writing about it by reducing the scope a bit. For instance, I could write about what pieces are involved in making a simple Objective-C method call work.
β¦actually, an Objective-C method call is probably too complicated, I'd write about a C function call and then maybe have a follow-up talking about Objective-C, because that's at least twice as complex.
super focused stuff would be cool! and honestly the more little self-contained write ups the better (maybe easier to write and then we get "more" stuff :p) fun bugs or cool implementation tricks would be cool to hear about too. but i like 150% get the effort and perfection angle
bugs are fun⦠there was a really bad problem with the threading system that I thankfully caught before release, which I talked about a bit during my release celebration stream. I should think about whether I could turn that one into a blog post somehow, I guess it would be an interesting lesson in the architecture.
doing an impromptu stream using this rn btw https://twitch.tv/hikari_no_yume
hello this rules and i love the use of <ruby> tags
btw my rss aggregator initially refused to load your hybrid blog page/atom feed, and i think it's because it's served with content-type application/xhtml+xml. i told it to ignore that and it loaded fine, but i worry that other people might not be able to subscribe because of this
thanks :3
yeah, I know it's the wrong MIME type for an Atom feed, it's a workaround for Safari refusing to attempt to display the page if I do claim it's Atom, because Safari used to have an RSS/Atom feed reader, and now it displays a message telling you it can't read such feeds, even though I made sure the page can be displayed as styled XML.
maybe I need to send a different MIME type depending on the Accept or User-Agent headers or something
i feel like it might be worth setting up a different path that just serves the same content with different headers
β¦that's not a bad idea, though it's not as elegant