seen quite a few people lately spinning up lil single-user instances for themselves and talking about how it feels really freeing to be in charge of their own fedi presence; that's really nice to read :)
programmer, (former) moonkin, nasty woman, geek
@bananabull's geekier half
would give left pinkie to work for #nasa, building stuff at #prisma until then
πΊπΈβ in π³π΄β #trondheim, vestkyst bestekyst
formerly @ellotheth@mastodon.technology (c. 2017) and @gemma
#php #golang #reactjs #typescript #linux #git #devops #webdev #backend #programming #prisma #womenintech #cycling #trailRunnin #gravelcycling #uciwwt #norway #dogs #gaming #gameing #destiny2 #valheim #fedi22
seen quite a few people lately spinning up lil single-user instances for themselves and talking about how it feels really freeing to be in charge of their own fedi presence; that's really nice to read :)
Hello everyone, after a week or two down the release candidate mines, we've emerged blinking into the light carrying with us #GoToSocial v0.18.0 Scroingly Sloth!
https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.0
Please read the migration notes carefully for instructions on how to upgrade to this version. This version contains several very long migrations so you will need to be patient when upgrading, and backup your database first!!
Release highlights
instance-stats-mode setting, admins can now choose if and how their instance serves stats via the nodeinfo endpoints. Existing behavior from v0.17.0 is the default.prefers-color-scheme preference: there's now a light mode default theme to complement our trusty dark mode theme, and the theme will switch based on a visitor's prefers-color-scheme configuration. This applies to all page and profiles, with the exception of some custom themes. Works in the settings panel too!Thanks for reading! And seriously back up your database.
@schmalliso @ello a gajillion percent, and also i was like halfway into the second book before i realized it wasn't actually written as femme, i had just unconsciously understood it that way π
alexander skarsgΓ₯rd as #murderbot will be
From @updates: we just added support for the fediverse:creator tag on @write_as! https://write.as/updates/now-your-write-as-posts-can-be-associated-with-your-profile-elsewhere-on-the
This is also coming to #WriteFreely: https://writefreely.org/pull/1253
Random Nigerian fact for you:
During the civil war, Nigeria used starvation as a weapon of war. Over a million Biafrans died, mostly kids.
Eventually, the rest of the world came through with food donations. Norway, for instance, sent a dried cod product that they barely ate called stockfish.
That was 55 years ago. Now stockfish is an indispensable part of Nigerian cuisine. We spend tens of millions of dollars each year importing it from Norway.
I guess generosity pays.
I am still looking for work.
I am open to contracting or full-time remote positions. I am in the US, ET.
Tech skills with lots of FOSS stuff: Python, PHP, JS. 25 years building the web.
I also can consult on Team building and Communications, and find out how to really help your developers be productive and happy.
Hit me up!
#WikiTok: a #TikTok-style interface for exploring random #Wikipedia articles
Hi everyone!
We've just pushed a very important security bugfix release for #GoToSocial v0.17.3 and below:
https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.17.4
If you are running on GoToSocial v0.17.3 or below, you should update to v0.17.4 as soon as possible. It's a very small update from v0.17.3 -> v0.17.4 as it contains only some code logic changes, and no database migrations.
In short, when a dereferencing bug is triggered under a specific set of circumstances it can cause loss of account data on affected instances. It's a rare thing to be triggered, but when it does happen it really, really stinks, and necessitates restoring from backup or manually editing the database to get things working again. (It's not possible to access or tamper with data by triggering the bug, only destroy it.)
We'll release a proper CVE for this in a couple of days when admins and packagers have had a chance to update.
Please note that folks who are already on v0.18.0-rc1 or latest snapshots are unaffected and do not need to do anything, as the bug occurs specifically in v0.17.3 and below. This means if you prefer to update straight from v0.17.3 to v0.18.0-rc1 then that's also an option; you can follow the release notes for v0.18.0-rc1 in this case.
So! If you know folks on GtS v0.17.3 or below, please let them know that they should take action! Link them to this post if you want! And please boost for visibility :)
Thank you everyone! <3 Computers!
@ShmosKnows i use Outline for family document collaboration, it's nice
#Forgejo 10.0.1 and 7.0.13 were just released! They are security releases.
We strongly recommend that all installations are upgraded to the latest version as soon as possible.
Read more in the companion blog post https://forgejo.org/2025-02-release-v10-0-1/
Download it at https://forgejo.org/releases/. If you experience any issues with this release, please report to https://codeberg.org/forgejo/forgejo/issues.
Instance idea: snailmail.zone, all posts are automatically scheduled to post in 7-10 days.
@pamela unordered and not actually the best:
that last one's good for at least 15 watts on the trainer :flan_strong:β
The woods
Teleport to the woods
Its woods time for you
@atomicpoet i was on xbox by then, so i'm more of a halo person heh