101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

508
active users

#tagging

0 posts0 participants0 posts today

Planned to add file name descriptions and #tags to my recent photos while taking a train ride.

Unfortunately, tab-completion of my Python-based #tagging tool doesn't work at the moment and I have no idea why. This makes my tagging session an unpleasant one.

So I created a bug report for it: github.com/novoid/filetags/iss

The only thing that worries me is that it's my own tool, that has this bug and I don't know how to fix it. 😔 🤦‍♂️

Could be related to #readline, terminal emulator, pyreadline version, ... 🤷

GitHubTab completion is not working · Issue #74 · novoid/filetagsBy novoid
I had an idea for an infographic like this for new users to #pixelfed who might be familiar with other social media platforms (!nstagram, Tw!tter) etc. I see people post all the time with zero tags for example. I was not aware of some of this as a new user myself and maybe it would be helpful to share things like this.

This is me just slapping together some bullet points in Canva. If there's already some sort of guide for pixelfed I hope we can share it more. Or is this already very obvious to everyone here? Could you make a better version of this?

#pixelfed #pixelfedhelp #newusers #newuser #howto #howtopixel #fediverse #tagging #meaningfultagging #infographic #explainer

Latest attempt at building better documentation for thi.ng/umbrella (also to make it available offline!): Having noticed that recent versions of TypeDoc support extracting & merging of doc strings from monorepos, over the past few weeks I've been updating/cleaning docstrings in hundreds of source files across all 200+ packages and started building a small tool to assemble a single/mega-page documentation (currently ~4.3MB of just HTML). The tool translates existing docstrings and references contained therein (and still used for the existing API docs) to support proper cross-package references.

I've uploaded an early preview here:
docs.thi.ng/umbrella/

Please be aware that so far this is only an early stage prototype and only contains very limited docs. I.e. there are no generics/typeparams, no details about classes/interfaces... But at least I know now HOW to add this all, as well as all the additional metadata I've already got (currently still only available via other custom tools/examples).

For example, there're links to the tag-based browser[1] and I'm also planning to add the fuzzy doc search engine/index[2] to this new documentation... The tag browser integration still needs more work in terms of correctly matching package names to tags. The underlying system is there already, just needs more work in terms of actually doing/assigning the concept mapping. Since most package names in thi.ng/umbrella are very plain/boring (for a reason), for many (most?) packages this already works pretty well:

Example: Visiting the WebGL package docs: docs.thi.ng/umbrella/#webgl and then clicking on "examples" for this package, then opens the tag browser for WebGL: demo.thi.ng/umbrella/thing-bro where you can then see all other packages and examples related to this topic...

More updates on this all soon! Excited! 🤩

(EDIT: added screenshots...)

[1] demo.thi.ng/umbrella/thing-bro
[2] demo.thi.ng/umbrella/rdom-sear

Replied in thread

@Serenus @sandwich

#contentWarning and #tagging are very different

tagged content flows by at the same level of exposure

content warning hides content from general consumption, putting up an additional barrier to engage with it

for plenty of topics: sex, violence, etc, it is an utterly valid ask

but to ask someone to content warn something that doesn't require a content warn by any coherent rationale?

this is asking the world to bend to your personal preferences on contrived entitlement

Replied in thread

@Serenus @sandwich

yes: #tagging is a completely different story than #contentWarning and i agree with you wholeheartedly

it allows people who want to be engaged in the same content as you to find you

and the inverse:

it allows others who want to avoid the content you are engaged in to avoid you

and *that* is the way it should be

i am not entirely sure there is or ever will be a better option