justira

Pokopia dropped, aaaaaaaaaaaaaaaaah! I've wanted a Pokémon farming sim since like... 2012? So I was VERY hype for Pokopia! So far it's not actually that. It's more like Dragon Quest Builders 2, in that your job is to smash blocks, build houses, and make friends, but considering how normal I was about DQB2, I'm okay with that.

I'm still in the first section of the game, Withered Wastes, so spoilers through that behind the cut.

( Read more... )

Listen, I have been noodling on and off with a Pokémon/Harvest Moon fusion where you can ask your Pokémon to help you water crops and cut down trees since I was in uni and messing with RPG Maker, having Pokopia might actually be the dream.

Current Mood: bouncy

lassarina

( You're about to view content that the journal owner has advised should be viewed with discretion. )

lassarina

( You're about to view content that the journal owner has advised should be viewed with discretion. )

spindizzy

Because of course they are. Due to Brilliant Financial Decisions that I can't get into without doxxing myself, work are making some changes. Some of them I can understand; they're standardising opening hours and want shift patterns to line up with each other, cool, that makes sense. Some of them though... Yeesh. Their ideal situation that they're working towards includes but is not limited to:

No full-time contracts, and a hard limit of 25 hours a week max. (Lunch breaks are inconvenient, and if we only work a five hour shift we don't get a break.) Also, no one will need to work extra hours because we'll be fully staffed – ignore every other time we've said that, this time we mean it!

No home libraries; everyone is part of a pool and assigned two or three libraries per week to work at.

No overlap between shifts, so no proper handover between shifts (because why would we need that?).

"We heard your complaints that there's no job mobility that isn't becoming a manager, so we created more manager positions! ♥"

Two fewer libraries in the network – one of them is closing entirely, and one is full of valuable and delicate material so we're going to leave it open and completely unstaffed.

And when people raised questions and objections, they were told "Well, you can always leave."

... Aight, bet.

Now I'm waiting to hear back from one library job, and I've got three other applications to get in by close of play on Monday. ¯\_(ツ)_/¯

For bonus points: we were all assigned a mandatory meeting with one of our great-grandbosses to discuss the changes and ask any questions. Me being me, I sent him an email before the meeting with all of my questions so that we had an agenda and he could prepare answers! (ʘ‿ʘ🌺) He told me a lot of things, most of which did not answer my questions, and I sent him a summary of his answers and the questions I would still like answered. (ʘ‿ʘ🌺) I think each email was two pages each, front and back, and I need you all to understand the peak comedy of his reply: "Had a quick read, that looks right, hope it helped you."

I do literally hours of writing relevant and appropriate questions, checking my recording, summarising your useless responses, checking FAQs, and your response is "Hope it helped you."

(ʘ‿ʘ)ﾉ🌺

Met with my line manager on Thursday and accidentally cried at her, because I sent her copies of my messages and her response was "I can tell you really care about this job and your colleagues." Turns out I wanted someone to acknowledge that? I'm not being awkward for the sake of it, I'm being awkward because I want to keep doing my job! She also suggested that I send my questions to Other Great-Grandboss to get actual answers, but only after I revise out some of my... Expressions of frustration... Because Other Great-Grandboss will actually read them, and it won't help me get my answers. But god, I just – I'm irrationally convinced that somehow I can find the magic words to convince the bosses to fucking listen to us and understand why people are upset. I can't, but what if I could.

... Anyway, that's what's going on with me right now. I'm going to cross stitch Pokémon and watch other people play the new Resident Evil game because hahahahaha NO I AM NOT PLAYING THE GAME WHERE SOMEONE STALKS ME IN THE DARK. NO THANK YOU.

Current Mood: annoyed

lassarina

( You're about to view content that the journal owner has advised should be viewed with discretion. )

mark posting in

dw_dev

We've seen some questions lately about AI and how it relates to Dreamwidth, especially around scraping and training. Rather than answer piecemeal, I wanted to talk through how denise and I are thinking about this and try to be explicit about some things.

Dreamwidth is a user-supported service. We don't build the service around monetizing user data, and that informs how we approach AI just like it informs everything else we do.

Your content and AI training

Dreamwidth does not and will not sell, license, or otherwise provide user content for AI training. We have not and will not enter into data-access agreements for AI training purposes.

We will continue taking reasonable technical steps to discourage large-scale automated scraping, including known AI crawlers, where it is practical to do so. No public website can prevent scraping with absolute certainty, but we will keep doing what we reasonably can on our side.

AI features on Dreamwidth

Dreamwidth will not introduce AI features (and we have no current intention of doing so) that use or process user content without a public discussion with the community first.

We're only phrasing it like this because we can't predict the future and who knows what will be possible and available in five or ten years, but right now there's nothing we can see wanting to add.

If that ever changed, the conversation would happen openly before any decisions were made.

Site admin uses of AI

Keeping Dreamwidth usable means dealing with things like spam and abuse, and that sometimes requires automated admin tools to be more efficient or effective.

We are not currently using AI-driven systems for moderation or similar decisions.

If we ever decide that an AI-based tool would help address a site admin problem like spam, we will explain what we are doing and how it works (and ask for feedback!) before putting it into use. Any such tools would exist only to make it easier and more efficient for us to do the work of running the site.

AI and code contributions

Dreamwidth is an open-source project, and contributors use a variety of tools and workflows.

Contributors may choose whether or not to use AI-assisted tools when writing or reviewing code. Dreamwidth will not require contributors to use AI tools, and we will not reject contributions solely because AI-assisted tools were used.

For developers: if you use any AI-assisted development tools for generating a pull request or code contribution, we expect you to thoroughly and carefully review the output of those tools before including them in a pull request. We would ask the community not to submit pull requests from automated agents with no human intervention in the submission process.

I think it's important and I want to be able to review, understand, and maintain any contributions effectively, and that means humans are involved and making sure we're writing code for humans to work with, even if AI was involved.

Important note: this applies to code only. We expect any submitted images or artwork (such as for styles, mood themes, or anything else) to be the work of a human artist.

And to be very explicit, any AI-assisted development does not involve access to Dreamwidth posts or personal content.

In short summary

Dreamwidth does not and will not provide user content for AI training
Dreamwidth have not and will not enter data-sharing agreements for AI training and we will do what we can to prevent/discourage automated scraping by AI companies
Dreamwidth will not introduce AI features without a public discussion first
Any site admin use of AI tools will be explained openly and part of a public conversation
Contributors can choose their own development tools for code, but we do not accept images or artwork generated by AI

Oh, and we'll probably mention this (or a subset of this that isn't code related) in an upcoming dw_news post, but will defer to denise on that!

silveradept posting in

dw_dev

Oh, hi, everybody! It's been a little bit since we did a code tour, hasn't it? But never fear, we're here to walk you through the changes that have happened since the last time we took a tour through the code changes in Dreamwidth.

Let's dive in, shall we?

( Your code tour, with some attempts at arrangement by topic. )

There we go! Another year's worth of code commits, issues resolved, and attempts to make Dreamwidth a greater and cooler place to be. And to have it continue working into the future.

(We should do these more often, but volunteers and, well…*gestures broadly around*. So it may be a while before someone has the spoons to do this again, but we're always trying to be more consistent about it.)

Here are the totals for this code tour:

104 total issues resolved.
Contributors in this code tour: