e0qdk
Hmm. That doesn't really mesh with my understand of how certain prolific posters post (e.g. via automation), but digging into it a bit more, I do see the proxy link via Lemmy-UI even on the poster's instance, so there's something besides just mlmym involved here -- whether that really is inappropriate copy-pasting or a lemmy bug or what, I don't know yet.
Regardless, the fact that the image doesn't load in the post at all for those links seems like an mlmym bug that should be addressed; it's loadable via Lemmy-UI.
I've set up a new GitHub account for association with my lemmy account and will create issues on your repo in a little while.
Edit -- Issue links for future reference:
Thanks. I'm still learning both Go and the codebases involved. I'm pretty limited on free time where I've got both large enough blocks of time and energy to concentrate effectively on this. I'm also not very enthusiastic about taking on the administrative aspects of running an open source project -- I'm only really interested in keeping a JS-free version of Lemmy usable -- so contributing changes to a common community fork you've already got up and running sounds good to me!
I do have some specific issues in mind that I'd like to implement fixes for once I'm up to speed. In particular:
- There is improper filtering when a user submits a comment which results in certain text being stripped from the message instead of escaped properly. I'm not sure if this is an issue in mlmym itself or one of the libraries it uses, but I'd like to track it down and get it fixed.
- Federated image links to non-lemmy websites sometimes show up as image_proxy links from the poster's instance. This is a really annoying issue that results in misleading domains showing up next to posts as well as breaking image display in the post itself.
- Comments sorted by 'new' (and maybe other modes?) don't paginate properly.
I may take on some other issues after that, but those three are what I want to fix most right now.
You can use tesseract -l jpn input.png - on the command line to have it print out the text from input.png into the console if you've got the language files for Japanese installed. (There's also language files for vertical text and a few others for script in my package manager.) Alternatively give the filename (w/o extension) instead of - to write the output into a .txt file.
On Mint, I think I did sudo apt install tesseract-ocr tesseract-ocr-jpn to get it working for the simple case of horizontal text; been a while though.
The seeds from some kinds of pine are edible. e.g. pine nuts are used as an ingredient in pesto.
I've tried so many... so... many network filesystems. They all suck in some way.
Definitely agree with you on that! Distributed systems are just fundamentally challenging. Network filesystems try to hide some of that complexity, but it inevitably leaks through in one way or another...
I deal with Ceph at work. Thankfully I'm not the one in charge of its configuration, but I've seen enough of the headaches the admin had to go through to get it working right... Once we got it though, it's been working pretty damned well -- but you basically need a full-time sysadmin (or will become one yourself...) when you're dealing with the kind of scale we've got. (My home needs are not quite as insane though; mere dozens of TB instead of a dozen or so PB...)
SeaweedFS is another I've got in the back of my mind if I ever outgrown my NAS, but I haven't worked with it personally.
Yes, but more in a philosophical sense. Basically, just go read this: https://clojure.org/about/state
I generally use message passing rather than the sort of transactional concurrency the language promotes, but the idea of value vs identity has stuck with me.
Yup, I totally ate the onion on this one. Wait, what do you mean it's not satire!? :p