Posts

For more information, see the search syntax documentation. Search results are sorted by creation date.

Search Results

Site and Policy » Philomena open beta / breaking API changes » Post 1

Site and Policy » Philomena open beta / breaking API changes » Topic Opener

byte[]
Solar Supporter - Fought against the New Lunar Republic rebellion on the side of the Solar Deity (April Fools 2023).
Non-Fungible Trixie -
Verified Pegasus - Show us your gorgeous wings!
Preenhub - We all know what you were up to this evening~
An Artist Who Rocks - 100+ images under their artist tag
Artist -

Philomena Contributor
Introducing Philomena
 
Over the past 6 months, the developers for the site have been bootstrapping an entirely new backend for the site named Philomena. This was deemed necessary due to unavoidable shortcomings of the previous Ruby on Rails backend, which we are planning to deprecate and release the source of within a few weeks.
 
The alpha testers and I believe we have gotten the release to the point where it should be usable for average use over the Rails application. You can try out Philomena using this link. (It is expected that you’ll have to log in again.) Please report anything you consider to be a bug, but before you do, please also read the following:
 
  • The scraper does not work correctly, and does not fetch Tumblr posts at all. This is due to an unfixed bug in hackney. When this is fixed I will let you know.  
  • A few things, like user settings, have been moved around due to the way Ecto/Phoenix handles model updates. Some settings are not yet implemented in the interest of current development priorities; however the ones most people use should be correctly implemented.  
  • Pages don’t have titles yet. We will fix this eventually.  
  • The beta site may be down occasionally (502 Bad Gateway) as we work out issues with our deployment strategy.
     
    API changes
     
    In the interest of preserving API compatibility, we will attempt to rewrite requests to our exisitng Rails JSON API for as long as is reasonably feasible after the migration (~ several months). We hope most applications will be able to migrate over to the new API format before we remove the Rails app completely.
     
    As before, you can use the filter_id parameter to override your current filter, and the key parameter to authenticate yourself to the API. Here are the new API routes:
     
    [example] GET /api/v1/json/images/:image_id  
    [example] GET /api/v1/json/search  
    [example] GET /api/v1/json/oembed
     
    There is also a POST route which takes a query parameter named URL. However, it depends on the scraper; do not expect it to work reliably until the scraper is fixed.
     
    POST /api/v1/json/search/reverse
     
    I want to help, how do I do that?
     
    Use the beta site. Report any missing features or obvious breakages here.
     
    If you think you are seeing something you aren’t supposed to see, you can contact me privately here, on IRC, or on Discord. The sooner I know about it, the better.
     
    Welcome to Philomena!
     

     
    ||Next week is finals week. Please don’t kill me if I’m not able to fix things as quickly as I’d like.||

Default search

If you do not specify a field to search over, the search engine will search for posts with a body that is similar to the query's word stems. For example, posts containing the words winged humanization, wings, and spread wings would all be found by a search for wing, but sewing would not be.

Allowed fields

Field SelectorTypeDescriptionExample
authorLiteralMatches the author of this post. Anonymous authors will never match this term.author:Joey
bodyFull TextMatches the body of this post. This is the default field.body:test
created_atDate/Time RangeMatches the creation time of this post.created_at:2015
idNumeric RangeMatches the numeric surrogate key for this post.id:1000000
myMetamy:posts matches posts you have posted if you are signed in. my:posts
subjectFull TextMatches the title of the topic.subject:time wasting thread
topic_idLiteralMatches the numeric surrogate key for the topic this post belongs to.topic_id:7000
topic_positionNumeric RangeMatches the offset from the beginning of the topic of this post. Positions begin at 0.topic_position:0
updated_atDate/Time RangeMatches the creation or last edit time of this post.updated_at.gte:2 weeks ago
user_idLiteralMatches posts with the specified user_id. Anonymous users will never match this term.user_id:211190
forumLiteralMatches the short name for the forum this post belongs to.forum:meta