![](https://media.kbin.pieho.me/3c/b1/3cb1589e68083e831454c957a89e8171a585c83f6ec7a6b75af5a70cb16b6423.jpg)
![](https://lemmy.world/pictrs/image/0943eca5-c4c2-4d65-acc2-7e220598f99e.png)
41 here. Getting drunk on a Friday wipes me out for a long weekend. It’s touch and go whether I’ll be capable of work on Tuesday.
A #PHP developer who, in his spare time, plays #Tabletop and #VideoGames; if the weathers nice I #Climb rocks, but mostly fall off of indoor #Bouldering ones.
Pronouns He/Him
Blog https://realmenweardress.es
Photos https://pixelfed.social/pieceofthepie
Keyoxide https://keyoxide.org/606B2E3C103A443663DA82716B37390F365AADAA
41 here. Getting drunk on a Friday wipes me out for a long weekend. It’s touch and go whether I’ll be capable of work on Tuesday.
Finally got around to playing Carrion. It’s a great game for the deck and is a massive amount of fun.
ITT people who don’t understand that generative ML models for imagery take up TB of active memory and TFLOPs of compute to process.
Somewhere south of “man flu” but north of “the sniffles”
Promises to recover all fraud, is unable to prove any fraud…everyone wins!
The issue here is that Lemmy is federating out it’s content with the pre blocks containing rendered code fit for some sort of code display plugin/CSS - which KBin doesn’t have.
It would ideally send out the blocks html encoded and would let downstream implementations like KBin or others figure out how to display it themselves. I don’t know how we would fix this.
As a vegan, and a pirate, I approve this message.
This is actually due to the way these platforms work. When a user comments on a comment or post on their instance it will be shown on their instance. It’s then sent on to the owning instance of that comment or post. That owning instance then forwards it on to all interested parties (magazine instance, commenters instance).
Any instance in that chain can refuse to forward or broadcast that message due to a block, but the users own instance will likely always show that post. Ideally they would not do that and would be made aware of a block but that is a bit of a grey area in ActivityPub implementations.
For me that can be answered with 90% of the feature set for 50% of the cost.
It runs the KBin instance I’m using to reply to you :)
Also Adguard home.
When was that update?
Guess I’m missing some lore. Where can I find out more about Q’s involvement (also, why was the footage so… different)
I think I may have had battery saver on at some point in the time since it was last reset but not today no.
This morning I walked the dog in my full autumnal boots, jeans and a Rab padded jacket.
It be cold.
Mmm. Looks like you’ve stumbled across (or at least highlighted) a bug in the way kbin federates out links in it’s content. I thought I’d covered the various cases but apparently didnt.
When a post is made to kbin (or federated into it) that contains !magazineName@instance
it does a best effort to make links that will work for users on that instance, but it appears that best effort applies to the outgoing federated content too - and it shouldnt, or at least, it should do something different.
I’ll get a bug ticket in.
EDIT. For now I’d recommend that where possible you use fully explict links i.e. [{@|!}community@instance](https://instance/{m|c}/community)
No, I won’t, it demonstrably is.
Dessert places. Ice cream, waffles, all that kind of thing. There are a few around here that are always busy 10-12pm.
It’s one of my favourites and is the one I’ve reread the most.
Linus has repeatedly pointed out that, unfortunately, it works. They make way more money from videos that follow this shitty trend.