Closed williamhorning closed 3 months ago
roarer-2 (needs api accounts)
Trying to implement them, but I can't get the endpoint not to respond with a 500 error
roarer-2 (needs api accounts)
Trying to implement them, but I can't get the endpoint not to respond with a 500 error
that's really odd, is that with this branch or another one? if it's with this one, that's really odd as i haven't touched that code. but if it's with other branches, meo and apic seem to work just fine so try taking a look at their code
Tnix fixed that bug, I think Roarer 2 is compatible with this now with https://github.com/mybearworld/roarer-2/commit/856cb840979b0f0705d14b6a7be471fa0cea7d2c
@mybearworld alright cool. lmk when roarer 1 has support please
the development branch of svelte supports api accounts, so once i cut a release, we should be good
since it seems tnix may want to remove cl's dependency on the rest of the backend stuff even without gutting most of cl, this will need a bit more work but that shouldn't be terribly difficult. moving this back to a wip until i do that work
in theory the only cl -> rest
dependency is supporter's post parsing logic. at this point there are still a few rest -> cl
dependencies, all of which are sending events, getting ulist, or kicking clients (admin api)
this still works with everything except svelte, which tnix is dealing with supposedly
implementing pubsub for cloudlink stuff like ulist, client kicking, or event sending isn't something i feel like doing so that's out of scope for this pr
Closing as this has gone stale, CL3 commands have already been removed in develop and main, and there's many unresolved problems.
Closing as this has gone stale, CL3 commands have already been removed in develop and main, and there's many unresolved problems.
by many unresolved problems, there’re two: svelte and /status. at this point i don’t really care about /status, so that just leaves svelte. also, the implementations of the server on dev/main still have a lot of stuff that can and should be removed such as the majority of the trusted access logic, the gen_account command, allowing the use of passwords for authpswd, and a fair bit of server code. it’d probably be a pain to handle the conflicts that come from this being stale but i still as though those issues should be addressed somewhere
client/library compat
changes:
ping
andauthpswd
(with token only)/status
endpoint, use / forregistration_enabled
e
for new postspage
for all paginated endpoints (to replacepage#
).gitignore
and readme