sorted by: new top controversial old
[-] Kizaing@lemmy.kizaing.ca 7 points 7 months ago

Setting this up fixed it for me

[-] Kizaing@lemmy.kizaing.ca 3 points 11 months ago

Check out Anytype it's pretty much just an open source Notion, I like it a lot

[-] Kizaing@lemmy.kizaing.ca 31 points 11 months ago

I think the way it works is that banning just prevents them from making more posts/comments. The admin has to purge the user from the instance to actually remove the content

[-] Kizaing@lemmy.kizaing.ca 1 points 11 months ago

I think some downstream projects will choose to not implement it. Vivaldi and Brave browser committed to not implementing it when it drops, so those two will likely be fine, at least for now

[-] Kizaing@lemmy.kizaing.ca 1 points 1 year ago

It probably is using Synapse, the Beeper github links directly to the matrix ansible script which uses Synapse by default unless you change it

[-] Kizaing@lemmy.kizaing.ca 4 points 1 year ago

It looks to be an issue with using the backend 0.18.4-beta.8, ever since my instance updated to it I haven't been able to use Sync either

[-] Kizaing@lemmy.kizaing.ca 1 points 1 year ago

Ah that's too bad. I'm glad at least that it seems to be a reproducible issue. But hopefully it's fixed soon, looks like we just have to wait it out

[-] Kizaing@lemmy.kizaing.ca 2 points 1 year ago

The latest tag is mapped to 0.18.4-beta.8, I had it set to latest and my watchtower upgraded it from 0.18.4, I find it weird too

[-] Kizaing@lemmy.kizaing.ca 2 points 1 year ago

I attempted to downgrade, it did not work haha. Seemed to have issues migrating the database backwards

[-] Kizaing@lemmy.kizaing.ca 1 points 1 year ago

Clearing the cache seemed to have no effect :(

[-] Kizaing@lemmy.kizaing.ca 2 points 1 year ago

I just tried, seems the migration only moves forward not backward :( I was able to revert it back to the beta.8 image without issue though.

Looks like I might have to wait for a fix for now, but thanks!

11
submitted 1 year ago* (last edited 1 year ago) by Kizaing@lemmy.kizaing.ca to c/syncforlemmy@lemmy.world

Was hoping to see if anyone had encountered this issue, I'm running a single user instance for myself, and foolishly I forgot to set my lemmy docker images to not automatically update.

As of updating from 0.18.4 to 0.18.4-beta.8, Sync no longer works. I get a "failed to load" error

I certainly don't mind waiting till the next stable release since this was my own fault, but wanted to see if anyone else was experiencing this

Update: It's been fixed! Thanks so much ljdawson

view more: next ›

Kizaing

joined 1 year ago