en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Server stats:

250
active users

#discoverability

1 post1 participant0 posts today

I like this idea for a #LettersToTheEditor #preprint server.
link.springer.com/article/10.1

"Such a preprint server would offer three major benefits…: format-free ease of swift communication, increased author visibility and accountability, and avoiding the homelessness of unpublished [letters]."

PS: I've sent letters to journals that had policies not to publish them, but without saying so anywhere. Once I sent a letter to a new journal that had never received or published one and needed time to think about it. Right now #SocialMedia takes up this slack and does a pretty good job. But posting letters as preprints would give authors more space, prevent even published letters from languishing behind #paywalls, and offer better opportunities for #PIDs, #metadata, and #discoverability.

SpringerLinkReinventing the Letter to the Editor in Science: A Dedicated Preprint Server - Publishing Research QuarterlyAlthough letters to the editor (LTEs, or Correspondence) have a wide range of communicative functions within science, they also present several drawbacks, three of which we highlight: editorial ambiguity, technological limitations and skewed perceptions about their format. An assessment of Scopus (September 16, 2023) indicated that letters account for 1.7% to 3.2% per year, relative to articles and reviews, suggesting that the LTE field is undeveloped. We argue that the creation of a new preprint server, which we name CoArXiv or LettersArXiv, would allow LTEs—with timely and valuable knowledge and insight—to be posted in much the same way as other preprints, and would be one way to overcome needed reform of LTE-publishing culture, ultimately expanding the range of science communication channels for multidisciplinary research. We consider that such a preprint server would offer three major benefits for scientific research: format-free ease of swift communication, increased author visibility and accountability, and avoiding the homelessness of unpublished LTEs.

Gisteren heb ik de stream zitten kijken over de discovery service voor fediverse accounts waar het mastodon project aan werkt.

Zodra er echt een release is, wil ik kijken of we dit specifiek voor het Nederlandstalig deel van de fediverse kunnen inrichten.

Een betere vindbaarheid van elkaar is echt nodig om de fediverse voor meer mensen toegankelijk te maken.

fosdem.org/2025/schedule/event

fosdem.orgFOSDEM 2025 - Fediscovery: Improving Search and Discovery on the Fediverse
Continued thread

Update. Also see:

* NIH Plan to Increase Findability and Transparency of Research Results Through the Use of Metadata and Persistent Identifiers
osp.od.nih.gov/wp-content/uplo

* NIH Issues New Policy to Speed Access to Agency-Funded Research Results
nih.gov/about-nih/who-we-are/n

* Introducing the New NIH Public Access Policy
osp.od.nih.gov/introducing-the

h/t #GaryPrice

you know what mastodon desperately needs? LISTS. there should be a system where you can make lists of people and then follow/block a whole list at a time.

right now there's a problem where I want to be in a bunch of cool local feeds but I don't want to make a ton of duplicate accounts. if those worked like lists instead this would be a non-issue.

Something I would love to see on the #fediverse: That people could curate lists of hashtags and people to #follow that you could browse and follow people through without having to switch instance, copy addresses and put that in your search bar back at your own instance. Surfing the fediverse is not really like surfing, it's more like going to catch fish on the sea, but the kind of fish you need to bring home before you can eat them (yeah super bad metaphor, you get the point) #discoverability

Continued thread

Several rounds of updates later over the past few days (also in part thanks to some of the feedback received — thank you!), a new version of the thi.ng browser tool is up:

demo.thi.ng/umbrella/thing-bro

New features include:

- additional per-project/example links to API docs, live demos, source code
- for each tag only the top 10 related tags are shown now to avoid (well, minimize) cognitive overload
- dozens of tags have been pruned/merged/replaced (across dozens of package.json files, an ongoing process for the near future...)
- glossary/reference link additions
- CSS updates

Since this entire tool is also entirely made with thi.ng/umbrella packages, some of these features (e.g. the related tag ranking/sorting) has been implemented & simplified via new additions to the thi.ng/transducers package (e.g. the new `sortedFrequencies()` reducer function, just released). Please see the main repo readme (section: "Latest updates") for more...

This past week I've been doing _a lot_ of work on a new "thi.ng browser" tool (and the associated metadata) to help people exploring the thi.ng universe via a tree-based user interface of tags/keywords (current selection is 750 tags with only ~375 of 500+ projects in total).

demo.thi.ng/umbrella/thing-bro

Each tag shown is a potential entry route. By unfolding nested levels of the tag tree, each branch is creating increasingly narrower tag intersections to filter the list of available packages & examples. At each level, a list of related tags will be shown. Some tags/acronyms have associated glossary entries for further reading (incl. on Wikipedia). Nested tags can be promoted as new main search term (via "open as root"), which might increase the result set again. You can use the fuzzy search input to pre-filter the initial list of tags you're interested in... or use the list of initials as a kinda book index.

All this is work in progress! There're no easy or linear ways to consolidate and update the metadata of all these projects, manually assign screenshots/thumbnails, deduplicate language/tags etc. I've already been doing dozens of passes semi-automating keyword updates, but I'm guessing I'm only 1/3rd done... But, I'm already _very_ happy about how this is turning out and hope it will be useful to others as well! For any ideas/feedback[1], please reply here or use the GH discussions...

Eventually, I want to include additional levels & information both on the topic/tagging side (e.g. start with a smaller number of use case "macro"-tags) and on the project end (i.e. to unfold projects and their resources/assets)..

New or existing users might also find the source code of this tool interesting. No docs/comments added yet, but hoping to address these over the next week!

[1] ...as always, highly appreciated!

"Why publishers are preparing to federate their sites"
digiday.com/media/why-publishe

PS: When will #AcademicPublishers start to do this? For them, it would be all gain, no loss, whether or not their works were #OpenAccess.

I might not follow a #publisher, since too many of its works would fall outside my areas of interest. But I would definitely follow #journals and #book series. I'd also follow #tags.

Digiday · Why publishers are preparing to federate their sitesBy Sara Guaglione

Did you miss the University of Alberta Library #Editorial Lunch and Learn featuring multilingual publishing with #OpenJournalSytems?

Start with this thread!

Why #MultilingualPublishing? When English is viewed as the standard for #ScholarlyPublishing, a lot of research is missed or minimalized.

Language-inclusivity improves #metadata, #indexing & #discoverability.

Consider using #OJS settings as part of an alternative publishing model 🧵 ⤵️