Discussion
@wendinoakland @webhat @essjax
Birds also eat their own babies and also poo, but I don't think that's any reason humans should do it
@TheBreadmonkey you’re right, clearly. It seemed ripe for a counterpoint and then, immediately, went silly because the fediverse delivers! @webhat @essjax
@M0YNG what is your goal or mission behind the site? I might be able to help.
@N2LEE I don't really understand the question.
Mastodon.Radio has been around for 8 years, consistently has 700-800 monthly active users, is and always has been 100% funded by donations by our users and has been directly or vicariously responsible for 3 or 4 other radio instances plus single user servers
Seems pretty good to me 
№202 - Слюнтяйка
У всех свои предпочтения, не так ли?
@rf@mastodon.ml
#Tiff&EveRU #Еда #юмор #соус #пицца
@tiffandeve_ru У нас в постсоветской России SPAM'а не было, но сама баночная ветчина была.
И да, прямо из банки она шла на ура, у меня, по крайней мере.
Posted in
Fediverse
Sharing of ideas and code is a core tenant of FOSS. PyLova literally started as a copy of Piefed. Why shouldn’t the ideas and features flow both ways?
Multiple images in posts and in-line comment editing are basic features coppied from Reddit (and, like, every social media site), which probably coppied them from somewhere else. Let’s not pretend like PyLova is breaking new ground here, lmao.
Posted in
Fediverse
the fediverse logo is just so beautiful
i keep seeing it on the !fediverse@lemmy.world community and i keep going “aah ~” whenever i see it.
![Первая панелька: Ева в своей длинной-длинной футболке (или домашнем платье) морского цвета с флагом квебека, стоит и макает кусок пиццы в беловатый соус/салатную заправку. Тифф это замечает, и выражает своё омерзение: Ты макаешь кусок пиццы в соус ранч? Мерзость какая. Ева вкусняво жуёт и выпендривается: Ой, да не будь такой слюнтяйкой. Все так делают.
Вторая панелька: Тифф сразу решает отомстить, она лезет в кухонный надвесной шкаф, и говорит: Ох, это я то у нас слюнтяйка, да? Ева что-то заподозрила: Эй, чего это ты полезла доставать из шкафчика?
Третья панелька: Тифф, оказывается, достала консервы с ветчиной от спама, она с ехидным лицом вскрывает банку, Ева начинает отчаянно ругаться: Эй! Нет! Ты так со мной не поступишь! Не смей [нецензурная брань], не при мне! Тифф! ТИФФ!
Четвёртая панелька: Тифф вилочкой ест ветчину фирмы Спам прямо из банки, она издевательски это озвучивает: Ммм! Спам прямо из баночки! Вкуснятина. Ева сдерживается, чтоб не блевануть, и всячески ругает Тифф за её непоколебимую жестокость: КГРХ! ПРЕСВЯТОЙ РАТАТУЙ! ТЫ БЛ...БУУЭЭ, ЧЁРТОВ МОНСТР!](https://lamp.leemoon.network/files/webpublic-c034fcf0-1e2b-4e79-97e1-5c48a0f42240.png)
thread 'main' (1589097) panicked at iocaine-powder/src/sex_dungeon/means_of_production/voyeurs/regexes.rs:35:26:
failed to construct default matchers.Regex: Syntax(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
regex parse error:
^(?!x)x
^^^
error: look-around, including look-ahead and look-behind, is not supported
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
)
YAY!
Not friendly yet, but at least it tells the error.
Next: IP prefix matcher. There, I'm thinking about changing the API a little.
In iocaine 3, you constructed a matcher by doing Matcher.from_ip_prefixes(StringList.new().push("127.0.0.1/32")). You gave it a string list, and it made a matcher. Simple.
In iocaine 4, I can do this:
let matcher = matchers.IPPrefix.new([
[127.0.0.1 / 32, "localhost"]
]);
matcher.matches(127.0.0.1 / 32) // returns bool
matcher.longest_match(127.0.0.1 / 32) // returns Some("localhost")
The goal here is to be able to use the longest match's data part for logging, or... whatever else. Come to think of it...
match matcher.longest_match(127.0.0.1 / 32) {
Some(data) => { ... }
None => {},
}
That could also work, and then we only perform the lookup once. The downside is that if I'm only interested if it matches, I still have to unwrap it... so I guess the .matches() variant is still useful.
And then there’s the first edition, which is now titled “Cascading style sheets : the descriptive guide” and still lists the editor as a co-author. I’ve told them twice now that the editor is not a rights holder. I submitted a scan to show that that person was an editor, not an author. AND YET.
@Meyerweb sufficiently advanced incompetence is plausibly-deniable indistinguishable from malice
This one perplexes me as well. Even if the tech CEOs and crypto VCs thought Trump would be president for life, the guy is 80. It wouldn’t have lasted that long and a reckoning was inevitable.
Their thinking has been so short-sighted on this, much like their treatment of workers as they pivot to AI.
@carnage4life It's simple: they are faschists themselves.
Look at all the beautiful fediverse apps!
GNOME is at Capitole du Libre!
Capitole du Libre is taking place in Toulouse on November 14 and 15 at INP-N7.
Come chat with us and other free software communities, pick up some stickers, and support the GNOME Foundation by grabbing some awesome T-shirts!
Today is another "thanks, git reflog" day.
Today is yet another "thanks, git reflog" day.
Today is another "thanks, git reflog" day.
🔐 Direct messages are now stored encrypted
Since 14 November, all direct messages on bizzfed.de are encrypted at rest in the database (AES-256-GCM), including existing ones. The key is kept separate from the database and is not part of the backups.
What it gives you: anyone who got hold of a database dump or backup would only see ciphertext.
What it is not: not end-to-end encryption. The server encrypts and decrypts messages itself, so the operator can technically still read them. If you write to someone on another instance, the message leaves BizzFed via ActivityPub and is stored under that instance's rules.
Backups from before the change still contain the messages in plaintext and are deleted after 30 days at the latest.
Nothing changes for you. Everything works as before, including Mastodon apps and the data export.
Self-hosting? Encryption is optional and described in INSTALL.md. Details are in our privacy policy: https://bizzfed.de/datenschutz
🔐 Direktnachrichten sind jetzt verschlüsselt gespeichert
Alle Direktnachrichten auf bizzfed.de liegen seit dem 14. November verschlüsselt in der Datenbank (AES-256-GCM), auch die bereits vorhandenen. Der Schlüssel liegt getrennt von der Datenbank und ist nicht Teil der Backups.
Was das bringt: Wer einen Datenbank-Dump oder ein Backup in die Hände bekäme, sieht nur Chiffretext.
Was es nicht ist: Keine Ende-zu-Ende-Verschlüsselung. Der Server ver- und entschlüsselt Nachrichten selbst, deshalb kann der Betreiber sie technisch weiterhin lesen. Schreibst du jemandem auf einer anderen Instanz, verlässt die Nachricht BizzFed per ActivityPub und wird dort nach den Regeln der Instanz gespeichert.
Backups von vor der Umstellung enthalten die Nachrichten noch im Klartext und werden spätestens nach 30 Tagen gelöscht.
Für dich ändert sich nichts. Alles funktioniert wie bisher, auch in Mastodon-Apps und im Datenexport.
Selbst hosten? Die Verschlüsselung ist optional und in der INSTALL.md beschrieben. Genaueres steht in unserer Datenschutzerklärung: https://bizzfed.de/datenschutz
Marcin Wichary @mwichary shared links to the interface guidelines and style guides of some historical GUI frameworks such as GEM, OLPC, and Windows Phone 7.
Забыл остатки кофе в любимой гейзерной кофеварке, а он заплесневел, и плесень ПРОЕЛА АЛЮМИНИЙ.
@drq жду боя между постсоветской плесенью и британской 
Friends, it looks like someone is trying to impersonate me on the Fedi --- I can't see any content they've posted, but they're using my display name.
Please block/report that account if you see it.
Posted in
Fediverse
This blog post reads like AI slop.
Dansup does rely on LLMs, so it wouldn’t surprise me.
Posted in
Fediverse
This blog post reads like AI slop.
Sorry, the app encountered an unexpected error
