@foone you might be able to create a userscript for the fedi frontend that you use which grabs the PNG, dumps it into an html canvas, and then exports it as a jpeg, then replaces the file in the file input element with the jpeg. Like a greasemonkey script.
I did this pattern in my own app once, looking back at the code https://git.sequentialread.com/forest/graffiti-app/src/branch/main/static/app.js#1454
I think I ended up nixing the client side conversion to jpeg because it didn't work properly in every browser. Image rotation issues on iOS probably related to apples proprietary photo format
@thomasareed and some note: This is the Fediverse and CW is some kind of Mastodon hack which use the title of ActivityPub protocol.
So people participating on systems like Hubzilla, Friendica and others have no CW functionality and setting a CW is rather useless for them (and these people will never post with Mastodon CW warning)
Oops i forgot to include this link to thomas reed post https://infosec.exchange/@thomasareed/109376747868155703
IMO, pressure on #FediCulture to push CW usage closer to the "NSFW" mainstream cultural standard is not necessarily a bad thing. I acknowledge this is probably a classic straight white guy take but i think CW is weird! I honestly have a hard time believing that the CW feature / culture is as good at preventing harm as its hard-core adherents claim.
The question of what should be CW'd, what images should be fogged until click, etc, its subjective, culturally relative, and I feel like the current status quo might be a #Whiteness that has made black folks feel uncomfortable / unwelcome here.
Some of this is based on reading @shengokai takes on Mastodon and it's affordances, some of it from other posts I've seen around, I am curious what other ppl around me think.
What are some concrete examples of things that you would change about mastodon the software (or any general fedi client / server implementation) in order to achieve this ?
Therin lies the rub:
AFAIK there is no standard solution for this right now. So I was gonna just try to make one myself 😅 Greenhouse was just the beginning of that
The biggest part of it is how to handle replication and fail-over without requiring apps to be reconfigured. VM systems can do that pretty well as I understand it, I was thinking about trying to make my own system that is more oriented around Linux containers. I made a diagram about it:
https://picopublish.sequentialread.com/files/one-size-fits-all-replication-failover.drawio.png
@fack Yeah, true, I do think it's not gonna help much unless you have tons of apps tho.
But as a way to learn how to use kubernetes it would be great!! I just only have eyes for a multi-locality cluster these days because it would theoretically make the homebrew apps exponentially more reliable. I'm pretty sure Kubernetes cant help with that
@fack Well I just asked on the Free Geek discord today and they said they do sometimes have those thin clients there.
But I expect ebay would still be worth it. Free Geeks said the most of the thin clients even support SATA, just only in the SOM form factor. So no HDDs, you have to buy an SSD and then take the tin cover off of it for it to fit. Like this:
@fack Ah I see what you mean, so more about splitting multiple apps across multiple devices within the same locality (all under one roof)
I was about to go off on my "Kubernetes clusters can't span multiple localities" rant again 😛
That sounds intriguing, are you set on Kubernetes? Do you want to just do it for fun within your own home, or are you wanting to try to actually use the cluster capability for replication+failover in the context of homebrew servers?
I just published a new blog post about hardware choices for home-brew servers:
*[Shut] Up the Punx!!!*
Bomb the Music Industry
Mastodon 4 adds a new endpoint, /api/v1/instance/domain_blocks
This endpoint contains your instance's block list in an easily machine-readable format. As far as I know, the only tool that currently uses this endpoint is the kiwifarms one.
The endpoint does not require any form of authentication, so it's very easy to scrape. I recommend editing your web server configuration to prevent access to the endpoint until there's something legitimate that uses it.
@chanda See ya'll, this is what I mean by "toxic politeness".
This woman had a horrible experience in her first foray into the Fediverse, was treated horribly by the already-existing residents here(The same ones panicking about us Twitterers "colonizing" their perfect safe haven), and the conversation surrounding this is about whether she should be allowed to speak about it, because you all don't want Mastodon to look bad. Ya'll want it to APPEAR to be sunshine and rainbows when it isn't.
I believe it has the same Heterogeneous Multiprocessing design from cell phones, a combination of low-power and high-power cores, which helps a lot in terms of power efficiency especially when the software can take advantage of it.
Anyways, it's happening. The meek little SBC has grown up, it's a Real Computer now. Yes, things like graphics drivers and virtualization support are surely lacking. And it's not $35 any more. But as an affordable server platform for linux-based apps and containers, these little boards just keep getting better and better.
a user on the radxa discord quoted 18 Watts at the wall under 100% CPU stress. 4-5 watts at idle was a little bit of an underwhelming result, but it may be tune-able to get that figure lower.
RK3588 CPU has been picked up by Radxa, Orange Pi, and Firefly, and it pushes **serious** numbers on the CPU benchmarks, almost 4x better than the Raspberry Pi 4. Comes in 8GB and 16GB RAM flavors.
I am a web technologist who is interested in supporting and building enjoyable ways for individuals, organizations, and communities to set up and maintain their own server infrastructure, including the hardware part.
I am currently working full time as an SRE 😫, but I am also heavily involved with Cyberia Computer Club and Layer Zero