Bocchi succumbs to pyaa pressure.
Bocchi succumbs to pyaa pressure.
I smell a crime thriller where a serial killer is a programmer and hid their actual child killing searches by masking them as programmer endorsed child killing kind.
I could really use that extension 👀 got a link?
I mean W3C created ActivityPub, it’s only fitting they peruse what they had created
Don’t Louis Rossmann launched a repair wiki a while back?
Anyway, mediawiki wikis have a special page that lets you dump the wiki’s contents for migration purposes, but I forgot whether it’s locked to admins only.
Edit: here’s a publicly accessible export page: https://repair.wiki/w/Special:Export
deleted by creator
Buckshot@programming.dev wake up, new currencies just dropped
People tend to forget ChatGPT learns from people’s comments, like yours.
ah man I wish I saw that one.
“expired without issue” has a whole different meaning to historians/nobility/royalty:
expire: die
issue: children
and thus:
expire without issue: die childless
which is a problem with royalties since it means their line of succession ends.
I see Twitter as a ship too big to maneuver. Then one day it got bought and a new captain comes aboard. He deliberately breaks the hull here and there to make the ship lighter and more agile, and also fired half of the hands on deck. The ship’s taking on water faster now. He also painted over her name. Despite all this, the majority of souls on board would rather sink with the ship than jump overboard.
My guess is that this is going to go the same way as McDonalds v everything with the letters M(a)c, and Starbucks v Sattar Buksh
They devoted every brain cell to scamming people, none is left to detect 200IQ level pranks.
We’re fucking hiding articles behind captchas now? 😒
that’s a major security risk. even the reddit predecessor uses app tokens (though with the death of 3pa idk if such things still work). that’s why I want something that only runs on the client side.
tbf there’s nothing stopping userscripts from stealing your jwt token in the cookie, which is just as big a security risk, but at least with userscripts you can read the source code.
my plan would be similar to that one in which I store the jwt with the scheduled posts, with the notable difference of the data remaining on the browser storage. i wont even need to see any passwords since the jwt is already in the cookie which the script could read off of.
but thanks for the heads up! I’ll ask there about this as well.
I thought this is very well known and needs no explanation lol
I also wish roboragi is here on the fediverse so we can just call him.
“I only watch trashy scumbag creators and not nice ones who actually struggles when engagements really fluctuates on a whim. I also have never been on the other side to emphatize with them.”
It’s like Reddit. If you only consume trash the algo gives you you’re not using it right.
I take supporting creators with engagements seriously.
Nijika-san daijoubu???