As the title says, I got tired of hearing about twitter and reddit so provide this userscript a comma separated list of keywords and you will no longer see posts containing those keywords. I'd love to see this functionality built into Lemmy itself, but until then here's a userscript.

Repo link

You may have seen my previous post over here, after I had just gotten everything setup initially.

I've now expanded this with an additional script, a github repo, and proper documentation.

Here's a cleaner explanation:

I've taken on the challenge of self-hosting more of the services I regularly depend on. The latest target is Spotify. This meant I needed a simple and convenient way to listen to my music from anywhere, get new music into my collection, and also still receive recommendations based on my interests and listening habits.

I now have what I think is the pretty ideal setup, here's what it includes:

• A 24/7 radio station that plays my entire catalog (link here if you're interested). This is powered by Azuracast along with the scripts in the repo. The station link is using the Public Pages feature in Azuracast with a bunch of custom CSS.

• A Spotify-like experience that also supports mobile and offline. This is powered by Navidrome for web/desktop and Substreamer for mobile. Substreamer connects to Navidrome using the Subsonic API.

• A couple of scripts that allow me to easily download tracks/albums/playlists from Spotify and Youtube. I used these to bootstrap the collection and export my existing playlists from each service.

• A couple of scripts that automatically grab my latest recommendations from Spotify and LastFM, add them into Navidrome, and provide me a nearly fully automated way to parse out tracks I want to keep permanently.

That last point is the most interesting part in my opinion. Both scripts run on a weekly cron job that downloads my Discover Weekly playlist from spotify, and current recommendations from LastFM. It then creates a playlist for each source for that weeks collection and moves it into Navidrome.

I then browse that weeks playlist at my leisure, using the "star" feature in Navidrome to decide what to keep. Once I'm done I run another script manually that takes all of the starred tracks from those two playlists and moves them into my catalog, and then deletes the remaining tracks and the playlists.

This means I just need to go through and listen to recommendations and click a button on what to keep, and the rest is discarded automatically. It really doesn't get any simpler than this!

What remains will then be available for on-demand playback through Navidrome and also added to the full catalog that powers the 24/7 radio station.

FAQs from the last thread

What is being used to download from X? - spotdl is being used for Spotify.pytube is being used for LastFM and Youtube. spotdl is also just downloading tracks from Youtube under the hood.

What is the audio quality of the downloaded tracks? - Since these are coming from Youtube, everything is a 128kbps VBR Opus codec. It's certainly not FLAC but it's good enough for my enjoyment.

This is a semi-private instance, but feel free to post.

This is a test of the body length. Let's see how much shorter it needs to be for this layout to work properly

Working on a web app so I need test content

Working on a web app so I need test posts

I'm doing some testing in my mobile app so I need different links

Learn more about Fediseer here!

! !

Fediseer is a new tool from /u/[email protected] that employs a Chain Of Trust mechanism to help create a network of whitelists for Lemmy instances that are not home to spam and botting.

Inclusion in this network does not make any guarantee about the nature or quality of the posts on an instance, only that it's not being used as a platform for launching malicious attacks against the broader fediverse.

Huge thanks to /u/[email protected] for helping me figure this one out.

A game where you must devise a password that meets a list of requirements that grow in number, complexity, and absurdity

0.18 is now officially available. I expect it will be a few days as instance owners test the upgrade and decide whether or not to switch over. Especially since the captcha fix isn't coming until 0.18.1.

Relevant to this community is the fact that this upgrade includes two different PR's (1, 2) that add a number of semantic classes and ID's to the markup to aid in the creation of custom themes, userscripts, and browser extensions. Additionally the UI has been upgraded to use Bootstrap 5.

However it should be noted that Desallines has explicitly stated that there is no official support for anything utilizing these classes, and that the UI framework is going to be changed in a future update.

This means you're targeting these classes/ID's at your own peril, and they may break in a future update. They want to keep theming as light as possible rather than adding lots of custom hooks that people will then become dependent on and expect ongoing maintenance/support.

cross-posted from: https://lemm.ee/post/177673

Cross posting this here for visibility since lemmy.ml federation has been very hit or miss the last week. Original post from @[email protected]

> Today, a bunch of new instances appeared in the top of the user count list. It appears that these instances are all being bombarded by bot sign-ups. > > For now, it seems that the bots are especially targeting instances that have: > * Open sign-ups > * No captcha > * No e-mail verification > > I have put together a spreadsheet of some of the most suspicious cases here. > > If this is affecting you, I would highly recommend considering one of the following options: > 1) Close sign-ups entirely > 2) Only allow sign-ups with applications > 3) Enable e-mail verification + captcha for sign-ups > > Additionally, I would recommend pre-emptively banning as many bot accounts as possible, before they start posting spam! > > Please comment below if you have any questions or anything useful to add.

cross-posted from: https://zemmy.cc/post/26356

> There have been a number of ongoing conversations and PR's around trying to add semantics to the lemmy-ui markup to enable developers to more easily create custom themes, userscripts, and browser extensions. > > Up until now we've had no input from a maintainer, as they are rightfully heads down focused on shipping the 0.18 update. We now have direction on where we should be focusing our effort and to what extent the project will offer support for this: > > > ...I'm fine with adding something like this, with the very bold caveat that we as maintainers will not do custom theme support, and if class names change, and themes break, that is up to themers, not us. I've had to close so many issues on this repo for people asking me to do theming support for them, which I don't have time to do. > > This is great news for anyone who has been struggling with incredibly deep class selectors and general lack of specificity. There is further mention of switching UI frameworks in the future, so do expect that whatever you build today may break tomorrow. We're still in the very early days of the Lemmy maturity lifecycle, but it's encouraging to receive acknowledgement for this effort. > > Relevant links to the various efforts in addition to the post link: > > * jsit's proof of concept for classes > > * My PR to add classes and ID's (merged) > > * djv's thread that started their (post linked) PR > > * A thread from 2022 where Dessalines laid out their original motivations for resisting custom classes >

There have been a number of ongoing conversations and PR's around trying to add semantics to the lemmy-ui markup to enable developers to more easily create custom themes, userscripts, and browser extensions.

Up until now we've had no input from a maintainer, as they are rightfully heads down focused on shipping the 0.18 update. We now have direction on where we should be focusing our effort and to what extent the project will offer support for this:

> ...I'm fine with adding something like this, with the very bold caveat that we as maintainers will not do custom theme support, and if class names change, and themes break, that is up to themers, not us. I've had to close so many issues on this repo for people asking me to do theming support for them, which I don't have time to do.

This is great news for anyone who has been struggling with incredibly deep class selectors and general lack of specificity. There is further mention of switching UI frameworks in the future, so do expect that whatever you build today may break tomorrow. We're still in the very early days of the Lemmy maturity lifecycle, but it's encouraging to receive acknowledgement for this effort.

Relevant links to the various efforts in addition to the post link:

• jsit's proof of concept for classes

• My PR to add classes and ID's (merged)

• djv's thread that started their (post linked) PR

• A thread from 2022 where Dessalines laid out their original motivations for resisting custom classes

I created this server so that I could own my account across the lemmyverse and to provide a way for friends to try out the platform. Don't expect to see proper communities and content here as you would on someplace like lemmy.world or beehaw.org.

That said, you are welcome to post here in any relevant communities (of the few that exist), such as Testing, where I have a post passerby's have used to make sure federation is working.

This comes to us courtesy of @[email protected]. As a technical person I sometimes find it difficult to communicate with my friends about the value proposition of Lemmy and other federated platforms.

The reality is 99.9% of people are going to instantly tune out the moment they hear "federation", "decentralized", or "self-hosted". These things all existed before the centralized social media hellscape we have today, but those centralized platforms gained dominance because they were able to package their value into a simple pitch: "Your one-stop shop for social!"

Another good example of this is comparing the current state of the official Lemmy website to the official Mastodon website.

Mastodon spends the first 2 page scrolls offering you a visual explanation of what their platform offers, a cohesive and familiar social experience. It's not until you get 1/3 into the page that you see the words "open source", and the word "federation" doesn't even appear in the main copy, it's used in a user testimonial towards the bottom of the site.

Lemmy's site on the other hand has an okay paragraph of copy about it's value proposition, but then spends the first two image tiles and blurbs showing and talking about its source code and infrastructure, with only the third referencing moderator tools.

The following section talks about self-hosting and the fediverse, with only a brief mention to the core value proposition. I could go on about the remainder of the site but by this point it's likely that the majority of users who weren't already seeking this and/or are technically inclined have left.

Communicating the value of these things is difficult and something we're going to need to focus on improving both as platform providers and as users of that platform. That's why I'm so enamored with this video from Nina. It is quick and to the point, it only communicates what needs to be said for anyone to understand the value prop, and it does so in a way that doesn't invoke any of the exclusive terminology.

Thank you for coming to my TED Talk rant.

Notably for this community is the inclusion of the "lemmy-site" class on the #app div