And my axe!

May I see it?

Partially agreement. There shouldn’t be markdown in titles and Lemmy should probably have stripped it altogether: https://github.com/LemmyNet/lemmy/issues/3828

Disregarding the malplaced markup in the title, the article link is also broken. (Contains broken markup).

And again the multiple indentations and “cross-posted from” makes it look like Re: Re: FW material. I think my criticism is valid, even if I probably did sound a bit like a dick about it.

The writer uses the terms “locked out” and “frozen”, but also says that she is not allowed to share documents any longer and maybe unable to access her documents from a tablet and a phone, but perhaps still from a laptop? (The article reads like a fucken drama piece instead of… you know… actual journalism).

If she has any type of access, it seems like it is very easy to fix permanently:

• Download documents.
• Register a domain.
• Get a hosted Wordpress or some other foolproof CMS.
• Put documents there.

Don’t rely on a free service for something that has value you.

Here’s a screenshot showing what the post looks like for a Lemmy user.

What’s with the title? It’s just a tag and a URL. Tags do nothing on Lemmy and look awful. URLs in titles also do nothing and look awful. And what’s with the a escaped #-character? Is it to safely pass the title in bash-scripts?

The article link is broken. And the multiple levels of crossposting just seems kind of… lazy.

This is some next generation RE: FW: FW stuff.

What a terrible format.

Rivals hate this one secret trick.

We all need glasses to see Tiny Lena Headey.

This has huge potential. What I personally look for in a podcast solution is:

• Web/desktop player
• Sync between players (down to seconds)
• Organize subscribed podcasts with folders/tags
• Per podcast/folder/tag settings for “automatically add to queue”
• Some way of dealing with older (backlog) episodes (built-in or via an API)

For now, I’m using Pocketcasts which pretty much does what I need, except for handling the backlog, which I do with a homemade python-script that adds backlog episodes to my playlist whenever it has less than 4 hours of playtime left, using Pocketcast’s web player REST API. The result is an endless playlist where newly released episodes are played within a few hours and older episodes are sprinkled on with no real need for micro-managing episodes in the playlist.

It looks like web/desktop players and sync is already in scope, but are there any “advanced” podcast organization features on your roadmap?

That is not correct. Prowlarr also searches Newznab-compatible providers (i.e. most nzb-indexers).

One kilo of assorted cheese apples, please.

Woods porn.

Changing the original headline of an article into semi-gibberish? That’s a downvote.

Not all sheep. Some prefer wool-vos.

So the title of the post should be “When a stranger ties their dog to another stranger’s bike.”

The epitome of Danish design: The Kay Bojesen Monkey

If you can fit at least two people inside a thing, that thing will be fucked in.

She’s Dad now.

That’s gonna fuck up downloading for me…n of the pirate persuation.