publicação cruzada de: https://fedia.io/m/fedia/t/496603

Venda, comercialização e instalação de caldeiras, aquecimento central e energia solar térmica, assistência técnica profissional venda de peças e componentes.

publicação cruzada de: https://fedia.io/m/fedia/t/496611

Assistência caldeiras CHAFFOTEAUX ET MAURY, serviços de assistência técnica especializada na reparação e manutenção de caldeiras e equipamentos para aquecimento central

publicação cruzada de: https://fedia.io/m/fedia/t/496611

Assistência caldeiras CHAFFOTEAUX ET MAURY, serviços de assistência técnica especializada na reparação e manutenção de caldeiras e equipamentos para aquecimento central

Hello

I have noticed that the server have been going down a lot for 10 - 20 mins.

Unfortunately, I'm currently on vacation, so I don't think I will have the time to fix it.

I will be back tomorrow evening and will look into it and hopefully fix it then.

EDIT: There was a misconfiguration of the auto scaling setup. This scaled the system up and used all of its CPU, which caused the site to be unresponsive.

This should be fixed now, but I will keep monitoring it.

PieFed - Open Source Federated Forum

https://join.piefed.social/

@piefed

PieFed - Explore Anything, Discuss Everything.

While working on a small fix to lemmy, that was causing some unneeded cpu usage, I made a change that unfortunately caused the db and pictrs service storage to be deleted.

Thankfully I have backups of everything, so I went to restoring from a backup. However the restoring was very slow, since I used an unoptimal way to backup the db(raw sql dump). After the first backup completed, I found out that it was missing data, so I tried an older backup, but that didn't work either. It was missing data as well. So I tried a backup from another server(Since I backup to 2 different servers), which finally worked.

Usually restoring from backups, haven't taken too long previously, since my backups are faily small, but I will need to look into a quicker way to restore backups for lemmy, since the backup size of lemmy is much bigger.

NOTE: Data from ca. 2 hours before the site went down(16-18 UTC) will be missing and I'm unable to restore it.

I just upvoted a comment in a community hosted on my site, and in the nginx log I can see:

ip.address - - [19/Feb/2024:14:33:31 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://endlesstalk.org"
ip.address - - [19/Feb/2024:14:33:43 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://endlesstalk.org"

Dumping out the activity, I can see:

... (single vote from account on another instance) ...                   
{
  "@context": [
    "https://join-lemmy.org/context.json",
    "https://www.w3.org/ns/activitystreams"
  ],
  "id": "https://endlesstalk.org/activities/like/f102d062-dfe9-4ece-96e8-310a09b249ba",
  "actor": "https://endlesstalk.org/u/freamon",
  "object": "https://sh.itjust.works/comment/9061222",
  "type": "Like",
  "audience": "https://lemmon.website/c/tails"
}
... (single vote from account on another instance) ...        
{
  "@context": [
    "https://join-lemmy.org/context.json",
    "https://www.w3.org/ns/activitystreams"
  ],
  "id": "https://endlesstalk.org/activities/like/f102d062-dfe9-4ece-96e8-310a09b249ba",
  "actor": "https://endlesstalk.org/u/freamon",
  "object": "https://sh.itjust.works/comment/9061222",
  "type": "Like",
  "audience": "https://lemmon.website/c/tails"
}
... (single vote from account on another instance) ...        

It's the same for comments too (if I grep the dump for other people's comments, there's only one, but there's two for comments made by me)

EDIT: can also see dupes from lemmy.ca (they actually sent the same Like 3 times).

The s3 host that pictrs use, have gone down.

I might have to move to another s3 host, which will mean it will take a bit before images are working. This will cause a loss of images for the last 2-3 hours before pictrs stopped working.

EDIT: Have moved to new s3 host. Unsure how many images were lost during the outage.

Local time can be seen here

0.19.3 is mostly bugfixes. See release notes here for more information.

There should be no downtime or very minimal downtime. If there are any issues, check the uptime site here or site status here

Local time can be seen here

0.19.2 contains fixes for outgoing federation and a few other things. See release notes here for more information.

There should be no downtime or very minimal downtime. If there are any issues, check the uptime site here or site status here

EDIT: The server went down / was very very slow to respond. I'm not quite sure why.

The 0.19 version is out and I expect to update sometime during the next week. Since it is a big release, I will need to spend some more time testing, that everything still works fine and ensure that the migration works without problems as well.

I will update with another post, when I know, when the update will take place.

Cross posting

Cross posting from nostr to Lemmy

@0bd4b3c7

Ye ek ḅot simple guide hæ, meri script, yani "hinglish-lipi", ya ise iski hi lipi me "hiṇgliṣ-lipi", ke bare me :

Rules

+ agr koi alphabet normal diḳ rha hæ, ṯo use væse hi pronounce krna hæ jæse normal hinglish (whatsapp ḅaṣa) me krte hæ :
Example : k = क, p = प , m = म

+ ek vyṇjn ki pronounciation krne ke liye 2 alphabets ki koi zrụrṯ nhi hæ :
Example : नमकीन ≠ namakịn, नमकीन = nmkịn

+ agr koi alphabet alg diḳ rha hæ, yani alphabet ke nịẋe dot ho, to use væse hi Use kreṇge jæse normal hinglish (whatsapp ḅaṣa) me kisi alphabet ke ạge "h" lgakr pronounce krte hæ.
Example : खाना = ḳana , शांति = ṣaṇti
+ yhi same alphabet ke nịẋe dot swar ko bṛi mạt'ra me convert kr deta hæ :
Example : कौन = kꜷn , कीमा = kịma , इमली = imli , कैंची = kæṇẋi
Exception : ṛ = strong 'r' ; ẋ = च ; ẍ = छ

+ ट, त ko normal hinglish me "t" aur ठ, थ ko normal hinglish me "th" liḳṯe hæ, isi vjah se ट, त, ठ, थ ko t, ṭ, ṯ, ṱ liḳa jaṯa hæ respectively.

+ kuẍ hinglish ꜷr english ke words same diḳ skṯe hæ, jæse use aur use, iske liye jb mn kre english word ke phle - lga skṯe hæ
Example : use -use krna ṱa

+ अनुस्वार, चन्द्रबिन्दु lgana hæ ṯo ṇ ka -use krna, word ke last me lgana ho ṯo ẍoṛ ḅi skṯe hæ.

+ agar ị word ke end me ạ rhạ ṯo use i ya ị dono liḳ skte hæ, væse agr word ke bịẋ me ạ rhạ hæ to ḅi dono -use kr skṯe hæ lekin isse confusion ho skṯi h

+ same ạ ke liye ḅi hæ, bs ạ me confusion nhi hoṯi generally, to ạ ka -use bs words ki starting me krṯe hæ

+ hlṇṯ yani ạḓe vyṇjn ya ' ka -use krṯe hæ : Example : क्या = k'ya or kya

+ vyṇjn ke bad svr, jæse नई ko ni nhi likh skṯe isliye "n`ai" , agar नाई liḳna hoṯa ṯo "nai" liḳṯe hæ siḓa.

+ pronounciation ke vjh se spelling mistakes acceptable hæ, jæse बहुत ko "bhuṯ" ki jgh "ḅoṯ" liḳna, lekin isse confusion ho skṯi hæ !

v1.0

@nerd

Real Shitpost # 1

Hinglish Plus Pro Script made out of unicode characters

Consonants

क 𑂍
ख ખ *
ग 𑂏
घ 𑂐
ङ ઙ *
च ʧ / 𑂓'
छ 𑂓
ज 𑂔
झ Ɉ / 𑂕
ञ 𑂖
ट 𑂗
ठ ઠ *
ड ડ
ढ 𑂛
ण 𑂢
त ત *
थ 𑂟
द ໔ * Lao digit
ध ຍ * Lao letter
न 𑂢
प 𑂣
फ ફ / ꜰ *
ब ദ * malyalam
भ 𑂦
म 𑂧
य ય *
र ર *
ल ന * malayalam
व વ *
श શ *
ष 𑂭
स 𑂮

1. ह 𑂯ऩ 𑂢ऱ રक़ 𑂍'ख़ ખ'ग़ 𑂏'ज़ 𑂔'ड़ 𑂚ढ़ 𑂜फ़ ફ'य़ ય'क्ष ક્ષज्ञ જ્ઞ

@nerd

Color Combo in Pair that are eye candy to me

Contrasting Red, Blue, Green, Yellow, Black as major and white or silver as minor

@lemmy

Welcome !

This post is crossposted from Mastodon to Lemmy

@lemmy

The update fixes an issue with moderation actions sometimes not federating correctly(See release notes here).

There should be no or very minimal downtime. To convert UTC to your local time, use this

First post. More to come!

I expect a very minimal downtime of ca. 5-15 mins.