Local timeline

Replying to @xenotar

@xenotar @fasnix @shom @madamada We're not planning to add mysql/mariadb as it will make the codebase larger and harder to maintain and we'd avoid it, at least for now.
We're planning a db switch procedure so you can switch from one to another in a native way.

Replying to @fasnix

@fasnix @shom @madamada I don't know 😃 Some local automated tests show that 100 users with sqlite are fine, as long as there's not too much concurrency in writing stuff into the DB. For the public server....I don't know as well. The limit will probably be the limit of the hardware I'll be using. There's something to be fixed: blog generation will only work on single process installations, not on clustered setups. I'll probably easily adapt it to build blogs only on one specific machine (the one doing the housekeeping). Still, the blogs will finish into the local file system, so this needs to be sorted, too. But this will come later.

Replying to @stefano

@stefano @fasnix @shom @madamada Forgejo allows you to choose between SQLite (default), PostgreSQL, MariaDB, or MySQL. I don't know how laborious or complicated it is to implement this functionality.

Replying to @stefano

@stefano
If you add a public server, would you aim for it to accept an "unlimited" amount of users, or would you rather restrict it to, say, 100 / 500 / 1000 users?
(Where are the limits for sqlite?)

@shom @madamada

Replying to @madamada

@madamada
On the one hand, I understand your approach.
On the other hand: most fediverse services aren't like twitter at all, as they offer far richer functionalities.
So, a comparison to only twitter could end in:
"I never used twitter anyway, so the fediverse isn't for my liking."
I think it's necessary to show a broader view of what different fediverse services are capable of.

Replying to @fasnix

@fasnix @shom @madamada this server will be permanent.
I'm planning to add a "public" server. I'm not sure if it will be this (using sqlite, we could hit some limits) or another one, using PostgreSQL, ready to scale.

But yes, this is our littleOne and will stay.

Replying to @shom

@shom
I agree, however, I hope this server will stay permanent, not just as a "test environment" :)

@stefano @madamada

Replying to @menel@snikket.de

@menel@snikket.de oh hi @menel@snikket.de! Yes I did, part of the reason to change was just to upskill and increase my knowledge. I already have some regret as it was insanely solid and never missed a beat, but Prosody is still sitting in it's proxmox container - it isn't being deleted and may go back to it once I've had my fun 😉

Replying to @drscream@fru.bar
Nigel
@nigel
Public en edited

@drscream@fru.bar @stefano@bsd.cafe mainly masochism I guess... 🤔
I have a solid Prosody server setup, has worked for years great, and in that time I also dabbled with ejabberd but never in any serious way. So I thought, how can I learn how to make this clearer in my head... I know, run in production!

The main reason really is that I have grand ideas of running a public server one day, and read @thomas@metalhead.club post on migrating trashserver.net from prosody to ejabberd back in the day - and a friend still uses his server, which seems solid. The invite system ties into this longer goal/dream/stupid idea.

So yeah, basically because I wanted to learn things. If someone was starting out, or even not just starting out but wanted their own server, I 100% recommend Prosody. Every time.

Replying to @nigel

It turns out I found a minor bug in the invite system 😅

But its working, and friend invited ☺️

Replying to @mavu@mastodon.social
Nigel
@nigel
Public en edited

@mavu@mastodon.social it treats it like a linked desktop client I believe. You still need it installed on a phone. I use it for work unfortunately, but on a separate work phone, and it means my xmpp clients can all access the same chats as well.

And my wife and kids use it also, so the family group chat is on whatsapp - and the slidge bridge means it is also on my personal phone and desktop pc without whatsapp being able to access those devices.

Nigel
@nigel
Public en edited

@tabby@gts.iltabellinoweb.eu yes and no; people dont back anything up ever and just assume the stuff on their phone is safe from mishaps even though we have repeated evidence to the contrary. So I'm on the fence about this... but then regular folks wouldn't back up their server either I guess if its on a Pi zero 🤔

Replying to @fasnix

@fasnix No, you can convert any of your posts to blog posts whenever you want to. But you can't convert a boost into a blog post. Which sounds reasonable, I think.

Replying to @fasnix

@fasnix Ever after gifting my daughter my perfect Grüne Erde-futon and switching to our current Emma-setup, I am dealing with lower back and neck pains. These matrasses are way too soft and look absurdly large in our bedframe. I've been meaning to get another futon again, so this is motivational. :D

Replying to @stefano

@stefano
"Why does it work without JavaScript?
Because a social server is infrastructure, and infrastructure should not stop working because a bundle failed to load, a browser is old, a connection is bad, or someone reads the web with scripting off. Pages are rendered on the server; JavaScript improves them and is never required by them."

Love the consideration!

However:
"Only public, top-level, non-boost posts that were explicitly marked as blog posts are published."

Does that mean that if a publish a post in the morning that gets boosted during the day, I cannot transfer it to a blog post in the evening?
I would have to make that choice right away when publishing a post?

Replying to a post that is no longer available

Another step closer to release!

The official website is now live at https://littlefedi.org/ with documentation and project details.

Take a look and let me know what you think!

#littleFedi #Fediverse

Replying to @casolina

@casolina "all around the world" 😃

Welcome!

When I write something here, where does it go?

Good morning, #littleOne friends!

I pushed a couple of fixes - mostly in the admin interface, and now the composer will auto-collapse on threads, too. The interface should be cleaner now.

Have a great day!

#littleFedi

Load older posts