and thats ok. some great work has been done making the impractical practical. the article was a good think piece. it did its job.

it be there! ;-)

awesome job!

peachy keen, friend. peachy keen.

as a followup to how useful your visualization is, I have started spreading comments across a wider selection of instance communities.

this is something I have considered before, but your visulazation made the possible utility and usefulness of doing so much more “real”.

this is really, really interesting. thank you for this.

instance reach and relationships are pretty wild and I can see this helping people to mix up their communities between instances.

the tight groupings of some instance communities might be source of pride or distress, depending.

would be nice to select a community and query its n closest overlap neighbors or all neighbors within a certain distance.

very cool project.

and I realised I was seeing lemmy literally come alive!

thats a rather soul stirring realization put to words. :-)

but every API change brings it closer to perfection! cant stop, wont stop!

the API change high is such a rough addiction to break.

no kidding. this particular FWP was… unpleasant.

oh, great! crafted image files for remote code execution? my paranoia knows no bounds.

its always been about how you algo your rithms

interesting. as mentioned before, this issue completely disappeared for me around about v0.0.37 or 38.

iirc, i do seem to remember that the issue involved stale overlay popup screens when jerboa didnt get a reply from the server in time. but, I cant seem to reproduce the issue at all anymore, so…?

the v0.0.40 f-droid build of jerboa is complete and just waiting to get into the distribution repo. would love to hear if an update improves anything.

this has occasionally happened for me on older versions of jerboa. I am currently on the v0.0.39 f-droid build and this issue has completely vanished.

also, my ‘home’ instance is running mainline lemmy v0.18.2, so that may make a difference under certain circumstances when using particular versions of jerboa and your home instance experiences congestion.

edit: your home instance (sh.itjust.works) seems to be on lemmy v0.18.2 - so, barring any weirdness on your lemmy server, its likely just your version of jerboa.

its been built and should be in the distribution repo pretty soon.

if you want to track f-droid builds of your fav. libre project on your phone then the F-Droid Build Status app will help you out.

quick update on this. have been playing with the jerboa v0.0.36 f-droid build and it seems to handle network errors and junk data in a much more sane way - still not ideal, but it now throws visual error notifications instead of an outright crash.

looks like the jerboa robustness issue is slowly being addressed. lets see what we get with v0.0.37.

@[email protected], @[email protected], @[email protected], @[email protected]

I can actually see some merit to a lemmy API accessible reddit corpus. it would be interesting to reference old reddit info in a lemmy compatible way with zero reference to reddit itself.

doing so for the entire corpus properly (link fixups, etc) would be… challenging, but doable.

I am on lemmy.ml which is currently at v0.18.0 so it should be cool. wanted to crowd source some feedback before I open a github issue - dont want to waste dev time on non-reproducible ghosts.

indeed, an excellent article.

welcome! we are damn happy to have you here.

that first time committer list is fire!

Tumblr and Flickr are said to be joining the Fediverse.

yay! its AOL meets the internet v2.0

/s