I use mailbox.org which works fine, costs a euro a month, and has German Privacy so I'm not toooo worried. But it's not technically self-hosted even if it's @sirtaptap.com currently
I also have Paypal and Patreon, but the point is more to have as direct and 'on premise' a form as possible not just send traffic over. Plus fuck paypal
I’m gonna have to host this thing myself again, haven’t I? My Mastodon host, Fedi.monster, does not offer full-text search (ElasticSearch). Exporting the database and searching it by hand to rediscover posts is getting old. I wish I could just use my domain with one of the existing instances rather than having to maintain a full instance just to get my domain as the handle. Mastodon is nothing like email. #Fediverse #selfHost
I bet #Gandi is seeing a lot of imapsync work these days ...
 this page can be of help for anyone moving from one email provider to another to get it's archive transferred without relying on the providers user interface (that may not exist) : https://yunohost.org/en/email_migration
aujourd'hui 29 novembre, notre serveur souffle sa première bougie 🎂
joyeux fédiversaire à tout g33ks.coffee 🎉
une première année à surfer sur le Fediverse 🌊 l'occasion de regarder ce qu'on est devenu au fil des mois :blob_cat_heart:
One year ago this week, I setup my solo single user Mastodon instance at https://futurist.info
I thought I would give a shoutout to everyone that was involved in the effort. (Me). Thank you to the team (me) for all the hard work and effort! You did a great, fantastic job with stellar results!
(Wait - there was no hard work or effort. But a shoutout is still nice)
The story of my setup is in my profile.
I have spent about $150 or so for the year. For me, it's well worth it.
Thank you for all the followers, and I look forward to another great year!
Now I feel guilty that I haven't posted from my pixelfed @email@example.com account for over a month. (see linked stats😆 ) The reason why is it turned out there was no fix for the issue of not being able to see mstdn and pxlf accounts from one another becauee they are on the same physical box. 😢
#stats #mastodon #fediverse #pixelfed #selfhost #mastoadmin #pixelfedAdmin
We've upgraded to the kernel v5.15.0-89 ☑️
You might have seen a few "502 Bad Gateway" errors while the server was rebooting, but everything is back to normal now 👌
ℹ Up-to-date information
🗞️ 100% reliable Synology-related news
🧪 1st hand tests and tutorials
🎁 occasional giveaways including Synology hardware
☎️ 1-3 h per month for Synology consulting or #Docker assistance (depends on the subscription tier)
What's the point of an #anonymizing #messenger if they - in clear violation of #GDPR & #BDSG - conmect that to a #PhomeNumber which im more juristictions than ever can't be obtained anonymously in.any legal capacity???
I am a nerd and so I always want to know when the next release of software XYZ is coming… so for Mastodon:
Plex ruffled some feathers this week with their latest e-mail marketing campaign, so we've compiled a list of privacy-related settings every Plex user should review.
Let us know if there's anything we've missed!
Said bye bye to Proxmox on my home server today. I wasn’t really using it so wiped it for Ubuntu Server instead.
Now to self host a load of things I don’t need 😂
Heyho. Christmas time is coming and as always I'm ill-prepared. 😬
It's now able to handle multiple years (so the unlocked pictures from yesteryear aren't gone) **and** it can play videos. 🤯
Check it out here:
It's written in #Go and uses templating for the HTML pages. The text is currently fully in German, but should be easy to localize.
They're pretty good. Obviously not perfectly equivalent to #GPT4 but not a million miles away — and absent restrictions and the odd, overly-friendly, American undergrad paper tone.
I can't stop it. I'm now #selfhost addicted. I hosted a blog with #Ghost and it was cool. Then I hosted #UmamiAnalytics and integrated it into the blog. Then there was a #Gitea instance with some of my public repositories, previously hosted on #GitHub. And I have #Umami on Gitea as well now =) Because why not?
There are so many nice #FOSS out there! Need to try each of them! :blobcatscience:
So now the URL is https://sirtaptap.com/videos/ and I've removed most reference to YouTube where unnecessary.
Maybe I’m just getting old, but I’ve started to move to #selfhost more and more; decided to go ahead and buy a m2 pro mini as well to play more with local AI stuff..
googled an old banger tweet and forgor it won't be on google anymore. Gotta #selfhost my own twitter archive. I know I can do it just haven't bothered yet
I'm using Perfectly Push. It's options aren't as great as OneSignal but...onesignal deleted my several hundred subscribers. So.
It also links to my front page, not the article that I pushed! Not sure if I'm doing something wrong or if there's a better way.
As an experiment, I just managed to run the entire stack of @feedbackbulb on a MicroCloud (https://github.com/canonical/microcloud) and it really did take about 30 mins from watching the keynote and skimming the docs to a fully functional, highly available (8 nodes) instance of Feedbackbulb that can receive a feedback report. I've never used lxd before so I need to read a bit more but so far I'm loving it :).
Ask me anything!
Coming up to 1 year that I set up my single-user Mastodon instance at https://futurist.info
I was convinced that protocols were the future, and that controlling my destiny in the Fediverse would be important - and that running my own server would best help me understand what the protocol was all about.
I tell my story here, from a post last December:
"You might notice my Mastodon instance name, futurist.info
It's just me here. I decided early on I wanted my own 'identity' ; my own instance. Just like I got my own email address back in the 90's (under jimcarroll.com)
I think over time :
- you might find your current Mastodon home doesn't fit your future - it might become like a HotMail or AOL email address
- you might want to know how Mastodon actually works by having your own setup
- in the months to come, we will see a LOT of paid self-hosting options that might let you set up your own identity for a small fee.
With all that in mind, here's the story of how I did it."
I have added this new setup to the services setup section (Step 10) in my little how-to on creating your own mastodon server from an old iMac.
I've decided that just to be consistent with the current recommendations at joinmastodon.org, I'm going to bring the total threads on #footiMac back up to 25. 10 each for the two processes handling default/ingress/push/pull queues, and 5 for the process handling mailer/scheduler. I've been watching the sidekiq live-poll screen and want to see if bringing them back up to 10 helps clear the queue a little faster as when I post, both queues used 5/5.
#selfhost #mastoAdmin #selfhosted
The changes for my little 2-user #footiMac are doing well. When the queue fills to 100-200 it is quickly dealt with. Creating two processes/services for the four main queues allows them to use the two cores without blocking each other. The mailer and scheduler have their own service. I feel like the docs on joinmastodon.org should really replicate something like this rather than one service for all sidekiq queues. It's not a big deal as far as complexity and probably sets people up better for scaling if they do grow..
#MastoAdmin #selfhost #selfhosted #mastodon #thanks
You can see how I came to this setup from this thread:
Cuz I think this would work great and #decentralization would definitely reduce the burden of hosting and allow to further adapt it.
I.e. adding an #OnionService because I'm the kind of #MadLad that shoves vintage systems running #Lynx on OS/1337 (#toybox + #musl / #linux) behind a #OPNsense to provide them with @torproject / #Tor connectivity until I have ported that to #OS1337 as well...
I took the example from the resource linked before. This was my procedure:
1) I increased the sidekiq process to allow 75 instead of the default 25 workers. This helped, but it was still full and only going down slowly.
2) Then I split out the processes (by duplicating the systemctl file and make one each for the ingress, push+pull, default, scheduler, and mailers. All had 75 workers. It turned out only the pushpull service was pinned to that 75 and database connections went to over 200.
3) So I split the push and pull into separate processes and realized it was all on the pull process. All other processes were very low.
4) Finally, I reduced the number of workers back down to 25 for all processes except the pull process. RAM usage has quadrupled from 400MB to 1700 but I had space there to grow into.
My server is now back to a good place, database connections are below 50, nothing in the queue, and toots/notifications are going out instantly again.
And most importantly, I can once again handle all the news GottaLaff puts out! :D
I suspect #footiMac is getting a little overtaxed. But I am wondering if other #selfhosted #mastoAdmin have a thought about these messages in Sidekiq for dead processes? Too many files open, on my end or the remote end?
Is there maybe a FAQ available for small admins like me to look to that might show the most common indicators of problems on a Mastodon host?
I guess I will write a blog entry at https://jan.wildeboer.net on using #forgejo  as a lightweight project management tool using the MKS (Milestone Kanban System)  using the built-in issue, project, wiki. I think it is a good approach for many little non-software projects out there. And #OpenSource and simple to #SelfHost as a #container.
I think that maybe the Wordpress ActivityPub plugin that federates my blog has been causing a lot of undue PHP process activity. Any activity with friends/followers or when a post is published, it overloads my server. Anyone else federating their wordpress based website (self-hosted) seeing this problem? It might be interacting somehow with LiteSpeed Caching? #selfhost #wordpress #selfhosted #mastoAdmin #ActivityPub #Fediverse
We've just had a 7-minute internet outage, but everything is back up and running 📶
I need a replacement for DropBox.
All I use DropBox for is syncing a small number of files between 2 laptops and 2 phones and mostly as an easy way to send photos to the laptops from the phones. Their current free plan only allows 3 devices.
Happy to self host.
Somebody tell me why or why not I should #selfhost my own #Matrix server. I'm going insane with indecisiveness. On one hand I think it'd be cool to have an instant messaging service I host myself for my partner and I to use, but on the other hand I'm still kinda bummed at all the work I put into trying to selfhost a Mastodon instance that I ended up having to give up on earlier this year. I have precious few hours to spend on personal projects and I just can't decide what I want to spend them on
I know there are official numbers for this, but I'd rather hear from real people that run it.
RSS is great, now let's see how we can self-host FreshRSS on Fly.io
g33ks.coffee will move! 🚧
Our server will be unreachable tomorrow:
- from 06:00 AM CEST the 6th
- to 15:00 PM CEST the 6th
Indeed, we're moving to another town on this day 🚚
You won't be able to interact with us during the operation, but we can't wait to be back online from our new home 🏡
Our french blog post: https://www.g33ks.coffee/2023/10/05/indisponibilite/
SSRF is usually mitigated by preventing any requests to an IP that is not publicly accessible 
But in a home / self hosted env, you probably want to allow your local services to talk to each-other. If you run an app that makes requests to arbitrary addresses (think fedi server!) you may now be exposed?
I'm planning to self-host a few things (Mastodon, Home Assistant, Nextcloud, ...) and want to have some recommendations.
Should I use different cloud providers/ VPS/ servers at home? What is the most cost-efficient variant? What other platforms should I host by myself? Do you have other tips?
well i'm glad you asked
so here is the main thing you should take into account when you write anything you expect to be hosted by more than you or your employer:
You Are NOT The Only Thing Running On This Server
what does this mean in practice?
- don't attempt to handle common tasks such as ssl yourself. a reverse proxy is generally the first thing that gets set up, you can safely assume one exists.
- make your reverse proxy setup as painless as possible, ideally it shouldn't be more than a proxy_pass/reverse_proxy call (but unfortunately situations like /.well-known exist)
- don't bundle common dependencies like databases or redis, because there will generally be something else that will already require one set up.
- don't run multiple common dependencies at the same time (cough cough lemmy-ansible and a million other stuff running 2 half-configured nginx instances for the same thing that can be done with 1 well-configured instance)
- a big hell no to anyone who puts apache inside a php container. i get it php hosting sucks but at least go for php-fpm
- prefer common dependencies over obscure ones if possible (you better have a really good reason to pick an sql db that isn't postgres. mysql is begrudgingly acceptable. sqlite doesn't count)
- that said, resource usage is a really good reason to pick one dependency over another (say, a lighter search indexer than elasticsearch)
- don't assume you have full control over the above common dependencies (compiled extensions, weird configuration requirements)
- don't pollute the filesystem in a way that can't be trivially cleaned up
- so, either use the package manager or place files in predictable and non-shared places
- containers do not solve any of these problems (ok maybe except the last one), they just sweep them under the rug. do not rely on containers as your only way of installation.
- and for sure do NOT bundle common dependencies INSIDE containers, (cough cough gitlab)
- opaque install scripts are even worse than containers and should not be your only way of installation (cough cough pihole)
- opaque install scripts that assume a clean slate and blindly overwrite global configuration is a horrible idea and should have big red warnings.
- opaque install scripts that set up containers under the hood are only slightly less bad (still a bad idea)
- that said, for those who want the option, the last couple are definitely nice to have (they should not be required, however)
- the only thing necessary to host your thing should be a reasonably normal linux system (no cloud function serverless whatevers)
- try keeping resource usage in mind, unused ram is not wasted ram if there are 20 different services all competing for that ram
- scaling down is more important than scaling up. don't hoard excess resources ahead of time if the only reason you're doing that is so you can scale up in the future
- have actual installation documentation beyond "docker compose up" or "curl | sh" or "todo"
- while you are not obliged to support weird setups (musl, bsds, whatever) you shouldn't be hostile to them. they know they're running something unsupported and as long as you fix the often-not-that-hard compat issues they report, they'll do the hard work themselves
- you should never EVER REQUIRE a mail server, what is wrong with you?
there's probably more but it's apparently 3am so my brain is starting to go into eepy mode
#selfHost #selfHosting #selfHosted
Time to make a proper #introduction
My name is Ilya, but online I usually go ether with Mango (my sona name) or Ilya_MZP.
I'm 22. Pansexual. My partner is @ItsFunkyCaptain
Student and an IT help desk employee.
I post mostly about tech related topics (#linux #programming #selfhost #hvac #RighttoRepair). Horny on main, I repost #fatfur art. Used to draw back in the day, but abandoned that... I like #photography, so expect some nice pictures whenever I go out on my bicycle. Yes, I love #cycling