Soapblock list updated. about 40 additional sites detected using Soapbox.

https://github.com/VyrCossont/Soapblock

#Soapbox #Soapblock

The Mastodon project is planning to release critical security patches for the 3.5, 4.1, 4.2 branches and to main (4.3) this Thursday, Feb 01, at 15:00 UTC. Add a reminder to your calendars now.

(3.5 went EOL in December, but as this security patch is critical, there will be a patch for it)

If you're not already on the latest releases of 4.1 or 4.2 (or haven't updated your main branch code in a while) or you have a lot of customizations that you need to re-implement, you should do those in the next three days to minimize the effort and adopt these patches as quickly as possible.

#MastoAdmin

@panos @box464

on a side note, the fact that Threads seems to be developing against Firefish is amazing

agreed on that Masto should just take the Misskey implementation and be done with it. I appreciate that theyre now suddenly concerned about consent and safety, but if that was really an actual priority theyd just accept the glitch fork patches for allow-list federation, instead of spending a year building their own implementation for quote posting

#Threads is attempting to communicate the inclusion of quote posts in their AP messages.

Unfortunately, there’s not a true agreed upon standard for quote posts. Some #FediApp developers have made an agreement amongst themselves as to how that should work. Threads is not following those rules and has decided to use a _misskey_quote attribute in the AP messages. This isn’t coming across in the quote post format in most apps I use.

From: @pcottle
https://cyberplace.social/@pcottle/111729050177931482

note that sites on the removed list should be removed from your blocklist manually: these are sites that were formerly running Soapbox but have switched away from it.

i'm not sure if FediBlockHole is capable of handling removals except through its allowlist mechanism; allowlists are global and not suitable for this case.

#Soapbox #Soapblock

pleased to see that since the last Soapblock update, a few more sites have moved over to Mangane, and there is only one new Soapbox site

#Soapbox #Soapblock

@thisismissem i use recurring tasks in Apple Reminders for trash/recycling and also things like changing filters. they don't show up in the calendar, and they keep track of when they were last checked off.

Feditext beta users: today's build 79 includes the new "Siren" HTML parser, which is 3-6× faster than the current WebKit parser for the text formatting used in Fediverse posts. this should result in smoother scrolling for many users.

Siren is experimental, even more so than Feditext betas in general, so by default, it's off. to opt into Siren, open Feditext's preferences, scroll all the way to the end, select Siren from the "HTML parser" dropdown (instead of WebKit), and press the "Apply new HTML parser" button below it.

notes:

- do not switch parsers while writing a post: you will lose the post.
- the HTML parser is an app-wide setting, and can't be configured on a per-account basis.
- if you have issues with Siren, you can revert to WebKit from the same menu.

known issues that you don't need to report:

- blockquote lower vertical margins may be too big, causing the end of a blockquote's background rectangle to appear under the next normal paragraph. (however, the indents are still correct, so non-quoted text will not be indented.) this is related to https://github.com/feditext/feditext/issues/48 and https://github.com/feditext/feditext/issues/164 but is (currently) worse in Siren.

#Feditext #Metatext

Feditext beta users: today's build 78 fixes the paging issue with yesterday's build 77. big thanks to everyone who reported the issue.

if you had to downgrade from 77 to 76, please open the TestFlight app to install 78 and re-enable automatic updates for Feditext.

#Feditext #Metatext

Feditext beta testers: today's build 77 contains internal changes to the HTTP client and the API clients built on it, and shouldn't have any user-visible effects. there are no other changes, because the purpose of this release is to test those changes before building further on them. please let us know on the bug tracker if you see any new kinds of HTTP error.

update: build 77 has problems loading old home timeline posts. please stay on 76 for now; see downthread for how to revert to it.

for those familiar with Apple development: we've rewritten the clients to use Swift concurrency (aka async/await) instead of Combine, which is more readable and easier to reason about. this is the first step in replacing Combine in as many places as it makes sense, which we'll weave in with other work as we go.

prospective testers: we're working through a two-week message backlog, and will be sending invites out today.

we know it's been a bit since the last update. thanks for your patience.

#Feditext #Metatext

Fediblock rec: chaotic.ninja kishinjou.chaotic.ninja makai.chaotic.ninja

followbot + admin actively interacts with cawfee club, nyanide, other T0 instances

#Fediblock

@jdp23 @esm CLDR? i barely know'R

@jdp23 @esm https://github.com/mastodon/mastodon/blob/v4.2.0/app/lib/ascii_folding.rb

@esm and wait till you see how it normalizes hashtags

@esm Mastodon language handling is amazing. it also eats script information and can't tell Simplified from Traditional.

this started when I implemented post language support to the firefish backend, I saw that posts with the locale set to one containing a country code (e.g. en-US) wouldn't federate properly with mastodon - which is how I learned that mastodon strips the country code out of every locale string, including chinese languages

Feditext beta users: tonight's build 76 includes a partial fix for the iOS 17 performance regression. this fix removes a keychain access on a hot path, and is not related to the HTML handling change mentioned above, so you shouldn't see any visual changes.

as always, to update: open the TestFlight app, pull to refresh, and tap the Update button next to the Feditext icon and name.

#Feditext #Metatext

To know what software an instance is running (Mastodon, Pleroma, Akkoma, Firefish, Friendica, etc), have to make 2 calls:

1. `/.well-known/nodeinfo` - get the `href` for a nodeinfo link e.g. https://mastodon.social/.well-known/nodeinfo
2. `/nodeinfo/2.0` (possibly 1.0 or 2.1 too) - get the `software.name` e.g. https://mastodon.social/nodeinfo/2.0

And… both are not CORS-enabled (again) for web apps to request 😅😢

Reference: https://github.com/h3poteto/megalodon/blob/90461fa7d5a6349cb31dcd1d3c6ef8641281d29e/megalodon/src/detector.ts

#MastoDev #FediDev