Skip to main content


My #Friendica instance just produced an error that a PHP process ran out of its 512MB allocation. What is it doing?
in reply to Daniel Lowe

I was wondering if it was a plugin. Is that 1k posts per connected bluesky account?


(Sorry, there doesn't seem to be a way to notify just the local instance)

The server is already running out of disk space! I'm swapping out the object storage from DB to an object store, which should fix the problem and probably be snappier. The site may run a bit slow during the migration but it seems to be a transparent process.

in reply to Daniel Lowe

Most of it is images from the people I follow, I imagine. But this isn't a dedicated server, either. I run a bunch of stuff on it.
in reply to Daniel Lowe

Unlike the mostly-public Mastodon, this doesn't have an option to serve directly from S3. It makes sense. So this will be a purely internal change.


repebble.com/

This is super exciting for me. I'm still wearing a Pebble Time Steel with the Rebble firmware and this can only do good things for it.

in reply to Daniel Lowe

If you get a Pebble Time Round, they're pretty attractive and are still alive through the Rebble project (rebble.io/). Pebble Time Steels are easier to come by, they're slim too, but not as nice.
in reply to Daniel Lowe

OK, the first thing that's frustrating is that smart watch product listings don't seem to include the diameter of the watch face in the same units that a normal watch would. I know the maximum face diameter that works on my wrist in mm, but how does a screen size of 1.1 compare?

Daniel Lowe reshared this.


Attention Troubleshooters:

If you ever feel stressed out, overwhelmed, and helpless, just take a breath and find one thing you can do to make another Citizen's day just a little bit better.

But don't take too long, or you will be terminated for neglecting your assigned mission.

#ttrpg #mentalhealth

reshared this

in reply to Friend Computer

Friend Computer, you are so right. Just yesterday I disconnected the spycams and mics in a citizen's living unit (yes, including the bathroom) and they were so grateful they gave me 4 BTC!
in reply to Killa Koala

@dshan
How wonderful.
4BTC is almost exactly the fine for tampering with Computer property.

Thank you for confessing your crime. Your loyalty has been noted.


Daniel Lowe reshared this.


facebook is blocking mentions of disrowatch. a new wave of linux enthusiasts are on their way to the fedi as we speak

reshared this



The generations after Gen X obviously should have been Gen XI, Gen XII, Gen XIII, Gen XIV, and so on. We could also have retconned previous generations as Gen IX and Gen VIII.

Daniel Lowe reshared this.


Today I went to a freecycling party hosted by a friend! We all brought clothes/books/art supplies/etc we didn't want, perused everyone else's stuff and took what we wanted, and then divided any remaining items into categories to donate (e.g. one person takes all the art supplies to our local used craft supply store, another person takes all the clothes to a local thrift store, etc).

It was very fun! And I never would have thought of throwing a party like that, so I'm posting about it here to pass along the idea to others :)

#freecycling #buyNothing

reshared this


Daniel Lowe reshared this.


As someone who is totally blind, the Fediverse is the only place where I have ever been able to follow people such as photographers, artists, or even those who post pictures of their cats or the food they ate. The reason is that most of them use alt text. They take the time to describe the images that my screen reader can't recognise. Some write the descriptions themselves, and others use tools such as altbot. Some worry that their descriptions aren't good enough, especially when they are new at this. Let me assure you, not only are they good enough, they are extremely appreciated! If the rest of the world thought as you did, it would be a much better place. Don't hesitate to ask if you're unsure of something, but never think that we don't notice your effort.

#appreciation #accessibility #altbot #alttext #blind #blindness #fediverse #gratitude #images #inclusivity #peoplewhocare #pictures #technology

reshared this

in reply to Georgiana Brummell

@Georgiana Brummell I'd say not everyone would consider almost 1,000 characters of image description in a 1,500-character alt-text accessible. And even fewer people would consider a long image description in the post itself that's tens of thousands of characters long accessible if your screen reader spends an hour or several rambling it down.

My most extreme case is a post with only one image. That one image is described twice like all my halfway recent original images. The short description in the alt-text is a bit over 1,400 characters long which barely leaves any room for the note that there is also a long description in the post itself. That long description is over 60,000 characters long. I'm not kidding. It took me two full days from getting up to going to bed to research for it and write it.

Now, there are a few dozen bits and pieces of text all over the image. At the resolution at which I've posted the image, two of them are ever so barely legible for sighted people. They're on a large logo on a building. Four more, two of them on that logo, too, two more on a sign on an easel, are illegible, but still visible. At least more on signs inside the building are visible, but they can't easily be identified as text. All the others are so tiny that they're invisible. It takes the long image description to even know where they are, for example, on the control panels of teleporters.

And yet, they are all within the borders of the image. And I can transcribe them. I can't read them in the image, but I can go to the place shown in the image and take closer looks.

Unfortunately, the rule or guideline that any and all text in an image must be transcribed verbatim does not take into consideration text that can't be read in the image, but that can be sourced and thus transcribed by whoever posts the image. No confirmation, no exception. And so I have to assume that I have to transcribe illegible text as well. And so I do transcribe them all.

But there's no way for me to put all these text transcripts into the alt-text, not if I want to keep Mastodon, Misskey and their forks from chopping it off at the 1,500-character mark. I'd also have to explain where all these pieces of text are, after all. And so the text transcripts are only available in the 60,000-character monster of a long image description.

It isn't really accessible to expect blind users to have their screen readers ramble and ramble and ramble for hours, just to get information that should actually belong into the alt-text which, in turn, shouldn't be longer than 200 characters.

On the other hand, it doesn't really seem accessible to me if I expect people to ask me to describe things in the image for them. It rather feels sloppy, if not out-right ableist to not describe everything that someone could possibly want to know right away.

The problem with my images is that they're renderings from very obscure 3-D virtual worlds. This means that nobody knows what anything in these images looks like unless they can see these images. This, in turn, means that I cannot expect anyone to know what something in my images looks like anyway. They don't.

At the same time, I can't expect everyone to not care about my images. In fact, I expect the very topic of 3-D virtual worlds that actually exist to make people curious. At this point, it doesn't matter what's important in my images within the context of the post. Sighted people will go explore the new and unknown world by taking closer looks at all the big and small details in the image.

But blind or visually-impaired people may be just as curious. They may want the same chance to explore this new world by experiencing what's in that one image. Denying them the same chances as sighted people is ableist. But giving them this chance requires an absolutely titanic image description.

Sure, I describe lots of details which a sighted person can't possibly recognise when looking at the image, especially not at the resolution of the image as I've posted it. But I simply can't keep telling blind or visually-impaired people that certain things in the image can't be recognised due to the image resolution. It feels lazy, like weaseling out. I mean, I can see all these details. Not in the image, but where the image was made, simply by walking closer to them or moving the camera closer to them.

If there are two dark objects inside a building that may or may not be plants, but that can't be identified as plants by looking at the image, why shouldn't I describe them as follows: "On the sides of the teleport panel, there are two identical açaí palms in square terracotta pots with wide rims. Like the other potted plants, these mostly dark green plants with long pointy leaves are kept at an indoor-compatible size, namely about three and a half metres or eleven and a half feet tall. Also, like the other potted plants, they are made of only four flat surfaces with partially transparent pictures of the plant on them, arranged in angles of 45 degrees to one another."

If there's room for improvement in my image descriptions, I improve my future image descriptions and declare my past image descriptions outdated. In fact, the 60,000-character-long description is outdated because it's bad style to describe dimension using measures. Instead, dimensions should be described by comparing them with something everyone is familiar with like body parts.

Right now, by the way, I'm upping my game at describing avatars, using rules and guidelines for describing people which I've discovered over the last few months. The last time I've described an avatar, I've done so in about 7,000 characters, but according to my new discoveries, I may have missed something.

However, I can't go into so much detail while still making my image descriptions short enough that a screen reader can read through them in under a minute.

CC: @Nat Oleander

#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

in reply to Jupiter Rowland

@Jupiter Rowland @Nat Oleander Oh my goodness! Now I see what you mean. Even as a lover of nineteenth-century writing and proper English, that's long, especially for alt text!

Daniel Lowe reshared this.


Public Social Media

The choice is clear.

Mastodon
Owned by: No one and everyone
Structure: Public non-profit
Number of distributed nodes: Thousands
Post length: 500 characters and more
Can edit? Yes

Bluesky
Owned by: Venture capitalists
Structure: Corporate for profit
Number of "distributed" nodes: One
Post length: 300 characters
Can edit? No

#PublicSocialMedia

This entry was edited (4 days ago)

reshared this


Daniel Lowe reshared this.


Today's #DynDNSHistory brought to you by @jtk , who asks about early or interesting abuse-related issues.

There's lots here so this one will be a thread...

The first one that jumps to mind is credit card fraud. This isn't really surprising/interesting in the later days, but what surprised me was that people used stolen credit cards even when we were just taking donations.

Like, really? You're going to abuse some kids who are just trying to run a free service? Not cool.

1/?

Daniel Lowe reshared this.

in reply to Tim W (admin (and human))

Once we started doing paid services, the credit card fraud really picked up - in some cases it just seemed like they were using us to check stolen cards before using them for something bigger, other times they were really trying to get services.

I never quite understood the logic of the second one - you have to know it's not gonna last for long when you're using someone else's card. But maybe people don't notice and report the fraud?

4/?

in reply to Tim W (admin (and human))

This one led to some of the most interesting things about abuse - getting surprising new domain names! When someone bought a domain with a stolen credit card, there was usually no way for us to cancel the registration (eventually we could if we caught it fast enough, but by the time there was a chargeback it'd for sure be too late).

So, we figured - we paid for these, I guess they're ours now! I don't remember any specifics, but there was definitely some weird ones in there.

5/?

in reply to Tim W (admin (and human))

I don't remember if we ever turned any of them into actual customer domains for our free services - I don't THINK any of them happened to be good for that purpose.

Credit card fraud was a huge pain back then (not that it isn't now) - there wasn't nearly the range of intelligent analysis and risk assessment that's out there today. And as I recall we got chargebacks via fax (or had to respond via fax, maybe both). The bad old days...

6/?

in reply to Tim W (admin (and human))

Next time on #DynDNSHistory I'll talk about credit card processing - it was so much more complicated than just getting a Stripe account those days.

The hoops and shenanigans we had to go through as a small start-up doing online card processing in those early days were wild.

7/7

in reply to Tim W (admin (and human))

Oh, I'd love to hear more about credit card processing. I'm working with a start up Member owned Co-Op and we're trying to find an economical way of accepting SNAP benefits. It's literally the only reason we have our Heartland account, and we lose money every month in fees.
in reply to Lisa Gets Politik

@lisagetspolitik I know less about anything specialty today, bit I know (or at least used to know) a lot about the landscape of 20 years ago! 😀
in reply to Tim W (admin (and human))

we’re they using you as a registrar / reseller?

I never knew that DynDNS was in that line of business.

in reply to DrScriptt

@drscriptt yeah we started off as an OpenSRS reseller and then moved on to being an accredited registrar. Domain registration was generally a combination with our DNS for your own domain services.


One cool thing I have to call out for #Friendica is that there's a section for "Quiet Sharers" that highlight posts from accounts that don't post very often.
in reply to Daniel Lowe

I think your "latest" only applies from the time you started following, but if you go to my profile, you can see everything you have access to. Some of this is probably bound by federation etiquette - if you were to follow someone on another server, the system wouldn't download everything they'd ever posted.

The bullseye icon also shows all the conversations on the server you have access to.



I've been trying to settle in a bit on Friendica. Grouping my relationships into "Circles," reminiscent of G+. Unlike Mastodon, there doesn't seem to be any hashtag lists, which I miss. The interface would accommodate them though, I think.

Losing nearly all my followers is kind of tough. There's no Mastodon -> Friendica migration. On the other hand, maybe it's like a mark-and-sweep gc. The followers who actually wanted to follow me still are.

I'm still intending this to be a public instance, but I want to do some theming and policy work before I start putting it on directories.

in reply to Daniel Lowe

Update: There is a section for "saved searches" that support hashtags.


I created this Friendica instance to be my new home now that octodon.social is shutting down in a bit. I was hoping some people would follow me from Facebook but you can guess how that's going.

I think I actually prefer the Friendica interface for my Fedi content. That was unexpected.

in reply to Daniel Lowe

Huh, Octodon is shutting down? Weird, but I guess I haven't heard anything from them in quite a while.

Guess that's my backup account out, then. Not that I've really used that one since setting this one up.



Hello World!


This is my first public post on the new site! Here's hoping for a new Internet future.