HamSwagwich

joined 2 years ago
[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (8 children)

Thank you for the reply! I'm still not getting any federated content either direction with my node from KBin.social

I'm running a KBin node for the record, not Lemmy

Still working on it?

[–] [email protected] 2 points 2 years ago (1 children)

What do you mean "quickly?"

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago)

@jbenguira

I just tried this, but it doesn't seem like it's really ready for anything but a basic test environment.

When your system creates the service, it does so with the default elestio domain and there is no way to change it from within KBin, therefore your are stuck with a huge security hole and a nonsense domain name that's impossible for people to remember.

While you can indeed use your own domain name to resolve it, it doesn't appear that the domain is editable once KBin is setup (which is done automatically, and understandably on the federation side, you can't have the domain name changing)... so when you set up a KBin on Elestio, you are forever suck with "kbin-????-u5400.vm.elestio.app" as your server name in the Fediverse, which sucks and is really a non-starter.

I don't want to be @[email protected]

This appears to have the added effect of making it impossible to use Cloudflare as your proxy, since you get a bunch of 301 redirects bouncing between your resolved domain and the elestio domain, since KBin thinks it's name is the elastio domain and rediredts you, then our browser thinks it's going to the resolved domain and redirects you. Boing boing boing

[–] [email protected] 2 points 2 years ago

That's correct and that's the problem. If a given community server goes down, that community basically just becomes an archive. It really needs to be able to continue without the host instance, similar to how a mesh works. Each remaining server routes around the dead node.

There is also the problem of search engine indexing... If a given server goes down, that information is lost to the search engine, even though it's still on other nodes.

Which also leads to duplicate content problem for search engines, as ECU m each node of a given community contains the same information for a given post, making it crappy to index and search.

[–] [email protected] 3 points 2 years ago (2 children)

Indeed, and when you kiss someone you are making one big hole connected by two assholes.

[–] [email protected] 4 points 2 years ago

The RCS issue hits the nail on the head I think. It's really the biggest stumbling block for everyone at this point.

[–] [email protected] 1 points 2 years ago

Same. I don't see anything but one star reviews.

2.2M downloads and only 3.3 stars. You gotta be really shitty to have that low of a rating at that volume.

[–] [email protected] 1 points 2 years ago (1 children)

Dang I guess you can now. It wasn't working when I first tried it. Awesome

[–] [email protected] 4 points 2 years ago (3 children)

I like it, but the fact that you can't pinch to zoom an image almost kills it for me.

[–] [email protected] 1 points 2 years ago (1 children)

Crashing for me. Switched to Connect. Works well... except you can't pinch zoom images, which is a huge problem...

[–] [email protected] 4 points 2 years ago

Ive decided not to block him so I can follow him around annoying him and downvoting everything he says

Perfect example of why voting should be public!

Blocking him is the right answer, it's the right thing to do and solves the problem of him presenting posts you don't want to see.

view more: ‹ prev next ›