98 karma · joined September 4, 2020
https://www.maybevain.com/
It's been, what, at least five years(?) since predictive text was launched. I never expected to be the first to be supported, but starting to feel a bit ridiculous when some languages with a few tens of percents more speakers have had support from nearly the start.
Meanwhile third party keyboards have had support for ages. I'd rather use the stock keyboard, but can't bear it in its current state.
You play as the drummer on a viking boat, hitting the notes (similar to GH) to the tune of power metal. Nice workout, especially if you really get into it and start exaggerating your movements.
The trailer gives a better impression than I can.
Maybe the text you read refers to the OS itself and all first party software being written without external dependencies?
The only related thing I found was that free accounts are limited to one user that can trigger deploys in private repos, while anyone can trigger deploys in public repos (assuming I understood the announcement correctly).
”Tere” is also, perhaps unsurprisingly, used in Finnish.
[0] https://www.youtube.com/watch?v=dx5Wd28AKxQ (the video is a couple years old so the current implementation might be different, but I think the basic principles are still the same).
Interesting summary from the developers: https://www.eveonline.com/news/view/the-massacre-of-m2-xfe
Quick glance in this case: took a couple second snapshot on the Performance tab and saw a lot of React related calls.
Then again Finnish has anyway been a second class citizen when it comes to iOS features.
Safari is in Finnish on my phone, and I used the phrase ”Tervetuloa takaisin” to test. For the other languages I used whatever Google Translate suggested.
The Algolia index contains the comments encoded as HTML entities, so they should be safe to insert as is, but seems like the page is first converting it back to HTML, which causes the script and span tags to render as HTML instead of text like here on HN.
Quoting the relevant part: "They're welcome to have them back anytime they want."
https://thisanimedoesnotexist.ai/results/psi-2.0/seed37303.p...
Github readmes however only allow embedding SVGs as images, and Javascript won't work in that case.
EDIT: added a missing word
EDIT: to ellaborate for the interested, the Public Suffix List is used by browser vendors to decide what part of the URL is considered the TLD for display and cookie security purposes (and I imagine others).
The code is already hosted on Github, so I created a separate repo for the comments where each post would get an issue. Zola will pull all the comments on each issue on built time and embed them on the respective blog pages. A webhook on the repo will trigger a built when a new comment is made.
Can't say this system is battle tested yet, as there's been nary a comment posted, save for the couple test ones by me...
Coupling it with Tailwind for styling meant that developing the theme was really smooth (slowest part of changing a template was waiting for the browser to refresh, i.e. < 1s).
Did not notice being dead myself before reading your comment, so I assume someone vouched for me.
My browser did however cache the latest image (which is why I thought the system was not working for a second), and I'm not sure how to get around that.
[0] https://docs.github.com/en/github/authenticating-to-github/a...
EDIT: I see. The no-cache causes the Camo service to refetch the image every time it is requested, but it still applies a 4 hour cache time to the response to the browser so it is anyway cached on the client side.