Keith Whyte @keith@tic-ac.org

Is there a name for this rhetorical trick?

1. A writer asserts that "anyone who still uses two spaces after a full stop is abusing the language."
2. The writer notes that their target "is one of those people who still uses two spaces."
3. From that point, the author and all their fans describe the target as "an abuser" and their work as "abusive" without clarification.
4. Anyone who tries to clarify is described as "an apologist for abusers".

I feel there has to be but can't think of it.

The new joinmastodon.org website delivered by @oakstudios is live (has been for a little while, actually, but I've been working on it still). I think it's the best it's ever been. Check out the branding and about pages too!

https://joinmastodon.org/

As you might have seen from the last boost, PeerTube's latest version now supports "ability to automatically import all videos from a remote channel (from another video platform)".

What does this mean?

It means you can automatically import your videos from YouTube to PeerTube 🥳

➡️

More info from PeerTube's official news page:

https://joinpeertube.org/news#release-4.3

#PeerTube #Fediverse #YouTube

Mäuse fangen

Chilean voters resoundingly reject a new ‘ecological’ constitution

Draft charter had major implications for economic policy, climate, environment, research, and Indigenous rights

https://www.science.org/content/article/chilean-voters-resoundingly-reject-a-new-ecological-constitution

#ClimateEmergency
#pollution #ecology #environment #ClimateCrisis #ClimateCatastrophe #CllimateChange #Chile

We're celebrating OpenStreetMap's 18th Anniversary! #OpenStreetMap18

https://blog.openstreetmap.org/2022/08/06/happy-18th-anniversary-openstreetmap/

Cake by @osmbd@twitter.com :)

I have been testing for the past few days three replacements for #Google's #Firebase notifications: #ntfy, #Gotify and #NextCloud's Unified Push project. A few observations after a bit of tinkering:

1. The idea behind #UnifiedPush is amazing. An open protocol to share push notifications over any asynchronous channel (websocket, Redis, MQTT etc.) is what open-source apps have needed for years. Sure, there will always be those who say "push notifications are a distraction, and I'm happy to ditch them". But individual choices/behaviors shouldn't shape the development of a technology - especially when people want a genuine open alternative to something that they like/need to use.

2. UnifiedPush support from individual apps is still scarce. So far I've only found the NextCloud app itself (which only supports UP-NextPush), #Fedilab and #Element. Support on #Tusky has allegedly been implemented in the latest release, but I haven't yet managed to make it work. Let's roll up our sleeves and make sure that more and more of the apps that we like support open notification services!

3. The notification providers' client apps themselves are still quite buggy, and documentation still very sparse. I have used UP-Example from F-Droid to test the UP services. Only ntfy managed to deliver notifications end-to-end to my devices. Gotify reported an "unknown error" without many details from the logs. UP-NextPush is still very unstable both on the client and server side and I couldn't manage to deliver any notifications.

4. The protocol (and the apps that implement it) needs to slowly be extended to cover as many as possible of the features that have been implemented in the past decade. Action buttons, icons from URLs, custom background images, updates to existing notifications etc.: a couple of these features have been (partly) implemented by 1-2 providers, but we need open standards (especially for action buttons and gestures) if we want to ensure inter-compatibility.

Mathijs de Bruin blogs about why http://ipfs-search.com is needed

https://blog.ipfs-search.com/introducing-ipfs-search/

Unendlich

Twitter is starting to block some instances of Mastodon... Spread the word!