I’d seen it in my Firefox/Win10 + uBlockO setup. I just used yt-dlp and then a uBlock “quick fixes” update sorted it.
My meme/shitposting alt, other @Deebster
s are available.
I’d seen it in my Firefox/Win10 + uBlockO setup. I just used yt-dlp and then a uBlock “quick fixes” update sorted it.
I’d seen someone calling all us Kagi fans shills which I thought was stupid at the time, but now I’m starting to see why they might think that.
I don’t know, to be honest - I’m no expert, I just learnt some Arabic whilst living in Jordan.
Levantine Arabic says shamal شمال but that’s might be too slangy for labelling.
I’m not sure I even knew they had a Captcha, I guess I don’t look like a bot.
Apart from that archive.today seemed down yesterday - I was worried they weren’t coming back!
Yeah, which is good, right? Built-in generally works better.
The last section makes me think they can’t be bothered to take it into production. It’s weird; they spend all these words describing the problem and their solution then conclude with but 🤷♂️ no-one really cares.
I use Gboard which does the same, but I also have multiple languages enabled which you switch by long-pressing the spacebar and I regularly trigger the wrong one - very annoying.
I think that forcing links to create new tabs world be a problem. Links working the default, normal way is a feature, not a bug.
Hmm, I’ve just tested an that does seem to be the case, at least as far back as 0.17.4. Do you know when this was added? Or if it’s something that can be disabled?
Looking into Cloudflare Always Online, it uses the Internet Archive’s backup instead of keeping on itself which could explain me seeing zero comments (i.e. IA scraped the page after posting but before any comments). I can’t figure out which page in my history was the post in question, so I can’t be sure.
edit: This start bit is wrong; Lemmy does SSR so Javascript-free/spiders should see at least some comments.
Lemmy is currently pretty terrible at SEO, in large part because the comments don’t load until the JS has run.
This isn’t just a problem for search engines, it affect things like archive.org and offline reading. Earlier today I loaded a page from an instance that had dropped offline - while they had Cloudflare Always Online enabled, the page loaded without comments so it was almost useless.
I think it’s a mistake to consider all the SEO-related concerns as irrelevant just because you don’t care about Google, etc. Most of the things necessary for good SEO are just good practices, with benefits for all users, especially in the areas of accessibility and third-party tools.
I’ve done similar - I have three accounts on three instances and they each have different focuses. This account is meme/shit posting (since Lemmy.ml has access to all of it) and my accounts on smaller instances have the noisy communities blocked so I can see my interests.
Thursday’s patch is the product of recent penetration testing work that the Mozilla Foundation funded, Mastodon cofounder and CTO Renaud Chaput told Ars. He said a firm called Cure53 performed the pentesting and that the code fixes were developed by the several-person team inside the Mastodon nonprofit.
This is good to see, although it’s worrying that such a serious vulnerability went unspotted for this long. At least, I hope it wasn’t spotted; maybe some bad actor’s made subtle use and all our bases are belong to them.
It’s quite funny when it happens that the table makes the best possible hand. Everyone still in shows what cards they were bluffing with and splits the pot.
I’ve had it where I was winning until the final card caused one of these split pots; I’d been betting strong and was hoping no-one would notice that the table held the nuts (they did).