PumpkinDrama

joined 2 years ago
MODERATOR OF
[–] PumpkinDrama@reddthat.com -3 points 2 days ago* (last edited 1 day ago) (6 children)

Lemmy’s approach to privacy is fundamentally flawed compared to other social media platforms. All your posts are permanently public under your profile, with no option to restrict visibility. This means anyone can see your outdated and potentially cringe-worthy posts at any time, and tech companies could likely de-anonymize your profile by analyzing the topics you post about. The open profile design only serves to enable stalking and doesn't contribute anything practical to the site.

[–] PumpkinDrama@reddthat.com 2 points 2 days ago (7 children)

Yeah because first of all, content had to be spread out across 562826 different communities for no reason other than that reddit had lots of communities, after growing for many many years. It started with just a few.

Then 99% of those were created on Lemmy.world, and every new user was directed to sign up at Lemmy.world.

I guess a lot of people here are younger than me and didn’t experience forums, but we had like 30 forum channels. That was enough to talk about anything at all. And I believe it’s the same here, it would have been enough. And then all channels would have easy to find content.

source

[–] PumpkinDrama@reddthat.com 8 points 2 days ago* (last edited 2 days ago) (1 children)

Over the past few days, I’ve witnessed a remarkable surge in the number of communities on browse.feddit.de. What started with 2k communities quickly grew to 4k, and now it has reached an astonishing 8k. While this exponential growth signifies a thriving platform, it also brings forth challenges such as increased fragmentation and the emergence of echo chambers. To tackle these issues, I propose the implementation of a Cross-Instance Automatic Multireddit feature within Lemmy. This feature aims to consolidate posts from communities with similar topics across all federated instances into a centralized location. By doing so, we can mitigate community fragmentation, counter the formation of echo chambers, and ultimately foster stronger community engagement. I welcome any insights or recommendations regarding the optimal implementation of this feature to ensure its effectiveness and success.

[–] PumpkinDrama@reddthat.com 1 points 2 days ago (7 children)

Allowing a user-configurable option to sort posts based solely on the current instance would address this by making the content feed more localized and personalized, helping each instance maintain its unique character and fostering community discovery without being overshadowed by larger instances.

[–] PumpkinDrama@reddthat.com 28 points 2 days ago* (last edited 2 days ago) (18 children)

The issue with Lemmy's "all feed" is that the largest or most popular instances tend to dominate what appears there, which undercuts the ability of users on niche or smaller instances to discover content truly relevant to their specific interests. This make different instances feel less distinct and reduces the value of joining a niche instance. This lack of meaningful, diverse niche content makes federation a moot point—if every instance is just a clone of the same meme and political noise, users gain nothing distinct from joining a smaller or niche instance, turning Lemmy into a less convenient, more fractured Reddit without the depth or polish users expect.

[–] PumpkinDrama@reddthat.com 1 points 2 days ago (5 children)

The decentralized nature of Lemmy, while appealing in theory, creates significant frustration in practice due to widespread instance blocking. Finding an ideal instance becomes a daunting task, as users must navigate a complex web of inter-instance politics and restrictions. The only reliable solutions seem to be either hosting a personal instance—a technical hurdle for many—or simply hoping that your chosen instance’s admins align with your preferences and don’t block communities you enjoy. This politicking ultimately undermines the platform’s potential.

[–] PumpkinDrama@reddthat.com 2 points 2 days ago* (last edited 2 days ago) (12 children)

There were several issues on GitHub regarding proposals on how to solve the low visibility of small communities. However, after the Scaled Sort was implemented, all those issues were closed, yet the problem persists. I continue to use Reddit the same as before because I primarily used it for niche communities, which are lacking here. The few times I’ve posted to a niche community here, I’ve either received no answers or been subject to drive-by downvotes, likely from users not even subscribed to the community. As a result, I now only post on Lemmy when the post is directed to a large community, and I use Reddit for the rest.

 

I'd like to invite you all to share your thoughts and ideas about Lemmy. This feedback thread is a great place to do that, as it allows for easier discussions than Github thanks to the tree-like comment structure. This is also where the community is at.

Here's how you can participate:

  • Post one top-level comment per complaint or suggestion about Lemmy.
  • Reply to comments with your own ideas or links to Github issues related to the complaints.
  • Be specific and constructive. Avoid vague wishes and focus on specific issues that can be fixed.
  • This thread is a chance for us to not only identify the biggest pain points but also work together to find the best solutions.

By creating this periodic post, we can:

  • Track progress on issues raised in previous threads.
  • See how many issues have been resolved over time.
  • Gauge whether the developers are responsive to user feedback.

Your input may be valuable in helping prioritize development efforts and ensuring that Lemmy continues to meet the needs of its community. Let's work together to make Lemmy even better!

 

I'm looking for a federated social media platform that allows for easy topic-based following and blocking, similar to how you can follow or block hashtags on Twitter. On Lemmy, you can follow communities, but there are so many that it becomes overwhelming. I want a platform where I can see or block everything related to a specific tag, and also view only the most popular posts about that topic, similar to how Lemmy communities work. Mastodon, for example, only shows the latest posts, which isn't ideal for trending content. I don't want a chat-like experience; I want to quickly see what's trending about a topic or what's trending in general, while being able to block a few specific topics. Ideally, I wouldn't have to spend hours curating a list of communities or followed users. Does anyone know of a platform that fits these criteria?

[–] PumpkinDrama@reddthat.com -1 points 4 months ago (9 children)

I'm not referring to the amount of content but how it is curated. If it showed the content sorted by votes from the local instance instead of an aggregate of all instances the content would differ form instance to instance.

 

I've noticed that the "All" feed on Lemmy is pretty much the same across all instances, showing posts from every instance regardless of the specific focus or community vibe of the instance you're on. This seems like a missed opportunity to make the experience more tailored and engaging for each instance's unique audience.

For example, if there were an instance dedicated to literature lovers, wouldn't it make sense for the "All" feed on that instance to prioritize content that's more relevant to people who enjoy books, poetry, and writing? Instead of being a global feed that shows everything from memes to tech news, it could reflect the interests and values of the instance's community.

I feel like making the "All" feed more tailored to each instance would not only improve user experience but also strengthen the sense of community within each instance. What do you think? Would love to hear everyone's thoughts!

[–] PumpkinDrama@reddthat.com 3 points 8 months ago (2 children)

As long as I'm not looking at it I'd feel more comfortable with it that being surrounded by mosquitoes. Would you rather be surrounded by mosquitoes than be in the same room as that thing?

[–] PumpkinDrama@reddthat.com 3 points 8 months ago

You are overcomplicating the issue by suggesting a "favorite" option when there is already a "subscribe" option. At the very least, consider proposing something distinct that helps users discover more of the small communities they are subscribed to, rather than suggesting something that has already been implemented.

[–] PumpkinDrama@reddthat.com 6 points 8 months ago* (last edited 8 months ago) (8 children)

Although there were some proposed solutions for this issue, when scaled sort was implemented, @nutomic@lemmy.ml closed all related issues, even when they weren't being solved by scaled sort. So, it's clear that since there are no longer any open issues about this, no one is going to care about solving it. Therefore, it seems like the only option is to accept this fact and learn to cope with it. At this point, I've come to terms with the fact that Lemmy is mainly a platform for shitposts, while Reddit is for everything else. When I look at the feed, I mostly see memes, US politics, and some tech.

Custom feeds may not be the most efficient solution due to scalability concerns. However, an alternative approach could be to make the metadata about the posts (votes, comments, etc) available through an API call. This would enable users to develop their own algorithms for content discovery and potentially create a more personalized experience. Users could then implement, share and install these algorithms using tools like Tampermonkey or other userscript managers.

 

To automatically and recursively download subtitles for all videos in a directory on Arch Linux, you have several options. Here's a comprehensive approach using some of the tools mentioned in the search results:

Using Subliminal

Subliminal is a powerful command-line tool that can recursively search for video files and download subtitles for them[1].

  1. Install Subliminal:
sudo pacman -S subliminal
  1. Use the following command to download subtitles recursively:
subliminal download -l en /path/to/your/video/directory

Replace "en" with your preferred language code and adjust the directory path as needed.

Using QNapi

QNapi is another excellent option for downloading subtitles[5].

  1. Install QNapi:
sudo pacman -S qnapi
  1. Use QNapi in console mode to download subtitles recursively:
find /path/to/your/video/directory -type f \( -name "*.mp4" -o -name "*.mkv" -o -name "*.avi" \) -exec qnapi -c {} +

This command finds all video files with .mp4, .mkv, or .avi extensions and passes them to QNapi for subtitle download.

Using yt-dlp

While primarily used for downloading videos, yt-dlp can also download subtitles for local video files[2].

  1. Install yt-dlp:
sudo pacman -S yt-dlp
  1. Use the following command to download subtitles recursively:
find /path/to/your/video/directory -type f \( -name "*.mp4" -o -name "*.mkv" -o -name "*.avi" \) -exec yt-dlp --write-sub --sub-lang en --skip-download {} +

Replace "en" with your preferred language code.

Using OpenSubtitlesDownload

OpenSubtitlesDownload is a Python script that can be used to download subtitles[3][4].

  1. Install OpenSubtitlesDownload:
yay -S opensubtitlesdownload
  1. Use the following command to download subtitles recursively:
find /path/to/your/video/directory -type f \( -name "*.mp4" -o -name "*.mkv" -o -name "*.avi" \) -exec OpenSubtitlesDownload.py {} +

Additional Tips

  • For all these methods, you may need to adjust the file extensions in the find command to match your video file types.
  • Some of these tools may require you to create an account on the subtitle service they use (e.g., OpenSubtitles.org).
  • If you encounter rate limiting issues, you may need to add delays between downloads or use a tool that handles this automatically.

Remember to respect copyright laws and the terms of service of the subtitle providers when downloading subtitles.

Citations: [1] https://www.tecmint.com/best-linux-movie-subtitles-player-software/ [2] https://wiki.archlinux.org/title/Yt-dlp [3] https://aur.archlinux.org/packages/opensubtitlesdownload [4] https://bbs.archlinux.org/viewtopic.php?id=162416 [5] https://man.archlinux.org/man/qnapi.1.en

 

To synchronize your home directory between two Manjaro systems using rsync, you can follow these steps:

Preparation

  1. Ensure both systems are connected to the same network.
  2. Install rsync on both systems if it's not already installed:
sudo pacman -S rsync
  1. Determine the IP address of the destination system:
ip addr show

Syncing the Home Directory

To sync your home directory from the source system to the destination system, use the following command on the source system:

rsync -av --update ~/ username@destination_ip:/home/username/

Replace username with your actual username on the destination system, and destination_ip with the IP address of the destination system[1][2].

Explanation of the Command

  • -a: Archive mode, which preserves permissions, ownership, timestamps, etc.
  • -v: Verbose mode, which provides detailed output of the sync process.
  • --update: This option skips files that are newer on the receiver side.
  • ~/: This is the source directory (your home directory on the current system).
  • username@destination_ip:/home/username/: This is the destination, specifying the user, IP address, and path on the remote system[1][3].

Additional Considerations

  1. SSH Key Authentication: For a smoother experience, set up SSH key authentication between the two systems. This eliminates the need to enter a password each time you run rsync[4].

  2. Exclude Files: You might want to exclude certain directories or files. Use the --exclude option:

    rsync -av --update --exclude '.cache' --exclude '.local/share/Trash' ~/ username@destination_ip:/home/username/
    
  3. Dry Run: Before performing the actual sync, you can do a dry run to see what would be transferred:

    rsync -av --update --dry-run ~/ username@destination_ip:/home/username/
    
  4. Bandwidth Limit: If you're concerned about network usage, you can limit the bandwidth:

    rsync -av --update --bwlimit=1000 ~/ username@destination_ip:/home/username/
    

    This limits the transfer to 1000 KB/s[3].

  5. Incremental Backups: The --update flag ensures that only newer files are transferred, making subsequent syncs faster.

Remember to run this command from the source system, and ensure you have the necessary permissions on both systems. Always double-check your command before running it to avoid unintended data loss or overwriting[2][5].

Citations: [1] https://www.bleepingcomputer.com/forums/t/748252/a-guide-to-backing-up-your-home-directory-using-rsync/ [2] https://www.reddit.com/r/linux4noobs/comments/qtu0ww/backup_and_restore_home_directory_with_rsync/ [3] https://www.cherryservers.com/blog/how-to-use-rsync-on-linux-to-synchronize-local-and-remote-directories [4] https://www.tecmint.com/rsync-local-remote-file-synchronization-commands/ [5] https://www.digitalocean.com/community/tutorials/how-to-use-rsync-to-sync-local-and-remote-directories [6] https://stackoverflow.com/questions/9090817/copying-files-using-rsync-from-remote-server-to-local-machine/9090859 [7] https://www.heficed.com/tutorials/vps/how-to-use-rsync/

 

To install all programs from one Manjaro system on another, you can follow these steps:

Export Package List

On the source Manjaro system:

  1. Open a terminal
  2. Run the following command to export a list of explicitly installed packages:
pacman -Qqe > packages.txt

This will create a file called "packages.txt" containing the names of all explicitly installed packages[1].

Transfer the Package List

Transfer the "packages.txt" file to the target Manjaro system. You can use various methods like USB drive, network transfer, or cloud storage.

Install Packages on Target System

On the target Manjaro system:

  1. Open a terminal
  2. Navigate to the directory containing the "packages.txt" file
  3. Run the following command to install all packages from the list:
sudo pacman -S --needed - < packages.txt

This command will install all packages listed in the file, skipping any that are already installed[1].

Additional Considerations

  • AUR Packages: The above method only covers official repository packages. For AUR packages, you'll need to install them manually or use an AUR helper like yay[2].

  • Configuration Files: Remember that this process only installs packages, not their configurations. You may need to transfer configuration files separately.

  • System Differences: Be aware that some packages might not be compatible if the two systems have different architectures or Manjaro versions.

  • Updates: After installation, run a system update:

sudo pacman -Syu
  • Cleaning Up: You might want to remove unnecessary packages on the target system:
sudo pacman -Rns $(pacman -Qtdq)

This process should help you replicate most of the software environment from one Manjaro system to another. However, always review the package list before installation to ensure it's appropriate for the target system[1][2].

Citations: [1] https://www.reddit.com/r/ManjaroLinux/comments/ifowrz/how_to_install_software_in_manjaro/ [2] https://github.com/manzurahmed/manjaro-software-installation-guide [3] https://www.youtube.com/watch?v=82YinI2Cgbc [4] https://www.youtube.com/watch?v=VTE4vtrvIM4 [5] https://forum.manjaro.org/t/install-software-from-terminal-cd-downloads-in-manjaro/88674 [6] https://forum.manjaro.org/t/how-to-install-software-over-applications-in-manjaro-hello/110060 [7] https://forum.manjaro.org/t/how-to-install-apps-on-manjaro/84114 [8] https://forum.manjaro.org/t/how-to-install-new-software/141060

view more: next ›