Forest @forestjohnson@pixie.town

@lefractal

The only reasons I can think of:

1. tor is slow
2. VPS costs money
3. You have to place your TLS private key on the VPS (so you are giving your private key to VPS provider)

I did create an alpha version of a cloud service designed to do almost exactly this and make it as easy as possible to set up: https://greenhouse.server.garden/

Right now that project is on a bit of a hiatus / rethinking phase but AFAIK it still works and can almost be used in "production" .

I say "almost" because I think there are still some bugs around re-connection; in order to be truely production ready, the greenhouse-daemon service that you run on your server should be wrapped inside a health-check / auto-restarter.

The benefit of greenhouse: You don't have to pay for a VPS & you get even better data custody / security than a typical "lazy/naive reverse proxy over tunnel" setup.

The TLS will be terminated on your home server instead of on the VPS, so you get exclusive ownership of your TLS private key. Plus greenhouse "automagically" handles the `PROXY` protocol stuff for you so your HTTP server/app will see the proper remote IP of the connected client via the `X-Forwarded-For` HTTP header.

Because of the lingering bugs in greenhouse, I don't use it myself.

cyberia.club uses something similar to what you mentioned for our own services: https://wiki.cyberia.club/hypha/infrastructure_and_operations/reverse-tunnel

Its the same thing as what you described, except instead of TOR it uses SSH. We don't have to be concerned about about having the TLS keys on the VPS because its our own VPS hosted on our own hardware (https://capsul.org)

1. make the "link to post" (which is currently a bit too hidden as an un-indicated hyperlink under the timestamp ) more prominent

2. expand the search bar to cover the whole top of the page, perhaps even make the current URL show there by default... ? IDK maybe this is too much... But its gotta be a better solution than that awful "type in your full handle in order to take this action" popup window

Yeah I am realizing that over time, also that paste-url-into-search-field is a core usage pattern for fedi

@fack

It will take me up to my alert level :(

You know what, I'm realizing that maybe the correct implementation for a fedi client has **a freakin <em>URL BAR</em>** at the top o' the page like its its own browser

@fack BTW how much ram does it use? Honestly considering running my own until gotosocial + UI options are looking better.

@fack Isn't this all software these days????

12k new accounts in the last hour

@fack I'm sure there's a way to do this.. I'm assuming you cant just shell in and slap your own theme file in there? Does fly let you run your own container? Maybe you can do a quick docker build with the container you use now in the FROM line and then just COPY or RUN whatever you need to get the custom CSS installed .

@auroris@artisan.chat The instance I am on puts a big ugly red CSS border around all non-alt-text'ed images on timelines. I really like that feature, I think it's something more instances / web apps should do.

It looks like there is a small guide on it posted by feditips here:
https://mstdn.social/@feditips/107854431995239439

And the direct link to the css Gist on GitHub: https://gist.github.com/FiXato/3de505b04efefd49a1e3568b70545234

I created an account for my dogs to try out pixelfed: @fedipugs

So far its been a bit rough (no video support, hyperlinks get broken 🪦)

But if you like cute pet pictures maybe it could be worth a follow, I'll try to post when I can and occasionally maybe repost older stuff from the instagram that my partner made in the past.

@j3s https://picopublish.sequentialread.com/files/linking.mp3

```
Updating crates.io index
Fetch [===================> ] 82.56%, (163401/213323) resolving deltas
```

Ok, tinygo is definitely not stable enough for this, moving on to trying rust instead https://docs.rs/age/latest/age/ 👀

my co-streamer is with me today 🙂 🐶​

From yesterday: research into related memory leak here: ​https://github.com/tinygo-org/tinygo/issues/1140#issuecomment-1314608377

Streaming again, getting to work on running FiloSottile/age to run in the web browsa (compile golang to WASM with tinygo compiler)

music rn: 🎸🎺 Less Than Jake 🧨🍺

https://stream.sequentialread.com/

@fack

https://github.com/mastodon/mastodon/issues/20820

> **USABILITY: init db before configuration is completed causes silent failures / broken instance #20820 **