Just wonking about on the internet… oh look, a bee.
Only in the same way that stealing code from a PoC would make me racist, stealing code from a Jew would make me anti-semitic or stealing code from a woman would make me sexist.
Since, without proof of any of that you’re just making shit up I’m going to go with the reason that your post is being downvoted is that ITS JUST FUCKING STUPID.
I believe that the term Microblog originated out of Tumblr. Probably wrong in that though.
Yeah. PHP is not a speed limiting factor unless you’re calculating Pi to X million digits. Almost everything about ActivityPub is limited by network IO.
A number of kbin instances already have. But not .social - which is obviously the largest instance.
Aggravatingly .ml users can browse and interact with kbin magazines just fine as we let them in. It’s very much a bad faith thing at this point.
Not really suspicion at this point. They are proveably 403 rejecting requests from the KBin useragent. You have the letters “kbinbot” anywhere in your useragent (case insensitive) you ain’t getting content.
As a bonus they’re still sending out stuff to instances though. But since KBin can’t then resolve it it amounts to a DoS attack as the messages just build up in KBin retry queues.
The law: You can’t collect data without consent
The intent: Sites stop collecting data without consent
Sites interpretation: So I ask for consent right? right??
Not true.
Both Lemmy and KBin map the same activitypub activities to the same upvote and downvote actions.
Boosted and upvoted because I think you’re right. 😀
Not only hosts it. Wrote it. There’s a small team now but its mostly all him at this point.
This isn’t the case though? Upvotes (aka favourites everywhere else) are what affect the “algorithm” the functionality thats broken is Karma tracking.
Yeah. That is sadly #JustFederationThings.
In your case if you copy the full handle of the magazine from those results and use the actual search functionality kbin with go off and find it and then it will show up in those first results.
Because otherwise you end up with multiple copies of communities all sharing the same name with no clear distinction.
Thing is. That’s no different to anything your average reddit migrator would have done? This sub about topic slow? boring? full of trolls? Search for another. Oh look, there’s this other one with the similar name, it’s got more people on it, I’ll sub to that too.
The literal only difference is that now the alternatives can have the same name*
*assuming you ignore the @instance.domain bit at the end.
It has an option to always show what instance communities and users originate from.
If the concept of federation is confusing or daunting why would having it be more visible help? Genuine question.
Sign up, browse stuff, comment on stuff, curate your feed by subbing, all the other details are just noise.
Caveat: Unless you’re on a small instance that isn’t aware of the communities you might want. But let’s face it, if the concept of federation is confusing you you probably didn’t join some micro instance hosted by your mate Joe.
Not to mention that the defacto package manager (composer) blows NPM out of the water in basically all metrics. From what I understand most languages package managers now look up to or even model themselves on it.
Large parts of my particular departments .gov.uk stack are PHP. All modern (8.1+) using established frameworks and to be honest, it’s a joy. It’s quick to write, easy to understand and very easy to test. The write, run, debug cycle is also essentially instant; although I really enjoy using Go (another bit of the stack) being able to quickly iterate changes is something I absolutely miss when I’m using it.
Laravel + Livewire is some sort of dark voodoo magic. I can write only PHP and have a functioning SPA with push updates and all sorts.
There are tests (and if the readme is to be believed a 71% coverage) they live in the top level tests/ folder.
As to the .env file you just need to rename the example one and either amend these values (with appropriate urls)
SERVER_NAME=localhost
KBIN_DOMAIN=localhost:9443
KBIN_STORAGE_URL=https://localhost:9443/media
MERCURE_URL=https://localhost:9443/.well-known/mercure
MERCURE_PUBLIC_URL=https://localhost:9443/.well-known/mercure
CADDY_MERCURE_URL=https://localhost:9443/.well-known/mercure
Or add them to a new .env.local file.
Start it all up and jobs done*
*well, you need to run the asset pipeline and add an admin user but that’s all in the Readme.
It has one. Minus an undocumented step (that’s sat fixed in a pr). Bringing it up amounts to 4 lines in a console; 1 to bring up the stack and 3 to start a JS watch for asset compilation.
I’m just looking forward to news item Reddit puts out gaslighting everyone into thinking nothing of real consequence happened.
It’s not weird. I’d appreciate it if it were me.