Gargron
https://github.com/Gargron
•
Jul 5
But what about posts with no CW?
WeChat ID
aaronpk_tv
-
Posts with no CW would end up with just a
contentproperty. According to the new parsing rules, those look just like normal content-only posts and sites don't see anameproperty and treat them as normal text/microblog/toot/tweet posts. -
A change in the Microformats parsing spec from a few months ago reduced the cases where parsers would auto-generate a
nameproperty if there wasn't one in the original markup.Previously, when the
namewas autogenerated, people ended up having to add an explicitnameproperty to the HTML in order to avoid weird broken-looking names. Now that this change is approved and implemented in a couple parsers, things are working a lot better. I believe the Ruby parser has not yet implemented this change, but it's in the Python and PHP ones.Certainly one option is Mastodon could just remove the
p-nameclass, since the newer parsers would end up seeing those posts with just thesummaryandcontentproperties.Since afaik no Microformats consumers have the concept of CW/spoiler posts yet, this does raise the issue of how to provide a good fallback behavior for consumers that don't understand spoiler posts. My thought with moving the
p-nameclass to the same element asp-summaryis that the current consumers will see it as an "article", most likely only showing the name of the article. Here's an example of how my site renders comments that have a name (whether or not there is also summary or content)
Similarly, here's what my site shows when I'm replying to a post that has a name:
If the
p-nameclass is used only for the CW/spoiler preview text, then my site wouldn't show the full content in either the reply context or as a comment, which seems like the safest fallback behavior. -
Carl Hancock 🚀
http://www.gravityforms.com
•
Jul 5
There are obviously ways to do it. But the problem is it introduces friction. Users have to do X before they can do Y. Instead of just being able to connect an app to their WP site without having to install additional tools. WP needs a core solution for authentication.
Absolutely. I was more implying that someone should take this plugin and move it into core as a quick way to get OAuth into WordPress, since the work is already done. -
DΛVID V3.0.5
https://davidwolfpaw.com/
•
Jul 5
Similarly, if I had the proper skillset I'd love to push for more methods to be included like OpenID and IndieAuth.
Check out the work done on the IndieAuth plugin: https://wordpress.org/plugins/indieauth/
It also works as authentication for the REST API. IndieAuth has the benefit of not needing to pre-register clients, so it is actually useful in a distributed setting like how WordPress works. -
In Together, the notifications channel is the little bell icon in the top right corner!
-
cactus
https://github.com/cactus
•
Jul 4
go-camo was indeed originally intended to proxy only images, for two reasons: 1) the camo project it was inspired by only proxied images 2) my use-case at the time only required proxying of images
Later, a fork was created by a user to additionally proxy fonts and css. I wasn't comfortable including those in go-camo -- see discussion on https://github.com/cactus/go-camo/issues/20.
In my experience, video files are "usually" either linked (by url, no content warning), uploaded (service hosts it, so no content warning), or inlined from some hosting service (eg. youtube, vimeo; ssl provided by service). Video files are also generally much larger than image content.
Can you further describe your use-case/requirements for proxying video?
Ah, I can see why css/js could be an issue for some uses.
I'm using this on the server side of my new social reader application so that all image/video URLs presented to the reader apps are https and from the same origin. The videos come from either Instagram, Twitter, or peoples' own blogs hosting video files directly. Because the majority of the content is twitter-like short posts, the video files are normally always under a minute long so they aren't actually that big.
-
sknebel
https://github.com/sknebel
•
Jul 4
Looking at this again, I'm not sure what a good spot for a general note would be.
If you ok it I'd prepare a pull request adding the header to the examples?
At the very least adding the
Acceptheader to the examples is a good place to start, go for it! -
Nope, I also don't have permission to create repositories on the Microformats org on GitHub.
-
I’ve made you an itty bitty experiment just in time for independence day–
a tool to create websites contained within their own link.
🌐 http://about.bitty.site - a brief summary
⚙️ http://how.bitty.site - how it works
What might you make with it?
🇺🇸 http://independence.bitty.site
-
Portland, Oregon • Tue, July 3, 2018 4:43pm
-
RIP https://www.moves-app.com
You can use my location tracking app as a replacement, tho it requires you set up your own backend for it. But at least that way you're the only one who can decide to shut it down!
https://overland.p3k.io -
-
If you’re looking for an alternative, I strongly recommend Overland (https://Overland.p3k.io) by @aaronpk—tho you will need your own backend (which is a selling point IMHO)
-
nitinthewiz
https://github.com/nitinthewiz
•
Jul 3
@aaronpk could you share this script that adds the weather data? I'd like to add that to my setup.
Sure thing! Here's the script I use, you'll need to fill in the three API keys at the top of the file, and of course replace compass.p3k.io with your own domain. https://aaronparecki.com/2018/07/03/7/ -
Ton Zijlstra
http://zylstra.org/blog
•
Jul 3
Describing my ideal RSS reader, https://www.zylstra.org/blog/2018/07/my-ideal-rss-reader/ Maybe @TinyTinyRss_com can be the starting point for some tinkering #Indieweb #RSS
Pretty cool ideas! You can definitely create the group/folder model with the current #indieweb readers. I'd love to add a search feature to Monocle and Aperture too!
