Oh, any idea if there is a js-client community? Hate to spam their issue list but don’t see another way to check on their recco for moving forward. And thank you again.

Thanks for the response. I’m using 0.19.0-alpha.18 now (edit: in my develop branch), but wasn’t sure if I’d have the option to launch my apps with a non-alpha/beta/rc release ahead of the server release or not.

For announcements, while I’m not sure all developers who would want this are using RSS (I used to all the time, but haven’t lately), that would at least be an option if you were willing to do that. Please let me know if you do plan to make the switch and if so I’ll find a basic RSS notifier vs setting up Agriget or TTRSS again. It’s a shame we can’t turn on notifications for any posts there (similar to if someone replies to a comment/post), as that would be super-helpful here.

Thank you for the update. What is the recommended process for updating supporting apps using lemmy-js-client? I’ve got three apps, all with branches using an alpha client for now, but will the official JS clients roll out in advance of the official release of the server so we won’t have to run Alphas in production until we can get updates in?

Also, I know I’ve mentioned this before, and the response I got was “It will get upvoted enough”, but the 11/3 update only had 100ish upvotes, and did not make it to Top on my instance. I would really, really appreciate an announcement vehicle that allows us to get a notification. As Lemmy does not yet have a “notify for all in community” (or a community just for development updates that others can’t post to), could we please get some other vehicle where you post links to these posts? Even a pinned GitHub issue on LemmyNet would be fantastic, as we could subscribe to that and then see the link to here. Thanks again!

Honestly, when I read your comment, my internal monolog said “Huh, Esckwell? Ohhhhhh”

Do that in Javascript. Or HTML. Or CSS. Or by that logic is a web developer not a programmer? What about microcontroller programmers?

I could easily write a full logic program in SQL where the API just feeds it data, which is the inverse of how you treat SQL. Admittedly that’s not as common, but it happens pretty frequently in areas of big data, like medical.

I’ve hired Senior Software Engineers that were DBAs, and others that weren’t. They were a development team, all programmers in their own right.

Or not at all? Postgres? MariaDB? I think I missed the /s. I’m slow hah

This doesn’t make sense to me. SPs and functions are in every major database. If I wrote a bash script that runs like a program, and sounds like a program, did I program it? Script it?

And lots of systems have nested logic in the DB, optimization often leads to that to reduce overhead. Unless you’re being lazy with an ORM like prisma that can’t even join properly.

Getting high performing queries is just as difficult as any other programming language, and should be treated as such. Even Lemmy’s huge performance increases to .18ish came from big PG optimizations.

It’s tabs vs spaces for SQL. Notice how I capped.

Ditto.

Thanks for the response, I actually put another comment in after I started diving in and saw that the pagination/auth were overlapping, which was great news, it just didn’t come across clearly to me in the write-up for some reason. Thank you for structuring things this way.

Actually, as I start to do updates, it looks like the JS library still has page along with page_cursor (and the auth can be run in parallel) which seems to be great news! Does this mean I can continue to use page for pagination until .19 officially releases and rolls out, and then switch over?

For the truly breaking changes like API auth, pagination, and TOTP, is there a reason you don’t roll the deprecation like most software?

I.E. 0.19 supports both methods, and 0.20 deprecates the old one? This way developers aren’t caught off guard if they’re not following (which will get worse as time goes on), and allows development using official releases vs RCs.

For instance, if I want to update my app now, I have to release it with an RC library. If there was a version between deprecation, I could update at any point during the official 0.19 lifespan.

We’ve been working towards a v0.19.0 release of Lemmy, which will include several breaking API changes. Once this is ready, we’ll post the these changes in dev spaces, and give app developers several weeks to support the new changes.

Thank you for the update and the heads up.

How will this be announced, and what specifically does several weeks mean? Since Lemmy goes beyond Mobile Apps to all kinds of systems including moderation tools, auto-purgers, bots, CSAM, auto-subscribers, searchers, etc, breaking changes to the API can have far-reaching impacts.

Could something be set up specifically for breaking-change announcements where participants could be alerted? Even just a Breaking Changes issue that could be followed would work nicely.

Thank you again.

Translation, but not categorization. Trying to get reliable, and more importantly, predictibly accurate, metadata from an LLM without serious training is a pain. ML algorithms are far better for this but certainly take more brainpower (in my experience so far).

/c/whooosh anyone?

This is so smart. I’m stealing this.

Its always the backslash before the forward slash. Every. Time.

Sounds like you’ve contributed to git

First to star. Yay.

Even more strange is the use of DUO voluntarily. Can I ask why? I’m guessing work or a limited OpenVPN setup?