Replying to @⁨dansup@lemmy.world⁩

I’ve always been a supporter of your work, but I’m tired of all the fake promises, the “soon” you always say without shipping anything, how you often say “it’s released” when it’s just in the code so no, it’s not release for the people actualy using the software because you didn’t make a new release yet. I know software development takes time and love, especially when working solo, but not a reason to create fake promises or hopes.

Also, you used a framework that was clearly AI assisted itself : github.com/nuxt/nuxt So this is the reason why I thought the new fedidb was AI assisted, I was talking more about the UI (not the content itself).

Anyway sorry for calling something wrong on my part in my last comment.

I really want you to build cool stuff, and I want to like you for it, but for now I don’t see the cool stuff that much anymore…

Replying to @⁨dansup@lemmy.world⁩

Looks great! Is the best way to submit bugs by DM or email?

I noticed the following issues when trying to sign in and add an instance with my accounts on Lemmy and Piefed instances (lemmy.ca/u/otter and piefed.ca/u/otter specifically):

Logging in

Signing in with the profile-description (bio) code works on both Lemmy and PieFed, but logging in with a DM does not work for either.

On Lemmy, I get the error message

We could not deliver a message to that account. Check the handle, or use another way to sign in.

Meanwhile on Piefed, FediDB says that it sent the code, but it fails silently since I never receive a message on the account. I looked into adding fedidb.com as a trusted instance from the admin side, but I don’t think that’s the issue since there are no entries for fedidb.com there at all.

I know it should be possible to receive DMs from non-threadiverse instances since Canvas used that for auth. If it helps, here is the source code for that project:

I think they do it by sending the DM as both a Mastodon style note and as a Lemmy style chat message (link to code)

// around line 144
   const outbox = [
      await message.build(fedify.Note),
      await message.build(fedify.ChatMessage),
    ].map((obj) => apub.prepareObject(obj, ts));

Admin verification

This one fails for both.

On Lemmy I suspect it is looking at the wrong endpoint since I get this:

Could not reach the server to confirm your admin status.

Meanwhile on Piefed, I see the following message despite using an admin account that shows up in /api/alpha/site

Your account is not an admin or the contact account of this server.

I haven’t tried the other methods yet :)

GitLabsc07 / Canvas · GitLab · sc07.devCanvas is a collaborative pixel canvas built for the Fediverse

Replying to @⁨dansup@lemmy.world⁩

I tried signing up to try answering some of the unanswered Mbin questions, but it's telling me it can't confirm my account. I double checked the handle, tried with and without the @ in front, copied it directly from my profile, and I tried using webfinger manually to see if it replies with cloudflare (it doesn't). This happens with both the private message and profile code options.

Not sure if others using Mbin have the same issue or if it's the instance. What does it actually check to confirm the account (before sending the private message or giving me the code to put on the profile)? It doesn't seem to be a simple webfinger lookup.