MummifiedClient5000

joined 1 year ago
[–] [email protected] 12 points 6 months ago (3 children)
[–] [email protected] 2 points 6 months ago

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.

[–] [email protected] 2 points 6 months ago

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.

[–] [email protected] 1 points 6 months ago (4 children)

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.

[–] [email protected] 1 points 6 months ago (6 children)

What a terrible format.

[–] [email protected] 10 points 6 months ago

Yeah, we don't deploy on Fridays.

[–] [email protected] 70 points 6 months ago

This is not how you raise an issue on Github.

[–] [email protected] 2 points 6 months ago

Rivals hate this one secret trick.

[–] [email protected] 2 points 6 months ago (1 children)

I've kind of mellowed out for a while. I'm still into horror, but the truly disturbing stuff doesn't just doesn't speak to me any longer.

[–] [email protected] 33 points 6 months ago* (last edited 6 months ago) (17 children)

I've seen most of the movies mentioned here 🫠

IMHO, A Serbian Film and Human Centipede 2 have some of the most disturbing scenes I've ever seen. Realizing that they are made for shock value kind of make them laughable though.

SALO is often mentioned in lists of fucked up movies, but it's really not much. There's some poop eating, light rape and someone's tongue is pulled/cut out. It might have been shocking back in the day.

Irreversible made me feel nauseous and had an unsettling feeling from start to end. (Made me vary about Climax, which kind of have a similar feel, but is only fucked up to a much smaller degree). That one for too long scene that just foes on forever makes it the most disturbing film I have ever watched.

Heriditary has some fucked up scenes too and truly scared me. (But Midsommar bearly made an impression on me. Bearly).

Requiem for a Dream made me feel bad about drugs.

Bone Tomahawk kind of seems like an average action/adventurish movie in a western setting until... stuff happens.

Also worth a mention are Martyrs, Ôdishon, The Woman, Inside, The Girl Next Door (not the comedy) and either versions of Funny Games.

May have forgotten some.

(I have no plans to watch any of the Terrifier movies).

Edit: Totally forgot The Heart is Deceitful Above All Things somehow. Man, that is one fucked up movie. "Play with me Daddy".

[–] [email protected] 1 points 6 months ago (1 children)

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?

view more: ‹ prev next ›