sir or ma'am

You could just say : "That's kind of you, thanks".

As I was saying, it loads fine in browser, so it can't have been removed :

After some testing, it seems that the issue only occurs with that image.

However, when using my browser instead of the app, I have no trouble opening the high res image.

Yep, I noticed the post following this one had these screenshots. Thanks

I'm not using nightly, how does the profile/community page look like there ?

Thanks, almost there :

Where exactly in theme settings are these options ? I can't find these.

Also, to make sure we're talking about the same thing, I added a screenshot of it.

Thanks

the "mark posts as read" setting

Where's that ?

To make sure we're talking about the same thing, I added a screenshot of it.

Thanks

Tell me about it.

What do you mean by better microblogging support ?

By the way, microblogging ≠ blogging. Speaking of which, Lemmy's post character limit is 50K. What's Kbin's ?

Hi, I'm also interested in using Lemmy as a blog. Did you explore this further ? Thanks

dictionary/array hybrid

That's a name, thanks !

Serialization might not behave as you would expect (JSON.stringify)

Actually, my implementation idea relying on Proxy don't have this issue.

As for other implementations, they do have this issue, but as they say, hybrid array use cases don't generally involve the need to stringify, and even when they do, using Object.defineProperty with { enumerable: false } (or replacing the toJSON method) would fix it.

3rd-party functions might not be able to deal with your data structure properly (again, potentially unexpected behavior). You can’t easily access array methods (find, filter, map etc).

Actually, it would still be an Array, so no, there shouldn't be any problems, and yes, those methods definitely work, which is precisely what said I want to achieve.

How do you distinguish between ID access and index access?

If your IDs are integers then there is no need for an hybrid at all, precisely because all you have to do is put each item at the same position as their ID.

It’s harder to reason about access time of lookups. However, this might not be a concern of yours.

I'll definitely run benchmarks so that users would be aware of performance losses, if any. But use cases of hybrid arrays are mostly small datasets so it usually shouldn't be a concern indeed.

It may cause confusion if you’re working with other developers.

If I implement this, it will be as a documented and commented package, so it shouldn't be that much of a problem.