home.social

#antifeatures — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #antifeatures, aggregated by home.social.

  1. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  2. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  3. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  4. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  5. @hrefna

    > Unsafe

    The most unsafe part about #fediverse is master-don dominates with its #antiFeatures.

    M'don is not much decentralised as many assume (see #CDNs). We just had a little rant about it.

    We cannot protect fedizens, without protecting instances themselves. Adoption of I2P and/or at least proposals like #GlutPlug to help decentralise #contentDelivery will protect instances, but such discussions are nowhere.

    Case in point, even slow-moving #bitcoin has #I2P support now.

    #privacy

  6. @LionsPhil @nicuveo
    Re #hashtags. We have a pinned toot about it, it's that important.

    On fedi, use #milkshakeDuck, not simply 'milkshake duck'.

    In addition to being able to import toots, there *does* need to be a way to do #booleanSearch for #hashtags.

    eg. Either/or: #icecream #icecreme #gelato #gelati
    Addition: #icecream #icecreme +#fediArt
    Subtraction: #btc -#nft

    It seems #MastodonDevs are more interested in shadowban functions and #antiFeatures like the #botFarmTimeline, tho.

  7. @Mastodon
    For those thinking of forking Mastodon, please do so in a safe environment such as on the #InvisibleInternetProtocol (#I2P).

    - Consider removing the 'Explore' timeline (*cough* botfarm timeline)
    - Consider #makeJavascriptOptional
    - Consider not showing like and boost counts until a person actively opens the toot thread.
    - Consider not implementing the #antifeatures mentioned above.

    In wartime, artists are the first to be targetted. Please #useI2P and live.

  8. We remember asking for #QT on fedi, not in so few letters, but we did ask.

    Someone explanted that fedi was different. People found #QTs to be abusive on the #dotcons. We thought about that and basically instantly realised that our past #behaviour may have been less civil.

    We adjusted.

    I do not believe in yeilding to them (and many bots) who have descended upon Fedi, and specifically it seems, #Mastodon servers, in the past couple months.

    They should learn like we did.

    #antiFeatures

  9. @joeo10

    Dunno.

    > Appears on the scene to take control of fedi at some might say a very sensitive and opportune time,
    > Gets a disproportionate amount of funds to develop fedi software,
    > continues to not enforce #AGPLv3Compliance against #HellaDoge.com,
    > Magically comes to support #antiFeatures like forced #javascript, Explore Tab, showing interaction counts, etc
    > #JoinMastodon.com is CloudFlare,
    > But says 'no' to #ventureCapital out of #SiliconValley.

    Hmm.
    @Gargron

  10. If #Mozilla had less funding, #Firefox might be a more stable #webBrowser.

    Part of the reason we find it unstable is because by the time we understand the latest #antiFeatures, and how to easily remove, disable, recompile them out. They are already deploying a new zeroDay.

    Its intolerable.

    #UBIFixesThis #bitcoinFixesThis