@0wl [ESP] Te damos la bienvenida a gnusocial.net. Varias cosas:
- Es NECESARIO responder a este mensaje para levantar el aislamiento inicial de tu cuenta.
- Las cuentas que continúen aisladas al cabo de un mes serán borradas.
- Las cuentas antiguas sin actividad serán borradas al cabo de un año.
- Documentación: https://gnusocial.net/url/7821081
[ENG] Welcome to gnusocial.net. Several things:
- You MUST answer to this notice in order to get your account initial sandboxing uplifted.
- Sandboxed accounts will be deleted after one month.
- Old accounts without activity will be deleted after a year.
- Docs: https://gnusocial.net/url/7821081
@t3rr0rz0n3 ¿Puede ser que escribieras un artículo sobre usar "Federation" en Nextcloud para hacer copias de seguridad entre dos instancias de Nextcloud? No encuentro nada en voidnull.es. ¿O a lo mejor simplemente lo comentaste?
simsa04 (simsa04@gnusocial.net)'s status on Saturday, 29-Oct-2022 16:18:06 JST
simsa04The main hurdle in explaining the #fediverse to people coming from Twitter is that they're accustomed to a singular, self-contained instance in which their posts are disseminated across the whole instance. They are thus far more statement-focused. In the #fediverse with its multitude of instances, relations of dissemination are conversation-based. (Follower relations make instances and accounts seen by other instances.) The differences in technological setup explain the difference between "scream media" (Twitter) and "social media" (Fediverse). We'll see how newcomers will handle that.
@dcent I remember trying to remove the artifact and it the patching also failed, that's why I have not applied it.
And yes, it would be nice if you could upload your patches to the repo, https://git.elbinario.net:8000/gnusocial/elbinario so more eyes can review/correct/use them.
BTW @administrator, would you like me to re-upload the CSS patch for Elbinario Theme that properly centers the website or do you know how to use the previous one?
Basically the last (17th) hunk that tries to remove the badly encoded character can be removed or even ignored. You can fix that badly encoded character by simply re-typing the last few characters in that line yourself.
Its an issue in itself that a badly encoded character is in the CSS, so we should seek to fix that immediately. Apply my patch after. It will complain about the 17th hunk but you'll be able to ignore it (because you'll have already fixed it yourself).
@dcent About the cache: right now, the cache is configured like this:
text/css 30d;
application/javascript 30d;
~image/ 30d;
~video/ 30d;
~audio/ 30d;
Everything else is not cached. I understand that, in order to show that you've liked a notice, that particular thing can't be cached, else it would not show.
About images: you are right, it's a poor UX. I'm afraid I don't know devs plans about it. I know a new interface is in the works, but that's about it.
Can pages have a longer cache time? What I've noticed is after I 'like' a person's post for example, and a new page is loaded to tell me the 'Like' was successful, I hit 'Back' in the browser but the page from earlier is not cached so the browser is forced to fetch a new page for the server; 100% of the time (so far) that page has been identical, no need to request a fresh page. I think this needs to be fixed to improve experience for both end user, that must wait for the fresh page and the server that must do 3x more work (on average) for zero benefit; a 5-minute cache time would fix this.
Also, images in posts should be enlarged in a new tab when they are clicked, not when the little link above the image is clicked. Currently clicking an image does nothing, and it's poor UX, I've put this past a couple people now and they seem to struggle with the UI. In all fairness, the little link above the images is only clutter, it is not even useful as a caption because it is often truncated.
Are these issues listed for GNUSocial v3? If not, I'll be interested in someone being so helpful as to copy-paste into it.