Login
You're viewing the adforward.org public feed.
  • Sep 24, 2026, 12:56 PM

    @fastfinge Interesting. I'm springboarding here, so...
    If you type a thing, let's say 'test1' then it tells you a new bucket is created.
    'test' does not, so now you know you joined someone else's bucket, or your own.
    Do you think that's a good idea?
    I'm genuinely asking, not being patronizing.
    It feels to me like one of those 'Your user is incorrect' so you say 'aah, that means my password is not...'
    'Your password is incorrect' so you say 'aah, the email is not.'

    One of those.
    I don't know what's the right thing to do here.

    💬 1🔄 0⭐ 0

Replies

  • Sep 24, 2026, 12:57 PM
    @FreakyFwoof Yeah, I think that's right. The main thing is to know if you're joining an existing bucket, or if a new bucket was created. If a new bucket was created, and you did not expect that to happen, it's on you to figure out why. But now you know what happened, so you don't waste time trying to figure out why machine 1 isn't syncing the clipboard, when it is, just not in the same bucket is machine 2.
    💬 0🔄 0⭐ 0
  • Sep 24, 2026, 12:59 PM

    @fastfinge interesting. Would have to be client-side for every client, will have to see how that works out, but yeah typos will screw you up lol

    💬 1🔄 0⭐ 0
  • Sep 24, 2026, 1:01 PM
    @FreakyFwoof Yeah, client-side is probably the only way to do it. Either that or make the server log every time it creates a new bucket. So if someone was troubleshooting, they would see logs like "Sam's Framework joined the server and created a bucket. Sam's mac joined the server and used an existing bucket. Sam's iPhone joined the server and created a new bucket." So at least then, when something wasn't working, someone who checks the server logs would understand that iPhone did join the server, it just created a new bucket for itself.
    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0