Mastodon 4.0 has introduced feature-breaking change
#Mastodon v4.0+ has introduced a change to the "Favorite/Reshare this" modal which makes it currently not compatible with #Friendica . Here how it is:
1) E.g. visit an up-to-date v4.0+ instance like social.tchncs.de and go to any post/toot. Now click on Favorite/Reshare (doesn't matter which one) and you are presented with a rebuild modal where you can locally login/signup or copy the URL so you can paste it into your instance's search form.
2) Just simply do that with your Friendica's search form and you won't be able to "manually federate" it over to your instance so you can interact with it.
Previous 3.x versions allowed me to enter my web-finger @roland@f.haeder.net
and redirected me to my instance after "manually" federating it to there. It worked like a charm! I'm sure the developers of Mastodon have their reasons for this change but this change made it impossible for at least Friendica instances to "manually" federate the toot/post/comment so you can comment on it.
Can we somehow make this work on our side?
Mastodon
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!Mastodon hosted on social.tchncs.de
Pascal likes this.
reshared this
My goodness, VARBINARY sucks so much!
When I wan to run some SELECT
statements on some tables, I always get a SQL query like SELECT *, HEX(`column`) AS `column` FROM `table` WHERE `other` LIKE UNHEX('%foo%')
in tools like #Adminer (a PHP-based web-frontend I usually use to administrate my database server). This causes it that zero records are being found and the culprit here is the wrong/excessive use of VARBINARY
instead of VARCHAR
(string variable character length) and a proper collation like utf8_general_ci
for all tables.
I don't know why you e.g. want to have non-alpha-numerical characters in URLs or keys?! Why on good Earth that? I think a #RFC states that such characters needs to be URL-encoded with %HEX-CODE
to avoid interference with not so tolerative systems. For example, I sometimes like to know how many contacts my node knows for a specific domain, so I usually choose LIKE %%
and enter the domain name to look for. It worked always flawless before but since VARBINARY
is in place, I can no longer find records.
Very sad to see such development.
CSS class' "icon" property "height" causing distance beween two lines in profile views
The said #CSS class .icon
has a property height: 48px
which with current HTML structure causes a distance between two lines when I view a remote profile (view: /contact/X
or a post (view: /display/X
):
I'm sure, removing height
from the said CSS class won't fix it in the long run but maybe checking the HTML/div structure would.
Friendica Support reshared this.
view/global.css
, was somit fuer alle Designs gilt.Friendica Support reshared this.
Null-safe invocation of Enum.compareTo()?
I look for an utilities class or self-implementation to invoke Enum.compareTo()
in a null-safe manner.
Does anyone know such a class or how to implement it? I have a few enumerations written here and I COULD write one for each one. But I guess there might be a more intelligent and flexible way to do this.
The background here is that I have a public default constructor for the #JPA here and an other constructor that beside some other class fields sets this enumeration. Still I need to compare both instances ("empty" one and one with set values) in a null-safe manner. If I try to implement it without the null-check, it throws the all-famous #NPE at me and a unit-test fails.
PS: Is there a #Java group/forum like !java
available somewhere?
Enum.compareTo()
by implementing a static method accepting Enum<?>
as types) and then checking both on equality (==
) and null
each. If none of them is null
, the method Enum.compareTo()
can be safely invoked.
Blackbird reshared this.
Sylvia J likes this.
utzer [Friendica]
in reply to Roland Häder🇩🇪 • • •@Roland Häder no way, Mastodon would never break a working thing, they don't do things like that. 😜
It seems to work for me, I went to mstdn.social, to this post and clicked the reshare, copied the link and searched for it on my server.
This showed the local copy of the post.
But... The post was already available locally, it did not show the two times like a new received post does.
Roland Häder🇩🇪 likes this.
Friendica Developers reshared this.
Roland Häder🇩🇪
in reply to utzer [Friendica] • •@utzer ~Friendica~ I guess that one works (and worked here, too) because of it has already federated to your/my instance. Try it on posts from instances, that isn't yet known to yours. I tried it in the past and it didn't work.
Let me try to find a proper example, please.
Friendica Developers reshared this.
utzer [Friendica]
in reply to Roland Häder🇩🇪 • • •Roland Häder🇩🇪 likes this.
Friendica Developers reshared this.
utzer [Friendica]
in reply to Roland Häder🇩🇪 • • •https://noc.social/@skimlines/109390044994689743
Friendica Developers reshared this.
Roland Häder🇩🇪
in reply to utzer [Friendica] • •Friendica Developers reshared this.
utzer [Friendica]
in reply to Roland Häder🇩🇪 • • •@Roland Häder blocks don't work when you fetch a post, unless they drop connections from your server.
I never used the webfinger way, actually never bothered too. But yes, it would be nice to have that too.
Roland Häder🇩🇪 likes this.
Friendica Developers reshared this.
Roland Häder🇩🇪
Unknown parent • •Friendica Developers reshared this.