Given the feedback and fixes I am going to contribute back to the original project. If the UI changes are too drastic I will consider managing a separate fork.
Given the feedback and fixes I am going to contribute back to the original project. If the UI changes are too drastic I will consider managing a separate fork.
Looks like larger images scales to the width of the comment block to the above image looks good on the app
What a pain this has been
From left to right: Android image before, android image after (full scale), Render in the web.
I mean realistically there should probably be a thumbnail and then an expanded view on click.
Or better yet completely hidden and images disabled. Whats stopping someone adding horrific images as a commenter and forcing everyone in the thread to view it?
Ah i see. It’s significantly smaller (maybe 45% the size)
I am less worried about the image size then the really large comment text though, but I will see if there is a workaround I can help out with.
Hmm i wonder how that works,
Image test
I can see these items in the code however how do you read
them? (I know they are for visually impaired but never needed to use them before)
These may also be put on the back burner as they most likely need to be multilingual.
Keep it simple with lemmy.itjust.works
.
If you get this going or need a hand then let me know.
I have been wondering how cumbersome the Lemmy design will become for some. I love the idea that it is federated and decentralized however these are also major drawbacks for most average
users (i.e not multi account users.
Multiple accounts needed for maximum uptime
on different instances. What if I really like my username and its taken on another instance? If one instance is down and i comment with my other account will i then need to manage replies etc through different profiles? What happens if something spins up another instance of a similar domain so that they can get a username of someone to imitate them? I am sure these can be blocked after the fact or will other federated instances be automatically blocked.
What happens when someone gets bored of their instance and stops it, or it gets blocked, or they start getting unwanted attention. Does this mean all that content then goes into the ether?
Will this go down the route of whomever provides the instance with the most resources, best load balancing becoming the one
, blocking other instances and controlling it as if it were private and independent?
There are a lot wait and see
things, but I am excited to help and see what this great project becomes.
I find this happens when the lemmy.ml gateway times out. When it’s back online and you open the app again you will magically still be signed in again
Pull requests incoming