• 25 Posts
  • 42 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle

  • In my experience anonymous people online don’t hide their bigotry behind an eloborate 10-point system. In this case, yes. I believe the motivation is exactly as it’s presented.

    The fact that the dev clearly thinks it is a fair justification shows exactly the mindset. The problem is bad enough on its own without making up additional poorly founded accusations.



  • You’re right, I should specify (although the condescension is not helping your case). They are views deemed problematic by the Tesseract dev.

    I’ve had run-ins with other devs or instance admins who find my views problematic, and banned me from their community/instance/whatever. That’s unfortunate, but it’s transparent. People know who the petty tyrants are and act accordingly.

    This is something different.

    Having a frontend preemptively blocking users and instances based on the sole judgment of the dev is unprecedented AFAIK. We don’t need to invent intimations of bigotry to see why this is wholly bad for the platform. It goes against basic principles of transparency, openness, and free choice that the Fediverse is based on.

    I believe that a front-end (client) should be a tool to access the service/network. It shouldn’t be making content decisions. If someone wants to make a block list and publish it for others to use, that’s great. If someone wants to trust an admin for content curation/blocking, well… that’s how this whole thing works. People choose or change instances based largely on that trust. But to have a tool for accessing the network also modifying the content? That’s bad, and a bad precedent.


  • See, THIS is the issue I wish people would focus on. The dev of a pretty important frontend has set up a block list. They have made it the default. They have not applied a clear and equitable criteria, set up a community feedback channel, or any sort of crowdsourced input.

    The modlog is open, meaning that anyone can see exactly what moderators and admins (generally) are up to. People can (and do) push back when things decisions are punitive, arbitrary, or unclear.

    This is not that. You have no way to see why your username was included, or correct it if it was in error. There is no community feedback to direct what standard makes sense.

    That’s the problem. It’s draconian. By manufacturing some shrill accusations of bigotry, yeah, it makes a lot more flashy posts, but doesn’t help in addressing the issue. If we can’t accurately name problems, we can’t solve them. We are just a mob on a witch-hunt.



  • That’s a big distortion. They are accounts that advocate violence or other problematic political views. Many of them are also LGBT, but that’s not why they are on the block list.

    I do think it’s problematic for a client/frontend to default-block any group of individuals or instances at all, but portrayimg it as motivated by bigotry when it’s not is pretty messed up too.







  • Sure. As a fork, it has all of the benefits of Calibre-web. It’s stable, well established, versitile, works well with Calibre desktop software (they are three different projects, despite the similar names). Yet it has a number of different features like automatic ingest, writing/converting files, sending to different devices, etc. There is a pretty complete list on the GitHub page I linked. It has a big community and active development, so its likely that any features you might look for could be coming soon.

    There are other self hosted software projects for ebooks (you can even use Jellyfin!). I had switched to Booklore at one point for a more modern UI and tracking, but it was more flash than execution and ultimately looks like it flamed out over some community issues. There are also projects like Kavita that are designed for features around comics/manga, but also do an excellent job with ebooks in general.

    You should consider two things: what the library looks like, and where it will be read. If it is mostly books with a few other media (like comics, PDFs, etc.), then CWA is probably a good bet. If it’s mostly comics and manga with some books and other media, consider whether Kavita is the better fit. If it is mostly DRM content, and you or if you want to manage it through Calibre Desktop, how does it connect? How often are new books being added and from where?

    What screen will it ultimately be read on? If it’s an ereader, check out the “books” and “self-hosted” communities here on Lemmy for which protocol, etc. is used. If it will be read on a computer or mobile device, what apps are available? Will it be read on multiple devices?

    For example, if it is a small library, read on an Android/iOS device, Jellyfin with JellyBook may be fine. If it is a large manga library already tracked on AniList, Kavita may be a good bet. If features like notes and highlights are important to sync across devices, something like Anx Reader with WebDAV might even be better.

    What OP describes is an excellent setup for 90% of cases.




  • For example, using insider knowledge to manipulate stock markets will lead to the government taking away your earnings and sending you to prison.

    An athlete using their position on the team to change the outcome of a game in order to win bets is generally met with ejection from the team and league, and there may be financial and legal penalties as well.

    Casinos generally have detailed regulations to ensure that their games are fair representations of what is presented.

    I’m not sure what country you’re in, but you should probably take a closer look at the legal codes around sports betting.

    Polymarket itself faces different levels of prohibition in many countries around the world.