hedge@beehaw.org to Technology@beehaw.orgEnglish · 1 year agoThreads' New Terms & Conditions Affects the Fediversewedistribute.orgexternal-linkmessage-square57fedilinkarrow-up1122arrow-down10cross-posted to: privacyguides@lemmy.oneprivacy@lemmy.mlfediverse@lemmy.worldfediverse@zerobytes.monsterfediverse@lemmy.mlfediverse@kbin.social
arrow-up1122arrow-down1external-linkThreads' New Terms & Conditions Affects the Fediversewedistribute.orghedge@beehaw.org to Technology@beehaw.orgEnglish · 1 year agomessage-square57fedilinkcross-posted to: privacyguides@lemmy.oneprivacy@lemmy.mlfediverse@lemmy.worldfediverse@zerobytes.monsterfediverse@lemmy.mlfediverse@kbin.social
minus-squareCanadaPlus@lemmy.sdf.orglinkfedilinkarrow-up7·1 year agoSee, I noticed this stuff reading through the Lemmy source code, but I assumed the authors just were on another level of database use than me. Is this actually just a mess? How exactly is it bad, beyond being opaque?
minus-squareBitOneZero@beehaw.orglinkfedilinkarrow-up8·1 year agoserous problems with scalability, it works fine if there is little data in the system.
minus-squareCanadaPlus@lemmy.sdf.orglinkfedilinkarrow-up1·1 year agoHuh. I guess I’ll have to learn a bit more.
See, I noticed this stuff reading through the Lemmy source code, but I assumed the authors just were on another level of database use than me. Is this actually just a mess? How exactly is it bad, beyond being opaque?
serous problems with scalability, it works fine if there is little data in the system.
Huh. I guess I’ll have to learn a bit more.