remotelove

My background: Long time IT security engineer here that can code when I need. For dev experience, I have worked with various languages over the years like assembly, C/C++, js, typescript, PERL, python, etc. When needed, I can hack out a specialized tool but I am absolutely not a professional developer.

My ask: I just want a simple web framework that I don't need to think about too much. There are a few ideas I have regarding security analyst workflow in a SIEM-type of environment and need a way to code simple tools as basic snap-ins to a central analysis console.

The ELK stack serves a inspiration (specifically Kibana). However, there is so much more I want to build into an security specific analysis console and building it one snap-in at a time seems manageable over time.

What is the current flavor of the day regarding Web app dev frameworks that might function how I want? What frameworks would be compatible with a broad audience over a long period of time? (I never liked open source applications that use super niche libraries or frameworks that become obsolete and stale after a few months.)

I hope I was able to describe clearly enough what I am looking for. I would google around for ideas, but I simply don't know the correct questions to ask about this kind of thing until I get more up-to-speed.

I turned off "Preload Images" and my feed hasn't hung since. There is still a tiny bit of wait time while the next group of posts gets cached in the feed (maybe < 1 second) and this is usually when post pre-loading would fail and hang the feed completely.

If for whatever reason, if an image can't be preloaded it'll hang the feed? Maybe if a post gets deleted on one instance and, because fediverse, it may still be listed by my home instance? A failed cross-instance image load does sound like an interesting theory for root cause.

1. (Regression, I think.) Strike through markdown broken when used in combination with exclamation point (maybe with other special characters too?) Also affects large blocks text that is marked with a strike through

~~Strike~~

~~Strike! ~~

2. Cannot select text from comment that you are replying to

3. Selecting text on your comment is appended with multiple spaces if there is no punctuation.

• to reproduce: create post or reply, press and hold the last word of the sentence with no ending punctuation

4. Text selection can become "sticky". (Unknown cause) Moving cursor around on a comment in progress results in the text selection bar that cannot be turned off. Connect restart is required.

5. Post cache is not always refreshed after edit. Requires Connect restart to see changes made to a post. (Post text is where the caching issue is, not generally comments.)

Single pull-down refresh breaks post alignment.

~~Multiple pull-down actions may cause the offset of the post to slowly creep up and I under the post menu and almost off the top of the screen. OR, when the post is opened, the post will load with proper alignment and then shift itself up.

This seems to happen within the first few actions on opening Connect and it may self-resolve if the post is opened again, but not always.~~

Edit: ~~There is something wrong with that specific post in the screenshots. Other posts work fine, that one does not.~~ Its happening on this post now too.

Post is fully scrolled down, post title gets covered:

Menu will self-hide and you can see how far up the post has been aligned: ~~

Not sure if it's a quiet night or not, but comment volume drops off about 3 hours ago as of this post.

Initial Load:

Pull-down refresh:

This is likely a critical bug for users on LemmyNSFW for image posts.

Edit: This was originally an issue with image posts, but many sites aren't opening now.

I can refresh some feeds, like c/LemmyConnect, but it is ineffective for high-level feeds like c/all.

Trying to replicate an issue where replies to long comments will get partially nuked during edit if you scroll up before the comment is committed.

Edit: This bug is a thing, but am missing one or more triggers for it to "work". Sigh. I'll make a formal bug post if I figure it out.