Hulk looks like he’s about to release a sick new Eurodance song.

Trying my best :)

Two reasons for me, but they’re mainly because of the MagSafe:

1. In the car, I just plop my phone onto the charger, and it holds it and charges it.
2. At home, I also use iOS 17 Beta, so I can use the StandBy.

Of course it has its drawbacks, but this assumes that I need to use my phone all the time (no), I can’t spare even 5 minutes to not charge, or that I need to top up from 10% to 100% in 5 minutes for some reason, which I don’t. If I do, then sure, I use the cable. Through the past year, I needed to charge my phone through the cable maybe twice.

Ok, so basically, there is multiple ways one could comment count. The most obvious option is to count the actual number of comments under the post. This might be in practice slow, as you must load all comments under the post. An alternative approach is to have a count variable for post, which is increased or decreased by 1 if post is added/removed. It’s way faster to retrieve that variable, instead of getting all comments and counting the number of them. The problem starts if some anomaly happens that is not accounted for, so for example, if I request the same comment to be deleted multiple times. So that counter can be decreased more than once for the same comment. This could be fixed pretty easily:

if comment_to_delete is deleted {
	// Do not do anything
	return
}

post.comment_count -= 1
delete_comment(comment_to_delete)

And yeah, I thought so too, but ever since I stumbled upon this bug, I think the way the comment count is stored is through the counter variable.

Yeah, sorry for taking so long with it 😅 Was a bit busy wtih other features too.

I accidentally made a post that has -3 comments.

This happens because Lemmy does not count the actual number of comments that there are under the post, but instead there is a counter per post. This is not necessarily a bad thing, but it does not seem like the counter is every synced with the actual count of comments.

My only gripe that makes me stay with Mlem is lack of any method of saving/sharing just the photo of a post.

EDIT: I meant Mlem, not Memmy.

As an author of one Lemmy front-end, I can confirm that you are potentially sharing your username and password. Unfortunately, there is no way for Lemmy front-end developers to, say, open a web socket to Lemmy instance and have you login through a web browser (which would be much prefered from security standpoint, but it is what it is).

Furthermore, from what I see, many of such front-ends store your password, instead of just the Bearer token. Unfortunately, from what I get, there is also no way of invalidating the Bearer tokens right now, so in the event of it getting stolen - you’re f***ed.

Now, couple of tips:

• USE 2FA AUTHENTICATION. In the event of malicious app actually stealing your credentials, you are at least a little bit more protected by this layer.
• Use password manager - do not use your banking password, please.
• Only use trusted front-ends, and in the even of an app, only download versions from official sources maintained by the app author.
• Make sure the instance you’re registered at has a valid HTTPS certificate.

I was thinking to take a break, as I’ve been working on Leomard non-stop since 1st of July 😅

Still a lot of work to do tho.

By the way! If you ever had any problems with loging in using Leomard, this update should address that. I noticeds there was a bug with parsing Instance data regarding registration method, which is resolved now :)

By the way! If you ever had any problems with loging in using Leomard, this update should address that. I noticeds there was a bug with parsing Instance data regarding registration method, which is resolved now :)

…this is literally something an intern could write in a single afternoon.

I guess I am a cross between “Normie” and “Conservative”. I use macOS and Fedora daily, I watch MKBHD but also watch FOSS YouTubers. I use WhatsApp, but only because, in Netherlands, it’s impossible to live without it. I don’t use any Chromium, and I use Firefox, but I also use Safari.

Fuck getting labeled.

I like 2019 more.

The “test” being whitelisting Chrome/Safari user agent? Because Bing AI works perfectly fine in Safari, as long as you change your user agent to Edge’s.

Glad to hear it. Although the pace at which new features are being added I think could’ve been better.

Honestly didn’t expect to get anything that fast 😅

Thank you kindly!

There in fact is a tip jar :)

https://ko-fi.com/athlon

Try the updated version.