Hello Mastodon! We are a collective of #students and staff from #Amsterdam University College who care about #OpenStandards, #FreeSoftware, and #OpenData.

Every week, we get together to explore, study and organize our way out of the corporate lock-ins that we face at our #university and beyond.

Next to our website, this account will be our main channel to communicate with the world.

We hope that we can connect with others that share our ambitions to push for a free and open digital world.

@OpenTech_AUC Great initiative. Very happy to see it :)

💕

@OpenTech_AUC is there a link to the website without the QR code?

Sure there is, here it is: https://opentech-auc.org/posts/

0. Posts

OpenTech AUC official website

@koen

Thank you for this service. We didn't manage to fit the website within the max word count of our instance 😁

(It is in the url overview of our account, just like our Codeberg page).

@OpenTech_AUC one of the nice features of running your own instance is that you can increase the number of allowed characters to something a bit more than the default.

That way you can fit those URL's (and your argumentation that has nicely formed sentences instead of abbreviated ones) in your toots and your reactions.

I strongly recommend doing that. #mastoadmin

@koen

We are quite happy with the Mastodon instance that @SURF provides to all students and employees of higher education institutions in the Netherlands.

But yes @SLURF , it remains an interesting question how/ to what extent the users/ community of our instance can be part admin choices (such as max word count, search functionality, federation and others)!

@OpenTech_AUC @koen @SURF Requests are always welcome! Indeed the advantages of a community instance is both that we can change the settings based on community requests and at the same time try to find a single set that "suits" the broad community and provides the efficiency of a shared platform that's already there and managed.

@SLURF @koen @SURF

Not sure how we missed (the rest of) this interaction. Apologies!

@SLURF At this point that approach (individuals making requests, you evaluating/implementing) makes sense, but maybe, as/if the community grows, it might be good (and fun?) to have some form of *communal* community involvement? At some point?

@OpenTech_AUC @koen @SURF Definitely! SURF as a member-owned cooperative is very accustomed to listening and working with the users of our services. For Mastodon we do not yet see an immediate need to make a special group besides the existing structures of SURF, as it seems that the service mostly "just works" and we're not getting many requests for changes just yet. But we're definitely open to it if the community thinks we're not moving in the right direction.