Post @post@social.cleverlibre.org

✨ The future is federated

Imagine being able to follow Twitter accounts from your Instagram account

With Mastodon & Pixelfed you can!

▶️ https://pixelfed.org

JOURNALISM 101 RULE: If someone says it’s raining, and another person says it’s dry, it’s not your job to quote them both. Your job is to look out of the fucking window and find out which is true. — Now more than ever.

I'm so proud of this community

Doom scenario: in 10-20 years, the FSF and/or GNU boards are infiltrated by commercial interests and publish GPLv4, which degrades to MIT equivalent and removes copyleft from all projects with a "or later" clause in their GPL license

Big thanks to @captainepoch for all their hard work on Husky over the years 🎉

I maintain a browser extension for saving quoted text or just the page URL in markdown. I made it for my own use of Logseq, but it's useful for anything that uses markdown.

Chrome: https://chrome.google.com/webstore/detail/link-md/nfjkoojhgklbbnlonpdplbdjkgoemgod

Firefox: https://addons.mozilla.org/en-US/firefox/addon/link-md/

#chrome #firefox #logseq #obsidian #markdown #javascript

Hello World! We are now live on Fosstodon

#introduction Hello! I work on free software. Trying out Mastodon again.

Here are some projects I'm working on at the moment:

https://sr.ht/~sircmpwn/sourcehut
https://sr.ht/~sircmpwn/hare
https://sr.ht/~sircmpwn/helios

Journals in Logseq can be used to implement the concept of Engineering Daybooks mentioned in the book The Pragmatic Programmer. Or at least that's how I've been using them.

#Logseq #PragmaticProgrammer

Came across https://github.com/Endle/fireSeqSearch today, which indexes your #logseq notes and displays them alongside web search results 👀

idk how useful I'll find it on a daily basis but at least this will get me to look at my old notes more often.

@JoshuaACasey Agreed, especially when the system makes it so easy for individuals to block. You onnly need to block servers not people and you address mostly all bad actors.. so a dozen or two blocks and an individual is good. There is no NEED for a master block list forced upon them because the block lists are so manageable.

Moreover users can just import the blocklist as a CSV, so it literally takes a few seconds.

@freemo that's another reason why I like this instance. Instances should not be responsible for blocking. Individual USERS should be responsible for blocking stuff that they don't want to see.

I mentioned this in a private message to someone recently about why a small handful of servers block qoto. I wanted to reiterate it here for the new comers on QOTO who dont know the history:

So there are some servers out there that demand every server int he network block every instance they do, and if a server doesnt block an instance they block then they block you in rettatliation.

Their reason for this is quite flawed but it goes like this.. If we federate with a bad actor instance and we boost one of their posts then their users will see it and defeat the purpose of the block. The problem is, this isnt how it actually works. If they block a server and we boost it, they wont see the boost, thats how blocks work.

The issue becomes even more complicated when you consider the fact that these servers, by virtue of their policy, have huge block lists where they block tons of major servers. So in order to satisfy them we too would have to block a huge number of servers.

This means you have a choice, you either join a server that isnt blocked, but has a huge block list themselves, or, you join a server that doesnt block and be blocked by a small handful of servers. Obviously that means on QOTO you will have bigger view of the world than you would on any of these others servers. In fact QOTO has onne of the largest federation footprints of any server in the network.

I want to also explain why we choose the decision we did. Years ago when this controversy started and servers across the fediverse started blocking there was a divide of people taking sides. WOTO was one of the few servers that didnt take sides and allowed people read content from any server (but with strict hate speech rules). This caused a huge influx of people,s pecifically from the LGBTQ community, onto our server. It turns out many people relied on us not-blocking for their physical safety. There were big name biggots (like milo yanappolus) who were on the network. They used their accounts here to watch his account for doxing so they could warn themselves and their community and protect themselves accordingly. In fact we added a feature just for them called subscriptions which allowed them to monitor accounts without following them so they could do so anonymously.

In tthe end for the safety of the LGBTQ community here we refused to engage in mass server blocking and instead encouraged our users to block servers on an individual basis and provided access to block lists for them to do so. But some really misguided servers blocked us anyway.

Thankfully the servers blocking us are few and far between and are limited to only the most excessive and aggressive block lists. As I said, QOTO has one of the largest federation footprints on the fediverse,

#mastoadmin

Once you start seeing how much space we sacrifice for #cars, you can't unsee it. They have taken over our cities completely.
And they feel entitled and justified to every single space available. Given a chance, anything becomes a parking spot.
And if you dare speak up about it or oppose it, #motorists respond immediately with aggression, violent threats, racism and sometimes actual violence.
Don't dare advocate for a cycle lane, some space in the footpath for a wheelchair user, or a stroller.

If you have worked with namespaces in #logseq before v0.8.9, you should migrate your existing pages according to the "New file name rules" mentioned almost at the end of release note https://github.com/logseq/logseq/releases/tag/0.8.9. Otherwise you might notice some weird behaviour with the pages in a namespace.
@logseq

@pedrosilva @logseq Logseq is so good. I’ve LITERALLY been searching Logseq for years.

Didn't expect to find so much people mentioning @logseq around here.
Looks like #pkm and #logseq are becoming a thing.