![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/2QNz7bkA1V.png)
And my axe!
And my axe!
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:
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.
This is not how you raise an issue on Github.
Rivals hate this one secret trick.
This has huge potential. What I personally look for in a podcast solution is:
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).
More snake than bear.
Changing the original headline of an article into semi-gibberish? That’s a downvote.
Greybeard elitism used to have much more substance back when not just anyone with a webbrowser and a beard could voice in.
Robert Del Naja (of Massive Attack) is Banksy. You’re welcome.
If you can fit at least two people inside a thing, that thing will be fucked in.
I guess most people are kind of ashamed to admit that they’ve been duped by racist talking points and Russian disinformation campaigns.
Did you literally type kill -9 firefox? Because the kill command normally takes PIDs not process names. killall takes process names, but process names are not always straightforward. Under normal circumstances firefox would exit when X/Wayland goes away though.
Using the sysrq key in the “reverse BUSIER” sequence when your system won’t shutdown/reboot is always better than shutting the power on a running system.
I’m not familiar with the TRegExpr engine and its quirks, so I could be wrong about some or all of this, but let’s try anyway:
The characters in the brackets describe a set of characters, but without any quantifier after the brackets, they will only match a single character. If you want to match an entire string, you should begin the regex with a ^ character (which means “start of string” when outside brackets), have a quantifier such as * or + after the list and then end it with $ (“end of string”).
The ^ character reverses the list, so it will match any characters not in the list. This may be what you want (i.e. to copy all the files that matches because they do not contain the characters in the list), but I feel that it should be mentioned.
I suspect that you may need to escape the / character with a . And since the error message mentions * and ? I’d also try escaping those.
So to match only the filenames that are FAT32 safe, I’d try something like this:
^[^\\\/:\*\?\"<>|]+$
https://regex101.com/ is a great site for learning regex so I’d recommend that you try it out there (and keep in mind that different regex engines can have subtle differences, but sadly the site doesn’t do TRegExpr).
Tailscale is an easy and secure way of getting access to your local network.
Mobile fuck shack.