It was the first hug on my optimized #GoToSocial instance and I’m happy to report that there were no fire alarms or things exploding. Just a bunch of ❤️❤️❤️
Started using it just for an interface to my GotoSocial accounts/servers, but it's just so much better I'm logged in with the Mastodon account and not looking at default Masto web pages at all any more.
Just nothing about it is worse and many things are better. It's probably better than even the plans I had for my own client one day if I ever got the time.
Skimming lists with it is so smooth, you can adjust easily how much attention you pay to boosts as you scroll by depending how much time you've got.
The catch-up view letting you sort and filter things while you've been sleeping or at a meeting or whatever is very nice.
It has the thing I want: Is web-app, so is the same on firefox phone and desktop.
There are improvements I want but maybe I'll even build the source code and see if I can do it. Be easier that that my-own-client-one-day for sure.
tapi memang benar, kalo hanya sekedar host app seperti #snac2 atau #GotoSocial saja maka pakai VPS spek tinggi dan host di luar negeri itu terlalu berlebihan.
Aye pastikan pakai Vultr dalam 3 bulan ini dengan 1C 1Gb RAM dan 25 Gb SSD ternyata lebih daripada cukup. Pemakaian CPU lebih sering idle daripada kerjanya (baru kerja max kalo dipakai compress data untuk dibackup) dan Mem hanya kepakai 300 - 400 Mb saja dengan 1 load balancer, 3 http server, 2 app fediverse.
Instance juga tak terlalu ramai dengan pemakaian bandwidth sebesar 8Gb saja perbulannya, bahkan SSD tak kunjung penuh meski storage media sudah dilokalkan.
Tbh I'm not enthusiastic about a #Mastodon#hardfork. Not necessarily because of the #techdebt or even because it's technically inferior to other #ActivityPub implementations (which are both true), but because I cannot be sure if that new fork is going to adopt the same attitude as Mastodon in choking the rest of the #fediverse with its proprietary extensions and #EmbraceExtendExtinguish / #EEE.
I'd rather not have the uncertainty. Either start from scratch like #GoToSocial is doing or help the other two mainstream AP families which are #Misskey and #Pleroma. That's the only way we can ensure no implementation overwhelmingly dominates the fedi. :seija_coffee:
If your profile and posts are set to "public" and you can read this very post, you should have no sense of "privacy" here on Fedi. That means ANYONE can reply.
There's 20,000+ instances and new ones every day, there's NO WAY to tell who is accessing your posts or what they're doing with them.
Fediverse is not some kinda "bastion for privacy" nor is there any sort of "consent" required to see your posts if they are public.
The only way you can be 100% sure that your followers are the only ones that directly see your posts is to make your profile and posts private. Even then, screenshots exist.
Remember, you're on the internet. Once you post it, it's probably not going away. This is true everywhere.
I am used to simple things running on Docker (Jellyfin, Nextcloud, etc.) I am looking at running my own personal Mastodon instance (maybe share it with a few friends and family), but I like using Docker. Looking at install guides, the steps required seem to be much harder than just editing docker-compose.yml and running the...
Instead of the full-blown Mastodon, you should also look at #GoToSocial which is compatible and pretty light-weight. (Doesn’t come with a web UI, so you need to use client apps.)
If there were ever a single post that truly shows how running a Fedi instance is, that I could boost to the moon, it's this one.
People still somehow think that Fedi is "opt-in" or "privacy focused" or even "community focused". None of these things are true and I wish more people understood.
It's not a BAD thing, per se. I like it, personally. I choose who I want to interact with by blocking those instances I DON'T want to interact with, but it's OPEN BY DEFAULT is something some people can't grasp.😬
I said it elsewhere, but I say it here too, I HATE how corporate social media sites have taken SOCIAL out of social media.
Thankfully the Fediverse is mostly taking that back. But if we don't expand to get those that are still on corporate social media to move here, then we'll just become the echo chambers we hate. That's why the Threads integration is a good thing. We need to expand.
I'm experimenting on my tech tips articles with #ShareOpenly, a web app that acts as an intermediate layer between sites that want a share button and newer social media sites like #Mastodon instances.
The publisher links to Share Openly with the URL and title or description of the page to share.
The reader clicks on it and tells SO what site they want to share on (pre-filled or type in a hostname, with the manually added ones remembered).
SO opens that site's post form with the text pre-filled and ready to go.
It knows where to find the posting forms for several kinds of server software, and you can add a <link rel="share_url".../> template to your site to tell it where to look. I may do this for my Postmarks site.
But not everything has a post form that can be pre-filled. Heck, not everything has a front-end to begin with. So I can't just put that link tag on my #GoToSocial instance and point to the post form, because there isn't one. And it doesn't look like Elk or Semaphore have a way to pre-fill a post either.
sigh Sometimes I really wish #WebIntents had taken off.
ANNOUNCEMENT: The world's first general purpose #Akkomane server is here!
With great excitement, akkomane.social is open for registrations!
Akkomane is an alternative to #Mastodon and #Threads that provides incredible stability with a beautiful and futuristic Twitter-like front-end for the #Fediverse.
I have launched akkomane.social to demonstrate this software's unique capabilities.
Currently, I'm capping memberships to 20 people (not bots). While membership preference is given to those who'd like to build and maintain an Akkomane server, everyone is welcome to apply! More membership slots will be available in the coming weeks.
@atomicpoet@atomicpoet chris i like it! I'm hosting little #GoToSocial instance for testing right now, i like it for the minimum impact on my vps but can i ask you what is the RAM consumption for your personal akkoma space?
ini adalah instance yanfg dibuat untuk tujuan uji coba. Siang tadi ane mendapatkan akses VPS dari provider dataideas dengan spesifikasi basic yang ane install #openbsd 7.5 sebagai OSnya.
Tujuan pembuatan VPS ini adalah untuk belajar dan ujicoba openbsd, nantinya jika sukses besar kemungkinan ane akan migrasi dari vultr (#freebsd)) ke VPS ini.
akun utama ane masih pakai #gotosocial di @poes dan ane belum ada rencana untuk pindahan ke instance lain meski sekarang gts sudah support perpindahan akun.
Feditext beta users: GotoSocial announced their first 0.15 prerelease today, which includes filter support contributed by our very own Vyr.
Feditext version 1.7.2 build 101 improves filter UI by hiding the "Drop instead of hide" filter option when using a GtS instance, where it is not yet supported and won't work.
if you aren't using a GtS instance, you don't need to upgrade Feditext today.
Decided to go hardcore and build it from source, even though I don't even know the programming language Go that it's written in at all.
Went pretty well building and running it, wasn't difficult and it's easy to understand how to adapt the page templates and things.
Seems like account migration works well enough now.
Didn't notice that I'd failed to build a bunch of assets for a while so couldn't understand why the settings page wasn't working as suggested and pages were weirdly ugly and non-functional.
Building those assets is bloody node again. Annoying. Hoping to avoid that.
Anyway. It looks good. So customizable, no effort to really do a reader but you use phanphy or something for that. All I really want is good customizeable shop-windows and a functional API.
Thinking that's what I'll move to if further experimentation goes well.
#GotoSocial does not list 'unlisted' posts on your profile page when loaded in the browser ... without authentication.
This may not be new to some of you, but I just realised how big of a deal that is. It means that it kinda operates like local-only posts for randos, in that they aren't viewable by anyone who isn't your "friend".
i'm sure there is more to it than just that, but the brain is foggy today ... and ... come on ... that is huge.
i need to focus on learning #go as soon as i get back... the more time i spend with it, the more i am in-love with it and i wanna help the team... i wanna feel useful.
Which may be a feature as far as most GTS and Snac users are concerned!
But I do want Threads to technically be able to federate with most/all other software that uses #ActivityPub, so it can be user/admin choice whether to accept connections from the giant instance...and more importantly, to cut down on the risks of vendor lock-in and EEE.
And I hope more compatible systems will cut down on the "OK, my software federates with itself and Mastodon, I'm done" problem. In some cases there may be bugs on the smaller project's side, and fixing them might also fix issues talking to other small projects.
If Facebook had an issue tracker for threads, someone could open an issue there. If threads was an open source project, we could look at the code and immediately know what's up, but... 🤷
I might take a look at the Snac logs later and see if there's anything on this end breaking communication with Threads, or if it's all on the Meta side.
We poked around and this looks like an issue in our SQLite dependency, so we stepped down to the most recent stable version, and also added some code to prevent the problem from rendering an instance unresponsive.
No db migrations or config file changes between v0.14.0 and this version, so upgrading is as simple as updating your docker container or stopping GtS, untarring the release, and starting GtS again.
For instructions to update to this release from versions < v0.14.0, see the v0.14.0 release notes, but replace v0.14.0 with v0.14.1 throughout.
Is it that difficult to run Mastodon over Docker?
I am used to simple things running on Docker (Jellyfin, Nextcloud, etc.) I am looking at running my own personal Mastodon instance (maybe share it with a few friends and family), but I like using Docker. Looking at install guides, the steps required seem to be much harder than just editing docker-compose.yml and running the...