muhyb

@[email protected]

This profile is from a federated server and may be incomplete. View on remote instance

muhyb ,

username checks out

muhyb ,

Except it won't be their most important data. Either their very first files from their desktop (up to 5 GB), or random 5 GB files (no idea which). Once it's filled quickly, it will start nagging about buying more storage.

Firefox 127's private window handling angers users ( www.theregister.com )

There used to be an option called browser.privateWindowSeparation.enabled, which ever since Firefox 106 back in October 2022 resulted in separate taskbar icons for normal and private Firefox windows. In version 127, this option has gone away, removed in this code change. Users complained on Mozilla's forums and on Reddit at the...

muhyb ,

Is this a Windows problem I'm too Linux to understand?

muhyb ,

Steve is Irish >> Steve O'possum

muhyb ,

There is PSPSPS

muhyb ,

Why the LTT logo though? Use something original maybe?

muhyb ,

Nice software gore

muhyb ,

Also featuring Dante from Devil May Cry Series.

muhyb ,

That's great news. It seems Osmin is matured enough. I should give it an another shot soon.

muhyb ,

I personally use ext4 everywhere but it is recommend to have BTRFS for your OS partition if you take snapshots often.

muhyb ,

pfetch gang

muhyb ,

That's weird, isn't Google Play already updating apps without asking?

(QKSMS master race btw)

muhyb ,

I see. It seems it's not the out of the box setting but can be opt out.

muhyb ,

Not at all! Developers should stay away from that abomination, especially open-source devs.

muhyb ,

Never go for user-submitted / approved by moderator system. I've been in one project like that years ago and it's not gonna work.

I'll make another comment once I get up.

muhyb ,

It's a slow system. MAL takes user submissions because they already have a big database and those submissions help filling the cracks. If you don't have a database to begin with it slows things down, especially if these submissions will go by trust-based. Doing this by randoms is also very risky.

However, I'm not completely oppose to that idea because it can be helpful for some areas. My suggestion is start with a basic dog tag system, where the anime name, alternative names, status (airing, completed), season and start date, studios (also licensors and producers), age rating etc. These information needs to be scraped for the fastest way to form a quick database, they are publicly available (even on Wikipedia) so it should be fine to scrape. You can even go full Wikipedia after got only the names. User submissions could be useful for the introduction / summary parts of the titles at this stage. For only names (and basic tags), you can scrape AniDB from this list. It's just a search query so shouldn't be against their ToS.

You can also check Kitsu for ideas, I like their DB request system. Pretty basic but can be done differently with the power of ActivityPub.

muhyb ,

Didn't know about Jikan API. After a quick look at their docs, I think it should be a steady source for scraping.

For features, can be done a lot with ActivityPub. Of course the most wanted features would be a watchlist / episode tracker (and possibly an importing from the lists people already have, I switched to Kitsu from MAL that way) but just thinking about federating the all anime/manga titles with basically their own communities out of the box sounds great. Good luck with the project!

muhyb ,

Noticed the edit:

For hosting images, you can go alternatives like some Lemmy sites do: Mirror everything automatically to Internet Archive.

I think people would want to self host, because they will get all the anime/manga titles with their communities out of the box and can moderate their own sites while their users can react to any other community via federation.

muhyb ,

Both have ups and downs. Assuming these lists will be in the code, do you have an estimation how big would that be? If you think they won't strangle the code, just go with it. Something like storing them in JSON and loading them when needed could be better for optimization though.

You can also do some best of both worlds, like not creating the communities beforehand but make the titles searchable from the database open for all users. That might require a bigger traffic from hosting side though, but it should be OK since these will be spread to all self hosted communities.

I think you can also ask some of your questions to selfhosted communities.

muhyb ,

That's a noble concern. I just gave an example there since some communities do that but yeah it would be better if not done I guess.

Also mentioned on other reply but you can ask this to !selfhosted and probably will get an optimized answer regarding that issue.

muhyb ,

You're welcome, and good luck!

muhyb ,

Well, since 100k titles would make a pretty big database, at least storing the metadata like years, seasons, genres etc as hardcoded could make it run faster than going full-fledged JSON, at least I meant that. However this will be an open source project and there will be localizations, so now it doesn't look like a good idea to me somehow.

muhyb ,

Sorry for the confusion. Don't take my words literally, I'm not an expert on databases. I use JSON for my job and it's enough for me, so use what database your project needs. But by full-fledged I meant completely leaning on databases which may slow some things down for the server side. However I now checked PostgreSQL and it seems much better for large datasets, so I don't think that would be a concern for you.

muhyb ,

Yeah, that would be nice for the running seasons I guess. Maybe even a couple years worth seasons since most of the traffic will come from those.

muhyb ,

Unlike Reddit, you can edit titles on Lemmy.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • kbinchat
  • All magazines
    •