I'm dumb. I assumed it was a mod I was replying to.

Oh, great! I somehow overlooked that community.
I see that you are mainly uploading images to catbox or using direct links of the source image. Which is fine but on the lemmy website, sometimes thumbnails are missing and some posts cannot be expanded so you have to open link in the new tab. That is the only reason why I was asking that question in my post. But it's not a big deal.

What do you think about adding a rule to have Imaginary[something] in the title just so that you could use it as a search query to find specific art, since we don't have all of those separate, specific communities?

I was thinking about having a list of possible Imaginary "categories" in the sidebar, and when someone is making a post, they could just pick one that is fitting.

This is a list from Imaginary network on reddit that I grabbed, that could be potentially used. And you would just pick one subcategory or if you are not sure about specific one, you could put a category instead.

Haha, I'm not sure what you mean by that. I'm simply wondering if having someones artwork uploaded on a lemmy instance (even if credited) can cause copyright issues. I don't really know how that works.

Edit: Maybe I'm wording it incorrectly. I'm talking about someone filing a DMCA complaint / "unlawful reproduction or distribution of their work"...

No, the images would be untouched. And those don't really contain copyrighted characters either.

The reason to upload it directly to an instance would be just for better combability with lemmy (some image links may not show correctly on lemmy, or may be missing the thumbnail...)
On reddit, they upload it directly, and link the source.

Did you maybe miss the linked article? :D

I also found out that Tesseract (Source) Has the word filtering in the settings.

On Android, it's probably a little utility software called Quick Cursor (it's not FOSS). It's incredibly convenient being able to spawn a cursor on your phone from thin air that you can use to reach the "unreachable" portions of your screen, especially if you are holding your phone with one hand. Besides being a "phone touchpad" it has a bunch of ways of triggering actions/shortcuts, for example: volume or brightness control, launching an app (I use it for launching a floating calculator, notes...), opening notification shade, copying text (it can copy any text that is under the cursor, even if it's not selectable)...

It's not that I couldn't go without it, but it changed the way I use my phone and it would feel really weird without it. It feels like it should be a part of the OS.

Keepass XC on PC, Keepass DX on Android, Syncthing to sync database

Works flawlessly!

• mpv (video player)
• Logseq (knowledge base/journal)
• KISS launcher (android launcher)
• OpenTracks (fitness tracking)
• BreezyWeather (weather)
• KDE connect (app to do shit between pc and phone)
• Tasks (todo)
• AntennaPod (podcasts)
• Hacki (hacker news)
• FlorisBoard (keyboard)
• Unexpected Keyboard (another keyboard)

Oh shit!

This post actually made me look for a solution and I found one!
Solution to opening tiktoks without using tiktok app or site, not how to stop ur friends sending u garbage.

It made me think... mpv player can play basically any link you throw at it (thanks to yt-dlp), and we also have mpv on Android, so why can't we do it there as well. And sure enough, I found this https://github.com/mpv-android/mpv-android/pull/58, someone baked yt-dlp in mpv for Android, making it possible to open link in mpv (share >> play in mpv)

It works for instagram and all other shit.

Imagine if everyone who made this kind of post, made a post on their fav niche sub instead.

Quote from some old guide:

The Importance of Being Connectable:

When it comes to torrents, being connectable can go a long way in helping your ratio. Connectivity is directly related to port forwarding, your router, and incoming torrent connections. Here's how it works:

You upload a new torrent. After going through the upload page and adding the torrent to your client, the client connects to the tracker to do the following:

1. Tell the tracker it is going to begin seeding a torrent.
2. Ask the tracker if there are any peers it doesn't know about.

Normally, no one has downloaded the torrent from the site between the time that you upload the torrent and when you add it to your client. So your client will now wait, for 45 minutes (or however long it's been told to wait by the tracker), until it will connect back and ask for more peers.

Now suppose someone downloads your torrent from the site after you added the torrent to your client. Normally, the person's client will ask the tracker for peers, to which the tracker will return your IP address to connect to. That client will then connect to your client, using the IP address and port number it got from the tracker pertaining to your client and the port it accepts incoming connections on. This is where being connectable comes into play. We'll assume your IP address is 139.129.43.5 and your port number used for torrenting is 3058.

When the peer attempts to connect to you on that designated port, your router has to know what to do with the incoming connection. It receives an incoming connection from the peer, on port 3058. If you have your port forwarded to your client correctly, that is, you've told the router what to do with incoming data on a specific port, the router knows to send anything coming in on port 3058 to the computer your client is running on. Now, if you are not connectable, the router doesn't know what to do with items coming in on port 3058, so they are discarded, and the other peer isn't able to connect to you.

If your port isn't forwarded correctly, the peer who just added your torrent to their client will have to wait for 45 minutes, until your client updates with the tracker, and gets the new peer's IP address and port to connect to. If the peer is connectable, you will then make an outbound connection to them, and it will connect successfully. Outbound connections aren't normally blocked by a router, unlike incoming ones, this is why a client doesn't need a port forward for outgoing connections. This scenario is also why you can still seed even if you aren't connectable. This can have very negative consequences for your ratio though as I will now explain.

Here's how not being connectable will hurt you. When you are seeding a torrent in a large swarm and a new peer comes online, his client will attempt to make connections to the other peers. If you aren't connectable, you will have to wait (at max) 45 minutes until your client learns of their existence, before you can start uploading data to them. During this time the peer is getting data from other peers, but not you. By the time your client finally learns of the new peer's existence, the client will already be done downloading! You won't get nearly as much upload than if you were connectable. Depending on the size of the torrent, your client may not get any upload for that peer, because he will have completed the torrent before your client even knew he was present.

The absolute worst case scenario is when both peers aren't connectable. Neither peer will be able to connect to the other, and both will sit without connection indefinitely.