I drive an Auris station wagon Hybrid (aka, the US Corolla iM with bigger boot). I had a chance to drive multiple Yaris generations and honestly I am always surprised by how roomy it is inside. They made a perfect use of space - way better than VW did with Polo (smaller Golf), that’s for sure…
Added
"Store Liked Posts" in Preferences -> Experiments
With this enabled, you can see all the posts you liked in the "Liked" tab in your profile
Added "Experiments" preferences
Added saving po...
Today I'm happy to announce Leomard 0.6! This update brings a handful of new cool features. To start with, you can now save posts as drafts!
Not only that, if Leoamard or your system ever crashes, if you come back to post editing, Leomard will ask you if you want to restore your autosaved post:
Another brand new feature that has been added is the experimental "Store liked posts locally" option. With it, you can browse the post that you have liked, which is not something Lemmy itself allows you to do. Unfortunately, because of that, the posts must be liked through Leomard, or at very least, they must be viewed through it.
Last feature worth mentioning is an option to use Piped.video to watch YouTube videos.
Added
"Store Liked Posts" in Preferences -> Experiments
With this enabled, you can see all the posts you liked in the "Liked" tab in your profile
Added "Experiments" preferences
Added saving po...
Link Actions
Hello everyone!
Today I'm happy to announce Leomard 0.6! This update brings a handful of new cool features. To start with, you can now save posts as drafts!
Not only that, if Leoamard or your system ever crashes, if you come back to post editing, Leomard will ask you if you want to restore your autosaved post:
Another brand new feature that has been added is the experimental "Store liked posts locally" option. With it, you can browse the post that you have liked, which is not something Lemmy itself allows you to do. Unfortunately, because of that, the posts must be liked through Leomard, or at very least, they must be viewed through it.
Two reasons for me, but they’re mainly because of the MagSafe:
In the car, I just plop my phone onto the charger, and it holds it and charges it.
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.
First method does not store the number itself anywhere. Let's assume that you store apples. I come and ask you "How many apples do you have?". To answer, you go and count every single apple one by one and return me the number. It's very easy if you have a small number of apples, but if you have, let's say, 5000 apples - you can see how long it may take.
Second option is you keeping a track of how many apples you have in stock by having it written down somewhere. If I ask you "How many apples do you have?" you just pull out your notepad and tell me the number. If you give me an apple, you just adjust the number you have written down already.
Getting the total number of all comments may be very resource heavy if there is a lot of comments.
If it's just 5 comments, then the computer can quickly get them all from database and count how many of them are there. Now imagine if there is 50 000 comments and suddenly, you me and entire website ask "how many comments are there for this post?"
Suddenly the computer is overwhelmed by the request and you may end up crashing it due to amount of tasks it has to do.
It's way faster if instead of all of that, the computer kept track of a number of all comments and simply adjust it when comment is added or removed. It does not have to get all the comments and count how many are there, just simply return the number and you are done.
But in the essence, you sacriface potential accuracy for speed. You may accidentally "desynchronize" the counter - if an user requests a removal of the same comment twice, and you don't check if that comment was not removed. Or, in theory, if two separate users add or remove a comment at the same time. This is called "race condition", which is common in multi-threaded computing.
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:
undefined
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.
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.
Added
Two-column view
Posts will open in the second column, instead of a popup window
You can enable it in Preferences -> Display -> Two-column view
The "[email protected]" in About view now ope...
After 9 days since the last major update, today I'm happy to announce Leomard 0.5! This update brings a long requested two-column view. In this view, opened posts are shown to the right side of the screen as so:
It works very good with the Compact View on! If you prefer the traditional popup view, you can still enable it in Preferences, which also received a new "Display" section:
Another new big feature is the brand new text editor. New text editor shows you how your Markdown text is going to look like live as you type it! Additionally, it has a heplful Toolbar at the top, which lets you add text formatting, insert link, image and preview the Markdown!
Lastly, Leomard can now mark posts as reas as you scroll past them in the Feed, without you needing to interact with t
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.
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 :)
Hello everyone! Today a new Leomard update has been released! This update brings some of the QOL features. To start, you can now enable separation of Followed communities by their first letter:
Additionally, you can search the list of Followed communities:
Login screen also received a small upgrade. Leomard will try to load instance’s icon, as well as allow you to search for an instance by its name:
Last but not least, a small set of “Mod Tools” have been added, which will make moderating a community easier:
This and more is available in Leomard 0.4. Here’s the full changelog:
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.
Added
Added support for "!community@instance" and "@user@instance" in the text. You can now click on them to open the community or user profile
Added protocol handler for leomard:// links. Communt...
Another feature-packed Leomard update is here! This time I’m adding some long requested features. First one is the brand new Compact View, which can be enabled in the Preferences:
Now you can see more posts at once! Additionally, one feature that I’m really excited about is “Hidden Instances” setting. With this setting, you can simply type the hostnames of instances you do not want to see:
Last but not least, if you open “Search”, you now will find the list of trending communities:
This and more is awaiting in Leomard 0.3. Here’s a full changelog:
Added
Added support for "!community@instance" and "@user@instance" in the text. You can now click on them to open the community or user profile
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.
Note: You will have to log in again, because the app now uses a different method of storing the authorization tokens. Sorry for the inconvenience.
Added
Added status indicator when sending a post ...
After a hard week of work, and tremendous help from boscojwho on GitHub, is here! This update brings many, many new features. Of course, we’re still far away from making it 100% feature complete, but it’s slowly getting there: we’ve got multi-account support, uploading photos, searching, support for “@[email protected]” and “[email protected]” links, and more!
This update not only brings new features, but also optimization improvements, which should help with the post load times, app load times and more. Here’s the full changelog:
Note: You will have to log in again, because the app now uses a different method of storing the authorization tokens. Sorry for the inconvenience.
Added
Added status indicator when sending a post (#7)
Added alert when sending/editing post/comment fails
Well, in case of Gimp for Windows, it also doesn’t help that it uses a modified GTK. So, when you start on Gimp on Windows, the program must load all the GTK libraries first, while on Linux the shared libraries are already loaded.
Hi everybody! This is the initial release of Leomard - a native macOS client app written in Swift using SwiftUI. It’s still in very early phase of development, features are missing, but it’s a start. Feedback is most welcome!
Hi everybody! This is the initial release of Leomard - a native macOS client app written in Swift using SwiftUI. It’s still in very early phase of development, features are missing, but it’s a start. Feedback is most welcome!
Hi everybody! This is the initial release of Leomard - a native macOS client app written in Swift using SwiftUI. It’s still in very early phase of development, features are missing, but it’s a start. Feedback is most welcome!
Btw, Lemmy’s HTTP API design choices boggle my mind sometimes. You guys use GET, POST, and PUT, but not DELETE, while also PUT acts partially as PATCH?!
EDIT: Also, why isn’t the bearer token sent in Authorization header?!