full-stack developer, linux user, open source lover, web performance & frontend enthusiast.
building apps in my free time.
part of the syndicats collective.
Das Erdklima bewegt sich gerade in einer Freakzone extrem unwahrscheinlicher Ereignisse.
Das bekommen zu wenige mit, deswegen kommen hier all die krassen Klima-Charts, die ihr sehen solltet 🧵
@EricHallahan@ggerganov@AiEleuther Besides this, hyperparameter need to be adapted, which should be too bad.
Also I'm not able to tell if actual usage of weights differ for the more compley layers (as I'm also struggling to find how they are actually loaded in hugging face).
If I understand @ggerganov's approach for 🦙.cpp correctly, it should also be doable to use his ggml with the fine-tuned GPT-NeoXT-Chat-Base-20B model that @togethercompute released last weekend as part of OpenChatKit, right?
@EricHallahan@ggerganov@AiEleuther I digged through the GGML impl of GPT-J today (https://t.co/eEdVXIM1ni) and compared it to the 🤗GPT-NeoX implementation.
A lot made sense for me, but I'm not able to tell if especially the attention layer implementation matches, as I'm not familiar enough with the maths.
@JannikWempe - (outdated) comments
My take: whenever you feel a comment is necessary, extract a function or variable and give it a proper name. Works often even for "why" comments
@Jonatthu @maxlynch Totally agree. I am using ionic/capacitor myself and it definitely was key to me to successfully building apps with existing skills.
I just highlighted one pro/con between these technologies that bothers me and is related to both using a rendering engine.
@maxlynch * Blurry background filters don't work Properly
And (not a bug, but different behavior) : pain with efficient webview behavior when keyboard is opened.
Not the fault of ionic/capacitor, but it did costs me days of caring about internals I didn't want to care about (3/3)
@maxlynch * ios keyboard state is not resetted after clearing an input (autocomplete keeps old chars for example) that's quite essential for a chat
* app became unusable since Safari reimplemented video loading behavior and capacitor wasn't adapted yet
(2/3)
App Store Optimization is something we didn't think about at first. We read articles, hired a professional and still managed to fuck it up. Don't do what we did!
https://t.co/Adks60GZEB
Seven years ago, we started developing and publishing apps. None were a success but we learned a great many things from the real world of app development.
In our blog, Appventuretime, we want to share everything that went well and everything we fucked up 🫠