There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

zen

@[email protected]

This profile is from a federated server and may be incomplete. Browse more on the original instance.

zen , to cafe in /c/café daily chat thread for 30 July 2023

there will be at least 5-10 minutes of downtime for db migrations though (more if the db size is huge). of course, after the long migrations the db size is reported to shrink significantly.

anyway, there’s already been at least 2 easily triggered/discoverable bugs:

  • view context for comments does not work properly (i heard it may even crash jerboa)
  • all software versions in the instances list are displayed as 2.0

hopefully they will release a 0.18.4 quickly with fixes for that.

zen , to cafe in /c/café daily chat thread for 30 July 2023

yea, then i’ll need to take a nap in the evening

zen , to cafe in /c/café daily chat thread for 30 July 2023

too bad sleeping in works for me sometimes, but not lately…

zen , to cafe in /c/café daily chat thread for 30 July 2023

sorry, i posted it in hopes of getting some replies from apple users, but i don’t have any apple devices myself.

anyway, since utm is using qemu under the hood, i wonder how easy is it to run plain qemu on ios…

by the way, today’s daily thread is so low traffic!

zen , to cafe in /c/café daily chat thread for 30 July 2023

for those using ios: getutm.app 🤯

zen , to cafe in /c/café daily chat thread for 29 July 2023

okay, anyway maybe there’ll be a lemmy 0.18.4 soon.

they’re finding all sorts of bugs including a duplicate comment bug, and another one that makes the lemmy version in the instances list become 2.0 instead of 0.18.x.

i wonder if someone was dreaming about an early lemmy 2.0, lol.

zen , to cafe in /c/café daily chat thread for 29 July 2023

luckily we caught this early before monyetbot had a lot of posts. anyway, i think what’s even more important is the keypair in the db, so it is good the problems monyetbot had were not related to that.

by the way, you may want to do a sql dump and search if there’s any other reference to frank_bot that can be updated. i heard lemmy 0.18.3 (out last night) has quite a bit of db optimizations, so don’t want any outdated reference to cause issues with that.

zen , (edited ) to cafe in /c/café daily chat thread for 29 July 2023

i don’t think so. i think what’s important is that it stays under the same license, which means sooner or later you’ll have to disclose source, but i don’t think anyone is going to be so picky as to say you have to do it at the very beginning.

in other words, as long as you are not intentionally withholding source, it should be alright, but again, ianal. anyway, yours is just a hobby project so no need to be so strict about it.

i am just bringing to your attention the nature of the license involved, so maybe if you’re not that comfortable with it, you could look around for a more permissively licensed python lemmy library (if there’s even such a thing, considering the whole lemmy stack is already under the same license).

zen , to cafe in /c/café daily chat thread for 29 July 2023

oh that’s nice, may i know what sql statement you used?

anyway, time to upvote everything in this thread so it federates over 🤣

zen , to cafe in /c/café daily chat thread for 29 July 2023

if you are referring to github.com/db0/pythorhead then you must take care, both this and lemmy-js-client (and the whole lemmy stack itself) is under affero which is a viral license that has been touted as a preventive measure against big tech.

ianal, but i think any network interaction with code derived from those 2 libraries must be placed under the same affero license.

wefwef/voyager was hit by this exact licensing issue.

zen , to cafe in /c/café daily chat thread for 29 July 2023

i can’t think of anything else besides the very risky option of editing the db directly, but you’ll probably have to ask the lemmy devs for the correct sql statement that would solve this.

or, as a more temporary option, maybe this could be solved at the webserver level, by redirecting all requests to /u/frank_bot to /u/monyetbot (must take care to distinguish between requests to backend and frontend, both *ends respond to that http request (with different content types)) but that would just involve an nginx expert instead of an sql expert, and i am neither.

zen , to cafe in /c/café daily chat thread for 29 July 2023

@Naomikho @Annoyed_Crabby i have found the issue.

check out monyetbot’s webfinger it points to frank_bot instead of monyetbot, which probably means monyetbot was renamed, and lemmy does not do well with renamed users that still refer to their former name under webfinger.

zen , to cafe in /c/café daily chat thread for 28 July 2023

you could just git push it to a new repo, unless it is not git, or maybe your organization has something that prevents that.

zen , (edited ) to cafe in /c/café daily chat thread for 28 July 2023

you’re accessing the lemmy db directly instead of using the lemmy api? (or on second reading, perhaps your code uses its own separate db to keep track of things?)

zen , to cafe in /c/café daily chat thread for 28 July 2023

is it in typescript? do you have any intention of releasing the code?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • lifeLocal
  • goranko
  • All magazines
    •