David Eagle

16 Followers
11 Following
16 Posts
hot dads are on line
there's already porn on here
@ruth hi I'm late but this is my jam when it comes to calming down: http://www.metmuseum.org/toah/hd/angk/hd_angk.htm

I think the major oversight Mastadon needs to correct is overlapping usernames. Whether federated or not, usernames should always be unique.

You can still be decentralized and not require a main database if you just force a degree of federation for the purposes of username sharing. Resolve conflicts by Creation timestamp.

The worst that can happen in this scenario is that a user creates an account and, a few minutes or hours later when federation catches up, they get prompted and informed that they must select a new username.

That seems...fine?

@ruth And I just saw her Q on the Federated TL too, not like, a Mutuals thing.

Small networks are wild. How do we get on Library Sciences / Big Data mastodon, because

@cm_harlow Depending on your organization and your comfort level it may be appropriate, after enough repetitions, to say "I can't help you until you've gotten the latest build. Please let me know you've done that before sending a question" - in some orgs this may be unacceptable, culturally.
@cm_harlow Also, can you solve a people/process problem with Technology? can you make your script check its version against Git and fail with an obvious error if it's outdated?

@cm_harlow Two things:

1. You may need to improve the way you're communicating that fixes are in place. They can't be expected to just _know_ you've published a new version.

2. If you're doing 1., it's just a matter of repetition. Every time they say "it's broken!" say "make sure you have the latest version. Go to Github."

I love this article about how Day 1 of a platform is not as polished as day 3,650.

Too, it misses the point. if the infosec and technology communities adopt an open source, decentralized platform, what will stops its growth is not a lack of polish (that's easy to fix) but a lack of steerage.

We'll see.