you know, I think I'm just going to delete my fucking LinkedIn account.

[lina@neuromatch.social]

@aud
oh nice, good luck!!

[aud@fire.asta.lgbt]

@[email protected] @[email protected] But yeah, definitely need "prior art"/work shown for this to be effective.

You have to prove that you are worthy of trust and can do the work. Or, at least, that's the kind of thing I would need to feel comfortable suggesting people throw money at work I'm doing.

[aud@fire.asta.lgbt]

@[email protected] thanks! I'm trying to get in by the first deadline, which is Friday. I have a lot written but admittedly it's sort of... trauma-revisiting to be writing it lmao. So it's extra good practice! Just not very exciting to work on to perfection...

[hipsterelectron@circumstances.run]

@aud @lina cc @ireneista who i'm paraphrasing

[aud@fire.asta.lgbt]

@[email protected] @[email protected] @[email protected] I feel like if I could put together a working bare bones implementation of a federated, community-run search engine (which I am actively working on), in theory I could pitch for it in some way, even if it's just for people with disposable time to start working on it.

I think it's really important that people, not corporations, control the access to information. I really long for the expertise of say, librarians, for example, to be able to help contribute to maintaining knowledge (and access to it).

I also thought that if I could get that together, it would in theory be workable for smaller projects (internal knowledge bases, etc), as well, and modest support contracts could be eked out to help maintain development while it gets rolling.

[hipsterelectron@circumstances.run]

@aud @lina @ireneista i'm very interested in distributed text search i will keep an eye on your work

[aud@fire.asta.lgbt]

@[email protected] @[email protected] @[email protected] thanks! It's currently overlapping with the other work I'm doing, but part of the reason I'm designing it the way I am is so that I can split it off and use the work there to start using AP/ActivityStreams to create a federated search engine. I think it would work. And would be easy for people to spin up and help curate (and be auditable).

[aud@fire.asta.lgbt]

@[email protected] @[email protected] @[email protected] I've only got some basic concepts for search itself from @[email protected] who was kind enough to give me a little guidance regarding critical terms and concepts to look up and research in the search space.

[aud@fire.asta.lgbt]

@[email protected] @[email protected] @[email protected] @[email protected] I have a mental model forming about how distributed search could work (I mean, all search is distributed to some extent; it's hardly like google runs on one fiddly ass ancient server, compute wise. And the backend as well, I'm sure, although I couldn't tell you whether they use a partitioning scheme or what) without causing intense load across the network for every query, for example, as well as updating/curation/auditing. Buuuut I haven't written it down yet.

But I think after this writing is done I maybe will, if nothing else so that someone who might have the time and desire to give feedback can critique stuff.

[ireneista@adhd.irenes.space]

@aud @trochee @lina @hipsterelectron we're always super happy to review people's design docs

[aud@fire.asta.lgbt]

@[email protected] @[email protected] @[email protected] @[email protected] oh! I would really appreciate that. I'm sure it'll just be a lot of high level stuff to start with; I expect to have a better idea of what would need to be in place both as I finish work on the ActivityStreams/AP stuff and research more search things, but.