Self Proclaimed Internet user and Administrator of Reddthat
I’ll be posting some of them which I find are interesting!
Thank you for the update and it’s good to hear your upcoming plans. Being one of those people in Australia (Reddthat) it will be good to see if it actually works as it’s designed too!
I’d love to save $7/m to not have a server dedicated to batching the federation traffic 😅
When you lay out the timelines for 0.19.3 onwards no time at all has gone by, and having to deal with the issues after .3 has certainly not been fun as an admin. (And I’m only a small server compared!)
Being such a huge player in our Lemmyverse, thanks for taking the time to plan this out as I know how much testing has been done to get us this far.
It’s always a nice experience chatting to the LW team!
Hope your updates go smoothly!
I too would love to know what your experiencing (so I can fix it!)
Article says the initial compromise of the non-airgapped systems is an unknown vector. So how they got into the organisation(s) in the first place is still a mystery
This is sso support as the client. So you could use any backend that supports the oauth backend (I assume, didn’t look at it yet).
So you could use a forgejo instance, immediately making your git hosting instance a social platform, if you wanted.
Or use something as self hostable like hydra.
Or you can use the social platforms that already exist such as Google or Microsoft. Allowing faster onboarding to joining the fediverse. While allowing the issues that come with user creation to be passed onto a bigger player who already does verification. All of these features are up for your instance to decide on.
The best part, if you don’t agree with what your instance decides on, you can migrate to one that has a policy that coincides with your values.
Hope that gives you an idea behind why this feature is warranted.
Yeah that’s why I included the other “main posts”… Their technical details really didn’t say anything technical
Oh I was wrong, after further reading this looks to be a lot better than what I was thinking.
I must have been thinking about another methodology of attempted privacy over a dataset.
Before I start reading, if this has anything to do with differential privacy, I’m going to be disappointed.
A faster db. Just the regular performance benefits, https://www.postgresql.org/about/news/postgresql-16-released-2715/
Also, Lemmy is built against v16 (now) so at some point it will eventually no longer JustWork
The script will be useless to you, besides for referencing what to do.
Export, remove pg15, install pg16, import. I think you can streamline with both installed at once as they correctly version. You could also use the in place upgrade. Aptly named: pg_upgradeclusters
But updating to 0.19.4, you do not need to go to pg16… but… you should, because of the benefits!
The downvotes you can see (on this post) are from accounts on your instance then. As this post is semi inflammatory it is highly likely to have garnered some downvotes.
Edit: I guess I was wrong regarding the logic of how downvotes work when we block them. As the http request (used too?) return an error when responding to a downvote. I’ll have to look at it again. As the only way it was/is 15, is if:
Right? Such a good vibe.
We rebuilt the Lemmy container with an extra logging patch. Seems build docs need some work? as that’s the only difference in the past 1-2 days, except for moving to postgres 16…
Thanks for the ping.
I’ve gone back to mainline Lemmy. @Morpheus@lemmy.today check now please
Should be fixed. (It already got merged: https://github.com/LemmyNet/lemmy/pull/4213)
It’s a sad day when something like this happens. Unfortunately with how the Lemmy’s All
works it’s possible a huge amount of the initial downvotes are regular people not wanting to see the content, as downvotes are federated. This constituted as part of my original choices for disabling it when I started my instance. We had the gripes people are displaying here and it probably constituted to a lack in Reddthat’s growth potential.
There needs to be work done not only for flairs, which I like the idea of, but for a curated All
/Frontpage
(per-instance). Too many times I see people unable to find communities or new content that piques their interest. Having to “wade through” All-New to find content might attribute to the current detriment as instead of a general niche they might want to enjoy they are bombarded with things they dislike.
Tough problem to solve in a federated space. Hell… can’t even get every instance to update to 0.18.5 so federated moderation actions happen. If we can’t all decide on a common Lemmy instance version, I doubt we can ask our users to be subjected to not using the tools at their disposal. (up/down/report).
Keep on Keeping on!
Tiff - A fellow admin.
I use Wasabi storage which is more expensive as they have a minimum space allotment but because my servers are in Aus I had issues with backblaze b2 storage and the latency. (I was dealing with 200-300ms in network latency AU -> US + the time that backblaze takes to store the data).
At that time lemmy/pictrs was not as optimised as it is now so it’s much better now.
Backblaze comes out WAY cheaper per-month if you have servers in us/eu, as close to their regions as possible, but they also charge you for API.
As part of an Object Storage / cdn remember you also might have to pay for egress charges as well. Cloudflare is part of the “Bandwidth Alliance” but that isn’t applicable here as pictrs needs to present the images via its own domain, (such as cdn.reddthat.com). So you’ll still want a CDN infront which will mean you will only pay once for the egress instead of everytime everyone loads it.
Reddthat has… looks up 150GB of object storage now.
I would recommend B2 if you are starting out and are in US/EU. Wasabi in all other regions and have a CDN infront. (and don’t mind burning a little cash for peace of mind)
Don’t forget & in community names and sidebars.
Constantly getting trolled by &
What a hero!
I guess it all depends on what you find interesting. I have the brief extension installed on my browser and whenever I find blogs or people I enjoy if they have an atom/rss feed I subscribe. Over the years you find lots of content.
Some of the random sites I follow:
Lemmy is still saving thumbnails and (previously) sometimes the whole image! The majority of image issues have been cleared up in my opinion and it works very well. Nearly all of our hosts allow hotlinking as it’s basically required for our use cases.
Lemmy also knows when the image is another Lemmy instance (through “magic”, or just cross posting). So if you upload once and then use that same link on all other posts then that would still be the same.
The problem I think you have is your usecase also includes posting externally to Lemmy. & to some extent, you don’t want those images tied to your Lemmy account. If my users post via my instance then they are welcome to also hotlink the images externally. This is only possible because Reddthat uses a CDN and caches the images as much as possible.
Even if we didn’t use a cdn there are plenty of VPS’ and proxy software that we could use which would transparently function in the same way. You could even setup your own VPS, some image hosting software like https://chibisafe.moe/ or https://github.com/nokonoko/Uguu or https://github.com/hauxir/imgpush
To sum up:
The 3rd option you can do completely anonymously via crypto.