Notices by jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site), page 2
-
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Wednesday, 31-Jul-2019 20:39:55 UTC jejune :abunhdhappy: @roka @bandali
yes, we have been talking about it for some time. there was in fact, quite a bit of speculation about whether Mastodon or Pleroma would do it first. it turns out Mastodon did it first as part of general refactoring work ahead of 3.0 release.
OStatus has a lot of design flaws that make it extremely difficult to implement in a secure way. there are numerous embargoed bugs that affect Pleroma's OStatus implementation as well as Mastodon's and GNU Social's.
these bugs exist because OStatus is unnecessarily complex.
and, frankly, we can't move forward on security in any serious way as long as there is a gaping hole that can be used to bypass (the pending 1.0.3 release fixes two protocol downgrade attacks that other implementations are also vulnerable to)
we do plan to keep OStatus support in the 1.x tree, which is likely to remain supported for some amount of time, but 1.1+ will have OStatus turned off by default.
2.0 will remove OStatus entirely from mainline (but if people want to maintain the modules out of tree, that should be easy enough) -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Wednesday, 31-Jul-2019 03:26:25 UTC jejune :abunhdhappy: @Laurelai is this kayla -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Tuesday, 30-Jul-2019 22:20:49 UTC jejune :abunhdhappy: anyway, if anyone wants a free pleroma instance, hit me up. the only catch is that you're a beta tester and so you don't get to complain if i rebake your container randomly. -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Tuesday, 30-Jul-2019 21:10:55 UTC jejune :abunhdhappy: anyway if you want managed fediverse hosting for [pricing depends on what you require], fediverse.services will beat masto.host pricing for the foreseeable future
(and unlike masto.host, i don't have any overlords to answer to, so you can't be deplatformed unless you annoy *me* directly.) -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Sunday, 28-Jul-2019 18:19:04 UTC jejune :abunhdhappy: tired: station wagon
wired: crossover SUV -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Wednesday, 24-Jul-2019 14:36:55 UTC jejune :abunhdhappy: we are actually very close to getting to where we need to eviscerate proprietary social platforms and their data abuses.
the work going into Pleroma 2.0 and Mastodon 3.x and all the other fediverse software will give us the solid foundation of consent we need to make it happen.
this isn't financial advice but it's getting close to time to short facebook stock. -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Thursday, 18-Jul-2019 14:45:03 UTC jejune :abunhdhappy: do you hate stuff like Cloudflare? why not make DDoS obsolete? demand your ISP implement BCP38 today. the answer to these problems has been known for literally decades at this point. -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Thursday, 18-Jul-2019 14:38:59 UTC jejune :abunhdhappy: imagine how much better the internet would be if people actually enforced BCP38 on their networks -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Wednesday, 17-Jul-2019 20:04:44 UTC jejune :abunhdhappy: stickers are coming to Pleroma! https://git.pleroma.social/pleroma/pleroma-fe/merge_requests/885 -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Tuesday, 16-Jul-2019 01:44:22 UTC jejune :abunhdhappy: anyway, last thing I want to say about MRF Transparency Exclusions is, I personally believe it’s a misfeature.
incidentally, many of the other things I implement on request from other people/groups I also believe are misfeatures.
with that said, the transparency community has the current view that partial transparency is still better than zero transparency. maybe this is the wrong view, but that’s the current view.
(also the “transparency cabal” is not a pleroma group, it’s a multi-stakeholder group, so dropping in a pleroma IRC channel demanding answers from the “transparency cabal” is just going to make you look ridiculous.)
and the reason why is because the transparency data is intended to be used in tasks like instance recommendations (“i want to see an instance that can federate with pleroma.site” as an example user story).
in a recommendation engine, partial transparency is fine, as long as the data is weighted appropriately: full data gets weighted over partial data, and both get weighted over data which shows that the target instance is blocked.
voila, you get recommendations that most likely can federate with the instances you care about.
and this is the real purpose of transparency: solving the onboarding problem.
-
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Monday, 15-Jul-2019 23:03:37 UTC jejune :abunhdhappy: ah yes my agenda of implementing things that people request, typically disabled by default -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Sunday, 14-Jul-2019 20:57:20 UTC jejune :abunhdhappy: correction. i forgot to actually bump the version on the release.
the actual Pleroma 1.0.1 OTP releases can be found here: https://git.pleroma.social/pleroma/pleroma/pipelines/14677
they are still building, but they include the OStatus spoofing fixes and MRF transparency exclusion feature.
everyone else can just update to the latest git master or develop branch. -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Friday, 12-Jul-2019 19:01:57 UTC jejune :abunhdhappy: what if gab.com looked like THIS
Screenshot_20190712_140132.png… -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Friday, 12-Jul-2019 17:29:19 UTC jejune :abunhdhappy: if you like @darius's https://runyourown.social/ it should be noted that many of those concepts are in the pipeline for Pleroma 2. -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Tuesday, 09-Jul-2019 12:51:59 UTC jejune :abunhdhappy: @dalme @colegota @up201705417 because of my work to modularize publishing in Pleroma, OStatus support remains here. but we will eventually deprecate it. -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Monday, 01-Jul-2019 06:26:53 UTC jejune :abunhdhappy: i set up a peertube instance. it's a joint venture with @sir (he provided the domain)
for lack of better judgement, i haven't restricted signups yet.
that means, you can sign up today at https://spacepub.space and fill my hard drives up with whatever crap you want
just don't post fucked up shit. and yes, the official definition of "fucked up shit" is "i'll know it when i see it" -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Sunday, 16-Jun-2019 06:12:25 UTC jejune :abunhdhappy: by the way if you think Michabo is a cool fediverse client, feel free to support it's development with your $$$. your support helps to ensure that development continues in an impartial manner.
https://patreon.com/kaniini
https://liberapay.com/kaniini
hell, i'll even make a bitcoin wallet if someone wants to send me bitcoins -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Sunday, 16-Jun-2019 00:49:21 UTC jejune :abunhdhappy: I am pleased to announce the immediate availability of Michabo v0.1. Sources can be retrieved from the Michabo Git repository. A pre-built binary for Mac users has been attached to this post.
I was planning to do a pre-built Windows version, but was unsuccessful in getting OpenSSL to work with Qt on Windows. Help with that is certainly welcome for future releases!
Michabo is a performance-oriented desktop client for Pleroma and Mastodon instances. With the exception of media handling, which is still a work in progress, the client implements most of the features one would expect in a fediverse client.
The primary goal of the client is to bridge between the fediverse and the desktop computing experience. This goal is only partially realized as yet, and I intend to write a more detailed blog soon about how this design goal is ultimately realized.
Michabo is free software, built by the Pleroma community and licensed under the GNU GPLv3 license.
Right now here are Michabo’s primary deficiencies:
No integrated support for viewing attachments (attachments are handed off to external viewers, with your web browser as the ultimate fallback)
Attachments without preview thumbnails are handled suboptimally.
The Attachment Grid Layout System could really still use some love.
Special timelines such as Pleroma’s Direct Messages timeline are not yet supported.
Composing messages with a custom scope are not yet supported (but the scope will be copied).
With that said, I’ve been using Michabo as my primary desktop client for the past few days to fairly reasonable success.
Please report any bugs you encounter to the Michabo bug tracker.
Michabo running on a Mac
Michabo.dmg -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Saturday, 15-Jun-2019 14:26:43 UTC jejune :abunhdhappy: you thought Putin was human. no. Putin is just a puppet controlled by a nearby rabbit. you'll find out soon enough. -
jejune :abunhdhappy: (kaniini@pleroma.site@pleroma.site)'s status on Sunday, 09-Jun-2019 01:21:48 UTC jejune :abunhdhappy: this means, if someone sends you an attachment, you can immediately have it in the software of your choice. videos get sent to VLC, images get sent to your favorite image viewer or editor, audio gets sent to your audio player etc.